This documentation relates to CiviCRM version 3.3. It's not maintained anymore.
Current version of documentation.

CiviCRM Localisation

Comparaison des versions

Légende

  • Ces lignes ont été ajoutées. Ce mot a été ajouté.
  • Ces lignes ont été supprimées. Ce mot a été supprimé.
  • Formatting was changed.
Commentaire: Migrated to Confluence 4.0

Introduction

One of our goals is to make CiviCRM as usable as possible - which means get it fully localised into any languages that our users find useful and make CiviCRM configurable in all the places that are locale-dependent. To achieve this, CiviCRM uses gettext for text localisation and configuration options for date/money/address formats and the like. This approach assures that CiviCRM should be easily localisable into wide variety of languages (also the ones using non-Latin scripts/alphabets).

This page explains how to set up CiviCRM to run in one of the other supported languages and how to contribute new and/or updated translations into new languages back to CiviCRM.

User Language (Translations)

To configure CiviCRM to use an existing translation:

  1. Download the translations distribution - civicrm-<version>-l10n.tar.gz - from the CiviCRM Sourceforge downloads site. This tarball contains all files for the latest available translations.
  2. Uncompress the tarball and you will see a directory called civicrm, containing two subdirectories called l10n and sql. The l10n directory contains a set of sub-directories named using their locale codes. (Example: the Canadian French translation files will located in /civicrm/l10n/fr_CA)
  3. Copy this l10n directory, together with all its subdirectories into your CiviCRM codebase root directory. (note if creating the l10n folder manually it should be ell-ten-n, not capital-I-ten-n)
     - For Joomla this would be site_root/administrator/components/com_civicrm/civicrm.  So if you wanted the en_GB language it would look like this site_root/administrator/components/com_civicrm/civicrm/l10n/en_GB/ - For Drupal this would be site_root/modules/civicrm.  So if you wanted the en_GB language it would look like this site_root/modules/civicrm/l10n/en_GB/
  4. Login to CiviCRM (as a user with "administer CiviCRM permissions").
  5. Go to Administer » Configure » Global Settings » Localization
  6. You should now be able to see and select all the localization options in the Default Language and drop-down menu. If you don't, and instead can just see the default 'English (United States)' option, check the preceding steps as the drop-down options are set by the directories under your l10n directory. Also be sure to confirm that the l10n directory is correctly named as l10n (that is: el-ten-en and not eye-ten-en).
  7. The other settings on this page are described below. You can review them and adjust as needed. Be sure to save your changes when you're done.

Your CiviCRM screens should now appear in the selected language. If the underlying server has the proper locale generated, the full and abbreviated month and day names will also be localised properly.

Any text that has NOT been translated in the translation files will appear in the default English language. If you see English text after setting a different language, you may need to add to the translation. Refer to the section on helping with CiviCRM localisations below.

Other Localisation Settings

Localisation cheat sheets

If you are installing CiviCRM in a country other than the US and you want help with tips, tricks and common gotchas for your country, have a look at the Localisation cheat sheets which aim to document common tasks that you'll want to carry out to make your CiviCRM work best in your country.

Note: these cheat sheets are fairly new so it might be that there isn't one in your language - if that is the case, please consider starting one for your country.  Your fellow countrymen and women will appreciate it! (sourire)

Date Formats

One of the aspects of localisation is the display and input format for dates. By default, CiviCRM displays the dates using the American formats, but this can be modified to match your preferred formats.

You can define the formats for the following types of date display:

  • Complete Date and Time (dates that contain year, month, day and time)
  • Complete Date (dates that contain year, month and day)
  • Month and Year
  • Year Only
    Tip
    titleDate Formats Use POSIX Sequence Codes

    Date formats are specified using the standard POSIX %-prepended sequences. You should review these formatting codes and the Date Formatting Examples below before attempting to modify the date formats.

  1. Login to CiviCRM (as a user with "administer CiviCRM permissions").
  2. Go to Administer » Configure » Global Settings » Date Formats
  3. Update formatting patterns as needed and Save your changes.

Date Format Examples

The default American format for Complete Date and Time is:
%B %E%f, %Y %l:%M %P
...which, for the date of 2005-07-13, gets expanded to 'July 13th, 2005 2:26 PM'.

European users might want to redefine this to:
%E %B %Y, %k:%M
...which would display '13 July 2005, 14:26' instead (note the switch from 12-hour to 24-hour clock and dropping of the AM/PM display).

The default American format for Complete Date is %B %E%f, %Y
...which, for the date of 2005-07-13, gets expanded to 'July 13th, 2005'.

Typical European settings would have this format changed; it could look like this:
%E %B %Y
...which would get expanded to '13 July 2005' (or '13 lipiec 2005' if user language is set to Polish - pl_PL).

The Date Input Field formatting options define the order of the date and date-time drop-downs in various CiviCRM forms (for example, contact's birth date or scheduled meetings' date-times):

The default layouts are:
Complete Date and Time: %b %d %Y, %I : %M %P
Complete Date: %b %d %Y

These defaults provide the user with six drop-downs: abbreviated month name (%b), day (%d), year (%Y), 12-hour-clock hour (%I), minute (%M) and an AM/PM selector (%P).

European users might want to redefine these to:
Complete Date and Time: %d %b %Y, %H : %M
Complete Date: %d %b %Y

Which would display the day before the abbreviated month, switch to 24-hour-based hour drop-down (%H) and drop the AM/PM selector.

Countries and Provinces

The installed CiviCRM database contains both an ISO 3166-1-compliant list of countries, and a full, ISO 3166-2-compliant list of provinces (states, departments, voivodships, etc.).

You can configure the selections provided in address input fields for your installation (based on the geographic distribution of the address records you plan on storing). You can:

  • Set a Default Country. This country will be selected by default when entering new addresses.
  • Limit the list of Available Countries offered in Country drop-down lists on address input forms.
  • Limit the Countries whose States and Provinces are offered on address input forms.
  1. Login to CiviCRM (as a user with "administer CiviCRM permissions").
  2. Go to Administer » Confiugre » Global Settings » Localization
  3. Update the fields in the Contact Address Fields - Selection Values section as needed and save your changes.

Postal Address Formatting

In various countries, postal addresses are written differently. CiviCRM allows you to modify the default United States format to meet the requirements of your installation. This option is best explained by example. The American default looks like this:

Bloc de code
titleDefault Address Format
{street_address}
{supplemental_address_1}
{supplemental_address_2}
{city}{, }{state_province}{ }{postal_code}
{country}

The general rules are as follows:

  • Every {...token...} will be replaced with the token's value (keeping anything else inside the curly braces intact).
  • If the value of a given token is missing, the whole {...} construct will be dropped.
  • Any {non-token} construct will be turned into non-token if, after tokens are replaced, it has content on both sides (i.e., it will be dropped if on the beginning or end of any line). If there's no city, {city}{, }{state_province}{ }{postal_code} will turn first into {, }California{ }12345 and then into California 12345.
  • If, after token replacements, there are any consecutive {non-token} constructs, the first one's contents will replace the whole series. For example, if there's no state_province, {city}{, }{state_province}{ }{postal_code} will first turn into San Francisco{, }{ }12345 and then into San Francisco, 12345.

For example, Polish users, who usually don't write the vovidoship names in the address, might want to change the Address Formatting to:

Bloc de code
titleAddress Format without Province
{street_address}
{supplemental_address_1}
{supplemental_address_2}
{postal_code}{ }{city}
{country}

# Login to CiviCRM (as a user with "administer CiviCRM permissions").

  1. Go to Administer CiviCRM » Global Settings » Address Settings
  2. Update formatting patterns as needed and Save your changes.

Address Parsing

CiviCRM supports optionally enabling address parsing so that the various elements of a civic address can be automatically separated from each other as they are entered in the Street Address field. This can be enabled at Administer » Configure » Global Settings » Address Settings, then clicking on Street Address Parsing in the the Address Editting fieldset.

Currently, address parsing supports extracting the street number, the stree number suffix, and the unit from the address, but not the street type and stree direction. Parsing is especially useful when you wish to produce reports that can be sorted for walk lists for street canvasses.

Beginning in version 3.3, CiviCRM will support localisation of civic address parsing. Initially, Canadian English and Canadian French addresses will be supported; they differ from American English addresses by supporting the unit before the street number (i.e. 2-123 Main St rather than 123 Main St, Unit 2), and putting a comma after the street number and before the street type in French (i.e. 2-123, rue Principale). There is no configuration options provided: when these locales are active, their address style will be used, otherwise the default American English one will be used. To include address parsing support for more locales, contact a provider on the Professional Services section.

Specifying the local to be used for address parsing is available to programs through the API by calling CRM_Core_BAO_Address:parseStreetAddress.

Currency and Monetary Display Formats

CiviCRM currently supports a single currency per site. The default currency is USD, but you can select the appropriate currency for your site under Global Settings.

You can also control the way that monetary values are displayed - both the number format and the arrangement of currency symbols relative to the amount.

The 'look' of the numeric value (amount) depends on the currency settings on the Administer » Configure » Global Settings » Localization page; you can directly provide thousands separator (US default: comma) and decimal delimiter (US default: dot).

Tip

The format of the complete monetary display (whether to write the currency before or after the amount, whether to use currency symbols like $, £ and € or use the ISO 4217 codes, whether to put space between the currency and the amount) can be controlled with the Monetary Display option:

Bloc de code
titleDefault (US) Monetary Display
%c %a

The meaning of the % symbols is as follows:

  • %c - currency symbol ('$'),
  • %C - currency ISO code ('USD'),
  • %a - monetary amount, formatted according to selected Monetary Locale.

To modify Currency settings:

  1. Login to CiviCRM (as a user with "administer CiviCRM permissions").
  2. Go to Administer » Configure » Global Settings » Localization
  3. Update the corresponding fields in the Language and Currency section as needed and Save your changes.

Helping with CiviCRM Localisations

If your language is not yet supported, you can take the matter into your own hands and create a new translation. CiviCRM's web-based translation tool does not require any special technical skills, and even allows a number of different people and organizations to collaborate on a translation project.

How it Works

CiviCRM localisation uses the standard OpenSource gettext approach. This means that all of the localisable strings (pieces of text) appearing anywhere in CiviCRM are kept in 'POT' files, which serve as 'templates' for different 'PO' files - one set of such files for every language. This way, the fact that CiviCRM is localised into a given language is equivalent to the fact that there exists a set of 'PO' files for the language in question.

Translating CiviCRM's Drupal Menu Items

Among the various POT files there's a drupal-civicrm.pot file (and its derived drupal-civicrm.po files, as well). This file contains a couple of strings that are Drupal-specific.

If you'd like to have the Drupal's CiviCRM menu items localised, simply enable the locale module in Drupal's administration interface, add your language in the localization section and import the relevant drupal-civicrm.po file there.

Web-based Localisation

The easiest way to translate CiviCRM is via our Transifex project.

Using available open source GetText tools, you can also download, compile and install a new or updated translation from the translation server using the following steps:

  1. Create a subdirectory in your CiviCRM installation under the l10n directory, named with the locale code for your translation (e.g. xx_YY).
  2. Download translated file from our GitHub repository.
  3. Compile the PO files into an MO file (civicrm.mo) using one of the compile tools / commands below.
  4. After compiling, you should have an l10n/xx_XX/civicrm.mo file. If you then select the proper language under Administer » Configure » Global Settings » Localization, the strings should start being translated.
    Info
    titleCompiling the Translation File

    If you have a Linux or Mac OS X box, running the command
    `msgcat *.po | msgfmt -o civicrm.mo -` should do the trick.
    On Windows, you can download the gettext tools here:
    http://gnuwin32.sourceforge.net/packages/gettext.htm
    If you have problems compiling your translation, feel free to contact us for assistance - we can easily compile the file for you.

Offline Translation

If you prefer to translate CiviCRM on your local computer, you can do this by downloading (from our GitHub repository) the right PO files for your language. If your language's PO files are not generated, you can download the POT templates and generate the proper PO files, or ask us to do it for you (or go to Transifex and add a new language team there).

Once you have the proper PO files, you can use any standard Gettext tool to translate the contents (or edit it with any simple text editor). The most popular translation tools are:

After translating/updating the translation, you will need to compile it and place it in the appropriate directory of your installation (procedures in the preceding section). Also, please send a copy of the file to us, so we can include it in CiviCRM. If possible, please keep the file encoded in UTF-8 charset.

Localisation Forum

If you'd like to do any work on CiviCRM localisation or have any feedback you'd like to share with us, it would be great if you joined our forum and checked out "Internationalization and Localization" forum board: http://forum.civicrm.org/index.php/board,10.0.html


Creative Commons License
Except where otherwise noted, content on this site is licensed under a Creative Commons Attribution-Share Alike 3.0 United States Licence.