I don't think we need to commit the po files here at all.

When testing the latest l10n_server packaging features, I've seen this nice surprise: Install profile packaging

What I think we need is to create that file on the server so it can be downloaded with drush make and become part of this install package.

Drush make should already work with something like the following lines, so maybe all we need is the localize.drupal.org server to be whitelisted for downloading files into install profiles (?)

Note: For drush make to work the files must be contained in a folder inside the tar.gz so I've repackaged it, check out https://translate.openatrium.com/sites/translate.openatrium.com/files/dr...

; Translations for openatrium install profile
libraries[translations][download][type] = "get"
libraries[translations][download][url] = "https://translate.openatrium.com/sites/translate.openatrium.com/files/drupal-installer.tar.gz"
libraries[translations][directory_name] = "translations"
libraries[translations][destination] = .

Comments

gábor hojtsy’s picture

gábor hojtsy
he/him
Primary language Hungarian
Location Hungary
commented

We'll need a way to export .po files to the filesystem on ftp.drupal.org. I think the main obstacle is file naming again :) Ie. we need an installer .po for every project per every language. So that would double the number of .po files basically on ftp.drupal.org. Drush could grab the .po files needed for a given install profile (by looking at the list of modules), and append those .po files for the install profile directory. That is how I see it. But doubling the number of .po files for this is a bit scary.

jose reyero’s picture

jose reyero commented

I think what we need here is some translations support into 'drush make'. It can work like this:

- We mark all the installer strings in the regular po files as *INSTALLER* or something like that.
- Drush make fetches all the po files, takes out the installer string ones and builds a profile/*/translations/xx.po for each language.

If we could make drush make translation aware, it could also package all module translations in the tar.gz, not just the profile ones. Then maybe we could save a lot of 'Drupal My Language install profile'.

What if we could provide a just English download and a multilingual one for every install profile? On one side profile downloads would get bigger, but on the other side we'd save thousands of single file downloads from the translation server.

Anyway, I think just having an installer profile for all languages and Drupal core would be a big step forward, so it would be interesting just uploading the core installer to the server, even if it needs a monthly manual update. That can be packaged by drush make right away.