Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.Are we able to recycle older project translations from the tar.gz files on scanning?
Maybe import this strings as suggestion. But it would be heavy to review all this strings again. Fuzzy strings should be added as suggestion... However i know how problematic this could be - it would be cool if we recycle them automatically and do not make this by hand...
Comments
Comment #1
hass commentedWe need to make sure this auto import is only done AFTER core translation is imported... or we need a checkbox like "overwrite" all existing strings... i think - core should be more trust worthy then many modules.
Additional if this strings are imported and if there are collisions they should be marked as "Suggestion by: module-views.de.po" or something like this... so we could get an idea where this string comes from.
Comment #2
gábor hojtsyRecycling that way is not a bad idea, and adding as suggestion when it is different is already how it is. It gets complex if there are lots of .po files in the tar.gz and/or they are big (think Ubercart). We need a user account to associate these with.
Comment #3
gábor hojtsySo, in short:
- we need a user id to use for that, what user id should that be?
- it could take a long time, and it could halt in the middle (we are on Drupal 5 mainly due to Organic Groups, so no batch API... and we would not be able to use batch API on cron anyways)
Comment #4
hass commentedI think we should allow selecting an self assigned user account in configuration settings. This way an admin is able to create a dedicated user, name it, assign permission and assign this user as the default import user in l10n_server local packages settings. We cannot use user 1 and therefor we have a number that is higher... but we have no guaranty what userid this will become on existing sites.
I know, i know... i hope this will not happen, but maybe extract first, extract the raw strings on the first cron run and do the translation import on a second run!? I think a translation server site should run cron every 5 minutes or more often to get this all imported in a reasonable time frame.
Comment #5
gábor hojtsyThe imports are already happening manually, so this could interfere with existing processes quite a bit. The manual imports made it easier for moderators to approve translations, while automated imports would make it a huge task to just review text for incoming packages. Therefore, automated imports of .po files from packages is not on the plan.
Comment #6
hass commentedOnly for understanding - in past it was planed to package l10n_server translations into releases. Would this packaging keep the previous translation files in CVS and/or will there be any collision or not? Are existing translations in CVS going to be ignored?
Comment #7
gábor hojtsyWe will not commit files to CVS, and people will be discouraged (eventually banned) from committing translation files to CVS. The translation packages are separate from the module packages themselves. See some testing files at http://ftp.drupal.org/files/translations/