As now Localization update does only fetch approved translation and is not importing suggestion when no translation have been approved.

On http://localize.drupal.org/translate/languages/XX/export it's now possible to export suggestions if you choose 'include suggestions (as fuzzy if untranslated, in comment if translated)' but you need to do it project by project.

On a project like Drupal Commons it can take a very long time.

The module Localization update is a great help as you can fetch the translation from the localize server.

But if you are not importing the existing translation you are missing as much as 33% of the available translation.

It would be nice to speedup the process.

In French we have a 1/3 of translation not yet been validate.
10310 strings to validate : http://localize.drupal.org/translate/languages/fr/translate?page=1031&pr...
24700 strings validated : http://localize.drupal.org/translate/languages/fr/translate?page=2470&pr...

So we could focus on the 202040 strings awaiting to be translated
http://localize.drupal.org/translate/languages/fr/translate?page=20204&p...

Comments

gábor hojtsy’s picture

gábor hojtsy
he/him
Primary language Hungarian
Location Hungary
commented
Status: Active » Closed (works as designed)

I think the server should provide better tools to help admins approve strings, and admins should understand that only approved strings appear for users. Using dynamic PHP to export .po files is a no-go, and we had that explicit reason that we went with periodic static file export from localize.drupal.org.