... | ... | @@ -4,12 +4,12 @@ |
|
|
|
|
|
Internationalization and localization make it possible to use CiviCRM in languages and cultural environments other than American English. This includes the menus, form labels, help texts, but also date formats, currency/number formats, address formats and supporting various alphabets (ex: alphabetical order of search results).
|
|
|
|
|
|
We will try to keep it non-technical, but if you use CiviCRM in another language you will often encounter these terms:
|
|
|
|
|
|
* **Internationalization (i18n)** is a set of mechanisms to make it possible to translate (localize) CiviCRM to other languages without changing code.
|
|
|
* **Localization (l10n)** refers to using CiviCRM in another language than US English. This includes translating the text of the user interface, but also date, currency and other settings.
|
|
|
* **Multiple language support (multilingual)** means that the CiviCRM instance supports multiple languages, such as bilingual or trilingual sites. For example, on a Spanish/English bilingual site, a contribution form will have a title, introduction text and other configurations that must be in both languages. This means that not only the CiviCRM system messages must be translatable, but also some of the configurations (title, introduction text, etc).
|
|
|
|
|
|
For simplicity, we often refer to all of the above simplify as "translation".
|
|
|
|
|
|
Recent and future changes related to translation are documented in the [roadmap](roadmap).
|
|
|
|
|
|
### Administrator guide: Using CiviCRM in your own language
|
... | ... | |