This bug is against the version of Localization server used on http://localize.drupal.org/
Just some background info first: I translate Drupal core for Norwegian Bokmål using export/import and the excellent PO editor Virtaal. The last fact is important because the Translation Memory in Virtaal can "prove" that I have translated a string earlier - 100% match.
The last weeks I have been exporting just the strings for Drupal core 7.0-alpha7. Then Drupal 7.0-beta1 was added and two things happened:
1) My translation stats when down - I had fewer translated string reported on http://localize.drupal.org/translate/languages/nb
2) Strings that I know I had already translated were suddenly untranslated. (I can provide a list with some of the strings.)
This is a severe issue. Please take some time and test this properly before updating any more modules so no more translations are lost.
PS! Two days ago I told another Norwegian translator that he was wrong when he claimed that translated strings had disappeared in his Norwegian Bokmål translation of the Quiz module. He was probably correct after all. Ref http://localize.drupal.org/node/2004 (It's in Norwegian, but maybe Google translate can help.)
Comments
Comment #1
gábor hojtsyIf you can provide some example strings, that would be really helpful in trying to track this down. The editing UI has string ID information as well for strings, which would be even better to know so I can quickly look these up (explained here: http://localize.drupal.org/node/1854)
Comment #2
hansfn commentedOK, here are three strings I translated for 7.0-alpha7 before 7.0-beta1 was uploaded:
http://localize.drupal.org/translate/languages/nb/translate?sid=352864
http://localize.drupal.org/translate/languages/nb/translate?sid=352866 (updated link)
http://localize.drupal.org/translate/languages/nb/translate?sid=352868
I could contact the Quiz module translator too and check if he remembers some specific strings.
Thx for the quick response.
PS! They are of course translated now because I retranslated them tonight (and imported the po file as usual).
Comment #3
gábor hojtsyOk, do you have examples, where you did not fix this yet? If you fix it for your self, I cannot look at the state of the database where it is broken, so no way to look at what might happen.
Comment #4
hansfn commentedArgh. That was stupid of me - I kind of thought you kept the history for each string in the database ... I have looked through the file and couldn't find any unfixed examples.
I'll report back if this happens again. Maybe some other translators experiences the same and can add to this issue.
Comment #5
gábor hojtsyWe do store the history of strings in terms of what other translations were available previously. Since you say the UI showed there was no translation yet (and looks like the DB has no historical translation strings for this either), we only have one record:
I've looked at the alpha7 .po file export downloadable from http://ftp.drupal.org/files/translations/7.x/drupal/drupal-7.0-alpha7.nb.po which was generated hours before the beta1 release was available on drupal.org. That does not contain the two strings you've linked either (your 2. and 3. links are the same string). So I'm not sure what kind of proof we have at all that these were available on localize.drupal.org and not only on your own machine.
Comment #6
hansfn commentedOK, then the conclusion must be that I'm wrong (even though I was 99% sure). That is of course the best since there is no bug.
Sorry for wasting your time (and mine).
Comment #7
gábor hojtsyOk, let's reopen if you find other cases, please.