If i export into one single file i have one missing string in a project. If i edit the translation it is displayed under the project and project version correctly...

Comments

hass’s picture

Title: Missing strings in exports if version string is missing » One or more missing strings in export

I think i found the cause of this... i don't have a version tag in all files... then i see in DB "n/a". This is really very bad... we have many many projects without version tags in files or defective version tags. Additional i cannot fix this for older project versions now, isn't it?

So the only possible and manual workaround looks like (untested) and will not work on d.o:

1. run potx on the extracted project release files to get an .pot file
2. export translation with "all" revisions to get all translated strings out of l10n_server
3. only select "export in ONE file" - all other options are broken, too
4. Then i have tooo much strings in the .po
5. update the .po file with poedit and the created .pot file (hopefully without any duplicate error from buggy .po extraction - or i'm lost)
6. delete outdated strings in poedit

Nevertheless i'm not sure if this is the full truth.

hass’s picture

Title: One or more missing strings in export » Missing strings in exports if version string is missing
Priority: Normal » Critical
meba’s picture

Title: One or more missing strings in export » Missing strings in exports if version string is missing
Status: Active » Postponed (maintainer needs more info)

hass, can you please check with 6.x-dev version of l10n_server?

gábor hojtsy’s picture

Status: Postponed (maintainer needs more info) » Closed (fixed)

Did not seem to happen in recent versions.

hass’s picture

I have never tested this again... have you?

gábor hojtsy’s picture

@hass: an error that nobody else reported in a year can safely considered to not reoccur IMHO.

hass’s picture

Not if the code have not changed.

gábor hojtsy’s picture

@hass: we've received multiple reports of missing strings in the past months and it was never related to missing version strings. Also, this module was in use on numerous of sites (consistently around 100 in the past year - see http://drupal.org/project/usage/l10n_server), and nobody else reported this issue, so it is unlikely it persisted.