|
|
What's planned for those using CiviCRM in another language than English? The following is a list of issues that have been identified and need work. Any help is most appreciated! Feel free to post on the Internationalisation and localisation forum to discuss any of these issues.
|
|
|
|
|
|
[[_TOC_]]
|
|
|
|
|
|
CiviCRM 4.7
|
|
|
===========
|
|
|
|
... | ... | @@ -22,9 +24,13 @@ Extensions |
|
|
* [x] Have a (very) long page to list all contribution page title/description, event title/description, option values, etc, to have a quick way of translating everything and finding strings? Have a way to search?
|
|
|
* https://github.com/coopsymbiotic/coop.symbiotic.translationhelper/
|
|
|
* nb: still requires a patch on core to fix overriding the 'ts' function.
|
|
|
* Extensions cannot add translatable menu item titles, i.e. we need to modify the civicrm_menu to add an extension column, so that we can properly translate the menu title in ts().
|
|
|
* Update the i18nexample extension with better examples for JS (ts closure) and smarty.
|
|
|
|
|
|
Backlog
|
|
|
=======
|
|
|
Dev backlog
|
|
|
===========
|
|
|
|
|
|
These are limitations that we are aware of, but no one is working on it.
|
|
|
|
|
|
* Greeting formats translation
|
|
|
* Mailing labels translation
|
... | ... | @@ -40,27 +46,17 @@ Backlog |
|
|
* Make the "organisation name" and "job title" multi-lingual? (goes with forcing to use the popups when editing those fields, in the past people would edit an organisation name in one language, and forget to update in the other language) - optional ?
|
|
|
* Event locations are not multi-lingual, event description? (should be.. bug?)
|
|
|
* (duplicate - cf CRM-16388) address format for labels should be multi-lingual (or depending on country?) .. sort of related to greetings (combinatory settings)
|
|
|
* Extensions cannot add translatable menu item titles, i.e. we need to modify the civicrm_menu to add an extension column, so that we can properly translate the menu title in ts().
|
|
|
* (big one) be able to enter titles/descriptions in multiple languages when creating new entities, not just edition. Ex: when creating a new group, the group must first be created in one language, then the user has to go back to editing the group and translate its name. This is really annoying for example when creating a new smart group from the advanced search.
|
|
|
* CRM-10006: When a language is removed in multilingual, the database is not cleaned up.
|
|
|
* Update the i18nexample extension with better examples for JS (ts closure) and smarty.
|
|
|
* When the CiviCRM core upgrader is run, if a localised install, make sure that the l10n files are present (sometimes admins forget to re-download the l10n files).
|
|
|
* When cloning contribution (and event?) pages, only the current language is cloned (ex: contribution page title).
|
|
|
* When a new language is added, pre-populate the translation of various option values.
|
|
|
* we can't assume that people install English first, then French (for example). They might be using Ukrainian and Russian.. so we can't just send strings in ts(). 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.
|
|
|
* Test RTL support for the CiviCRM menu.
|
|
|
* commit-hook to test/enforce ts() syntax usage.
|
|
|
* Contact Type token uses the name instead of the label (not translated)
|
|
|
* CRM-10509 - multilingual label for country / state (still a problem ?)
|
|
|
* Sysadmin: automatic synchronisation of regional translations.
|
|
|
* Sysadmin: jenkins task to detect new strings. Not necessarely push them automatically to Transifex.. but.. would be neat feedback to have regularly, have a faster cycle to push new strings (currently mostly manual).
|
|
|
|
|
|
Needs triage
|
|
|
============
|
|
|
|
|
|
* Report instances titles (and other settings?) should be multi-lingual
|
|
|
* Naming convention for first/last name, middle name, nickname, etc. How do various languages use them?
|
|
|
* when renamed, the field names in the import wizard does not always use the same name/translation
|
|
|
* a/b testing interface of CiviMail is not translated
|
|
|
* civimail/letter or anything else with templates: have a way to select a template based on gender?
|
|
|
* "New %1" (ex: new organisation) -> causes gender problems, also very confusing to users that the page title is not the same as the menu item.
|
... | ... | @@ -86,4 +82,11 @@ User documentation, with good practices for multi-lingual CiviCRM, ex: |
|
|
* saving the contact's preferred communication language
|
|
|
* formality, greetings, address formats
|
|
|
* document how to use string replacements in multi-lingual
|
|
|
* procedure for the user-admin book translation. |
|
|
\ No newline at end of file |
|
|
* procedure for the user-admin book translation.
|
|
|
|
|
|
Infrastructure
|
|
|
==============
|
|
|
|
|
|
* Automatic synchronisation of regional translations.
|
|
|
* Jenkins task to detect new strings. Not necessarely push them automatically to Transifex.. but.. would be neat feedback to have regularly, have a faster cycle to push new strings (currently mostly manual).
|
|
|
* commit-hook to test/enforce ts() syntax usage. |