Describes how to manage Drupal interface translation the way we do at LimoenGroen.

1. November 6, 2020
By: Erik Stielstra
Managing Interface Translations

2. Erik Stielstra
Sr Drupal Developer & Mentor
Contrib and Drupal 8 core development
Created the D8 interface translation
@Sutharsan

3. Managing Interface Translations
• Basic principles
• The 3 types of translatable strings
• Questions & Answers
Article
https://medium.com/limoengroen/how-to-deploy-drupal-interface-t
ranslations-5653294c4af6

4. Basic principles
• Developer centric workflow
• We prefer editing files over GUI
• All translation files (.po) are stored in git *
• All UI strings in custom code and theme are translatable.

5. 3 sources of translatable strings
• Strings in core and contrib modules
• Strings in custom modules and theme
• Custom translations that override the others

6. 1. Translate core and contrib strings

7. Translate core and contrib strings
Enable
module
Download
gettext
Save file
Import
translations
Add file
to Git
Interface Translation module

8. Translate core and contrib strings
Developer
• Download and import module translations (drush 9+):
drush pm:enable extra_field
• Add translations to Git:
git add ../translations

9. Translate core and contrib strings
Stage
• Import translations from file:
drush locale:check
drush locale:update

10. Translate core and contrib strings
Interface Translation settings
• Never check for updates
• Only use local translation source
• Only overwrite imported translations
• Translations directory outside of drupal root:
../translations
Development config override
• Use local _and remote_ translation source
$config['locale.settings']['translation']['use_source']
= 'remote_and_local';

12. 2. Translate custom code and theme strings

13. Translate custom code and theme strings
Custom code
Export with
potx module
Import
translations
Add file
to Git
Make
po file

14. Translate custom code and theme strings
Developer
• Create translation file (manually or with potx):
example/translations/example.nl.po
• Import translation to verify:
drush locale:check
drush locale:update
• Add translations to Git:
git add modules/custom/example/translations

15. Translate custom code and theme strings
Files
• Added to example.info.yml
interface translation project: example
interface translation server pattern:
modules/custom/%project/translations/%project.%language.po
• Translation file
modules/custom/example/translations/example.nl.po

16. Translate custom code and theme strings
Stage
• Import translations from file
drush locale:check
drush locale:update

17. 3. Translations that override the others

18. Translations that override the others
Export with
potx module
Import
translations
Add file
to Git
Make
po file

19. Translations that override the others
Developer
• Create translation file:
../translations/custom-translations.{langcode}.po
• Import translation to verify: drush locale (drush 9.5+):
drush locale:import nl
../translations/custom-translations.nl.po
--type=customized --override=all
• Add translations to Git:
git add translations/custom-translations.*

20. Translations that override the others
Stage
Import custom translations from file to override other
translations (drush 9.5+):
drush locale:import nl
../translations/custom-translations.nl.po
--type=customized --override=all

21. Questions

22. If you don't want to store translations in git
• Use https://github.com/drupal-composer/drupal-l10n
• Use local source in dev (do not override in settings.php)

23. How to deploy Drupal interface translations
https://medium.com/limoengroen/how-to-deploy-dr
upal-interface-translations-5653294c4af6

24. Image attributions
• DrupalJam 2008 by Bert Boerland; CC by-nc-sa 2.0
• DrupalJam 2010 by Boris Doesborg; CC by-nc-sa 2.0
• DrupalJam 2011 by Gerard Mourits; CC by 2.0
• DrupalJam 2014 by Daniël Smidt; CC by-nc-sa 2.0

25. Managing Interface Translations
Slides online:
https://www.slideshare.net/LimoenGroen/managing-drupal-interface-translation
License:
https://creativecommons.org/licenses/by-nc-sa/2.0/