po files list line number multiple times

How does the package gets reparsed?

Probably, I receive the same error: http://drupal.org/node/206126

Doh, just found out that there was a $fid value used in extractor.inc's l10n_community_save_string(), which was never initialized. So all reparsed releases had their lines stored all again, and again. Doh. Now hopefully fixed with this change:

http://cvs.drupal.org/viewvc.py/drupal/contributions/modules/l10n_server...

Note however that reparsing stuff still keeps old occurrences of strings, so strings removed in the new version will not get removed, and strings moved lines in the new version will get their old and new line numbers stored as well. This is either bad or by design. If we just remove the file/line information when reparsing a package, it could easily lead to data loss if the new package is not properly parseable. The reparsing "feature" is in itself a development feature by nature. The drupal.org install will parse alpha, beta, rc versions (depending on setup), but not nightly development versions, as parsing all nightly development versions again and again each day would add a *huuuuge* data overhead to this system. So this module will only parse fixed code bases, which are not modifiable, and therefore do not require reparsing.

2 Gábor Hojtsy - I can remove data it SQL http://drupal.org/node/203658 ? Lines will be taken again correctly.
Thanks

Sure, feel free to remove file and line data in case you reparse the file again. Keep the strings and translations intact. **Always** make a backup first, in case anything goes wrong.

Can we reparse all modules from scratch without losing translations? Something like

TRUNCATE 'l10n_community_file';
TRUNCATE 'l10n_community_line';
TRUNCATE 'l10n_community_project';
TRUNCATE 'l10n_community_release';

And reparsing all projects?

Yes, the extractor picks up identifiers of existing source strings, so if you keep the source strings intact, it will add back the file and line information properly. Actually, there was only a problem with the line information, so you should be fine with just truncating the line table and reparsing all source packages. (The code notices that you already have that file recorded, so it should not add that twice, there was only a problem with the lines).

Again, always make a backup first!