|
|
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.
|
|
|
|
|
|
CiviCRM 4.7
|
|
|
===========
|
|
|
|
|
|
* [x] CRM-15375 Add wysiwyg editor in the multilingual popup for fields that need it (4.7.0)
|
|
|
* CRM-16355 Schedule reminder language settings (to send reminders in the contact's language) – patch needs review/update
|
|
|
* CRM-16352 CiviMail in multilingual sites: allow to define the language of the mailing (for tokens, unsubscribe links) – patch needs review/update
|
|
|
* [x] CRM-14588 Non Local Date format used in membership thank you and confirm contribution pages (4.7.0)
|
|
|
* CRM-16388 Add multilingual support to localization settings (money format, date format)
|
|
|
* CRM-16395 When installing in a specific language, load settings for that locale, ex: default currency, date formats
|
|
|
* [x] CRM-16176 Make it possible to translate relationship types label (4.7.0)
|
|
|
* CRM-14349 Multilingual word replacements
|
|
|
* [x] CRM-18362 Cleanup confusion between $config->lcMessages and global $tsLocale.
|
|
|
|
|
|
Backlog
|
|
|
=======
|
|
|
|
|
|
* Greeting formats translation
|
|
|
* Mailing labels translation
|
|
|
* add the address format in the civicrm_country table?
|
|
|
* have tokens for the formatted address? (not just the individual address parts)
|
|
|
* impact on the mailing labels creation?
|
|
|
* formatting of addresses in places such as the ThankYou page of online contributions? (ex: the country is formatted as a 2-letter abbreviation) Format as the UI language?
|
|
|
* UI for multilingual -> disable the standard field to force people see the different languages
|
|
|
* CiviContribute
|
|
|
* CRM-17199 in honor/memory of: the title and description text is not localizable? (the code is weird, see CRM/Contribute/Form/SoftCredit.php buildQuickForm().
|
|
|
* "Other Amount $" hardcodes a currency symbol after the field label (c.f. CRM/Price/BAO/PriceField.php, line ~ 330: $label .= ' ' . $currencySymbol).
|
|
|
* Setting for "first day of the week" (has an impact on reports). See also 4.7 work on user-defined report date ranges.
|
|
|
* 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
|
|
|
============
|
|
|
|
|
|
* 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?
|
|
|
* 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.
|
|
|
* Export/import of settings: the API has a option.language parameter, but what would be the most efficient way to upload/update settings?
|
|
|
|
|
|
Websites / community / marketing
|
|
|
================================
|
|
|
|
|
|
* [x] forum.civicrm: promote locale/locality forums higher up
|
|
|
* create a forum for all languages > 20% ?
|
|
|
* find a new home for non-English Q&A (the forum will go read-only in 2017)
|
|
|
* www.civicrm.org: better download page for each language, make sure we link to the i18n install docs (see: https://civicrm.org/download-translations)
|
|
|
* CRM-16363 Display i18n downloads if browser language not English
|
|
|
|
|
|
Documentation
|
|
|
=============
|
|
|
|
|
|
User documentation, with good practices for multi-lingual CiviCRM, ex:
|
|
|
|
|
|
* multi-lingual mail/PDF templates (using if/else for language, vs using 1 template per language)
|
|
|
* scheduled reminders
|
|
|
* mailings
|
|
|
* saving the contact's preferred communication language
|
|
|
* formality, greetings, address formats
|
|
|
* procedure for the user-admin book translation. |
|
|
\ No newline at end of file |