Uploaded image for project: 'CiviCRM'
  1. CiviCRM
  2. CRM-17065

When a new language is added, pre-populate the translation of various option value

    Details

    • Type: Improvement
    • Status: Open
    • Priority: Minor
    • Resolution: Unresolved
    • Affects Version/s: 4.6
    • Fix Version/s: Unscheduled
    • Component/s: Internationalisation
    • Labels:
      None
    • Versioning Impact:
      Patch (backwards-compatible bug fixes)
    • Documentation Required?:
      None
    • Funding Source:
      Contributed Code

      Description

      When installing CiviCRM, option values and some other string are initialized in the database using sql files.

      If later on, we add a new language or change the default language, the database translation will not be updated because there is currently no sql files to update.

      We can't assume that people install English first, so we can't just send strings in ts() and update the database based on the .mo files.

      An option would be to move option-values from xml/templates/civicrm_data.tpl to an XML file, and then do lookups in the XML file using the option_value.name.

        Attachments

          Activity

            People

            • Assignee:
              samuelsov Samuel Vanhove
              Reporter:
              samuelsov Samuel Vanhove
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated: