Uploaded image for project: 'In-Portal CMS'
  1. In-Portal CMS
  2. INP-235

Phrases of state and country names

    XMLWordPrintable

    Details

    • External issue URL:
    • Additional information:
      Hide

      Same idea with currency translations.

      In total we could decrease language pack by approximately 600 phrases, that never got changed.

      ---------

      Country and state names and currencies should stay in language pack but not under <phrases> node by now. We can create special nodes for them, and language pack format will be like:

      <LANGUAGES>
      <LANGUAGE PackName="English" Encoding="base64">
      <PHRASES>
      ...
      </PHRASES>
      <COUNTRIES>
      <COUNTRY iso="USA" translation=".....">
      <STATE iso="IL">...</STATE>
      ...
      </COUNTRY>
      ...
      </COUNTRIES>
      <CURRENCIES>
      ...
      </CURRENCIES>
      <EVENTS>
      ...
      </EVENTS>
      </LANGUAGE>
      </LANGUAGES>

      This way different language translation of countries/states/currencies could be still transferred in language packs, but won't be stored in Phrase table.

      Show
      Same idea with currency translations. In total we could decrease language pack by approximately 600 phrases, that never got changed. --------- Country and state names and currencies should stay in language pack but not under <phrases> node by now. We can create special nodes for them, and language pack format will be like: <LANGUAGES> <LANGUAGE PackName="English" Encoding="base64"> <PHRASES> ... </PHRASES> <COUNTRIES> <COUNTRY iso="USA" translation="....."> <STATE iso="IL">...</STATE> ... </COUNTRY> ... </COUNTRIES> <CURRENCIES> ... </CURRENCIES> <EVENTS> ... </EVENTS> </LANGUAGE> </LANGUAGES> This way different language translation of countries/states/currencies could be still transferred in language packs, but won't be stored in Phrase table.
    • Change Log Message:
      Refactoring Countries and States functionality and adding management options
    • External issue ID:
      279
    • Copy Issue Key:
    • Patch Instructions:

      Patches must be submitted through Phabricator.

      Description

      Currently we have around 400 phrases of for countries and states used for ex. during checkout process. Translation of such kind of phrases almost never got changed and they provide additional load to each template, because they are used for Country field for users and user object is loaded on every page and these phrase with it.

      I propose to create multilingual column Translation in StdDestinations table and move all current state/country translations there. Then loading of these moved values should be done using "options_sql" option in field definition in unit config.

      Later we can add separate grid, where administrators could enable/disabled unneeded countries/states and change their translation.

        Attachments

          Issue Links

          parent of

          Bug Report - A problem which impairs or prevents the functions of the product. INP-613 New Icons for "Site Domains" and "Countries & States" configuration sections

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Closed

          Bug Report - A problem which impairs or prevents the functions of the product. INP-620 Language pack upgrade fails, when it contains translations to non-existing email events

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Closed
          relates to

          Bug Report - A problem which impairs or prevents the functions of the product. INP-505 Current language is not replaced inside calculated fields, when "%2$s" is used

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Closed

          Bug Report - A problem which impairs or prevents the functions of the product. INP-544 Translatable fields are not always created during table scan

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Closed

          Bug Report - A problem which impairs or prevents the functions of the product. INP-545 SQL is partially parsed, when displayed in custom field editing form

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Closed

          Bug Report - A problem which impairs or prevents the functions of the product. INP-976 Fatal error during Installation on States import with MySQL in Strict Mode

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Closed
          mentioned in

          Page Loading...

            Activity

              People

              • Assignee:
                alex Alex
                Reporter:
                alex Alex
                Developer:
                Alex
              • Votes:
                0 Vote for this issue
                Watchers:
                0 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: