Closed (fixed)
Project:
Localization server
Version:
5.x-1.0-alpha3
Component:
Code
Priority:
Critical
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
7 Mar 2008 at 23:29 UTC
Updated:
19 Jan 2010 at 14:25 UTC
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
Comment #1
hass commentedI 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.
Comment #2
hass commentedComment #3
meba commentedhass, can you please check with 6.x-dev version of l10n_server?
Comment #4
gábor hojtsyDid not seem to happen in recent versions.
Comment #5
hass commentedI have never tested this again... have you?
Comment #6
gábor hojtsy@hass: an error that nobody else reported in a year can safely considered to not reoccur IMHO.
Comment #7
hass commentedNot if the code have not changed.
Comment #8
gábor hojtsy@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.