Import multiple custom translation po files

[davidferlay]

Is your feature request related to a problem? Please describe.

• Drush already provides a command to import individual custom translation po files, such as :
  drush locale:import fr /var/www/html/translations/fr.po --type=customized --override=all
• This command requires to be duplicated when you want to import files for multiples languages, making things messy
• It also requires you to know for which languages you have translations files or not

Describe the solution you'd like

• Drush could provide a similar command to import multiple po files :

  • It would allow to streamline the process of importing custom translations on projects, regardless of enabled languages and available po files

• Proposal : drush locale:import:all $directory $options

  • The command would require files to be named with valid 2 char language code
  • It would take a directory path as argument
  • It would offer the same options (type + override)
  • it would import only translations for installed modules and enabled languages
  • It would import only updated and new translations

• Exemple : drush locale:import:all /var/www/html/translations/ --type=customized --override=all

Describe alternatives you've considered

• https://www.drupal.org/project/drush_language brings drush locale-import-all :
  • The feature seem critical enough to be brought by Drush itself rather than a contrib module
  • Most likely code of this module will be a good source of inspiration

[andypost]

On other hand it could be polished as "drush_language" and added to core as part of https://www.drupal.org/project/drupal/issues/2242947

[geek-merlin]

As a drush_language maintainer, i'll support any approach to move this to core, via drush or not. My gut feeling is that going drush and later core makes sense.

[davidferlay]

Tested locally, works perfectly with drush locale:import:all /var/www/html/translations/ --type=customized --override=all and similar commands, using po files like this one (to rename as .po).

PR was done from Drush version : 10.0.3-dev

• Drush provides new command drush locale:import:all $directory $options
• The command requires files to be named with valid 2 char language code
• It takes a directory path as argument
• It offers the same options (type + override)
• it imports only translations for installed modules and enabled languages
• It imports only updated and new translations

• Looks like some CI check need to be fixed

[davidferlay]

CI fixed!)

[davidferlay]

Any feedback @geek-merlin ? When PR is merged, we may backport it to drush 9 too btw

[ptmkenny]

Is there any way or plan to export custom translations as well via drush?