- Supported languages
- Requesting access
- Giving access
- List of translators
- How to translate content
- How to translate menu items
- How to translate Views configurations
- Technical notes
- Any language with over 20% translation on Transifex (c.f. new-official-language).
- Requested in the marketing channel by someone who also lurks in the translation channel, i.e. somewhat active, easy to contact, and who show interest in developing the CiviCRM community in a specific language.
- Region-specific translations (ex: en-CA, en-GB, en-AU, fr-CA) are possible, but should be considered a lower priority and should not monopolise webdev resources. It's not where we will make most of our growth.
@josh in the marketing channel.
- On the Drupal7 site, website admins can assign the 'translator' role to the Drupal account.
This must be done on the Drupal7 site first, because we synchronize accounts to the d8 site regularly, so the role would be lost if we added it to d8 only.
To save time, it's possible to also give the role on the d8 site manually. Otherwise the sync runs every 2 hours.
List of translators
How to translate content
Browse to a page to translate. Recommended examples are:
- Front page: https://d8.civicrm.org/home
- About: https://d8.civicrm.org/about (and other pages under 'about')
The page must be set to English, and not 'undefined'. The only way to tell is if there is not a "Translate" menu item available in the page header:
If you suspect that the language is not correctly set, ping an admin on Mattermost, such as josh or bgm.
Note that Drupal8 does not create a separate node for translations. They are all under the same "node ID" and we can only translate by going to the 'Translate' menu item, then selecting the correct language.
How to translate menu items
How to translate Views configurations
Currently Gutenberg requires that the translator role have the following permissions:
- Use the Gutenberg Blocks text format text format
- Administer Gutenberg
- View the administration theme