Updating OS X XIB strings leads to overwriting existing translations with *source language*

[taoeffect]

Possibly related to #3082:

In Pootle 2.5.1, when updating a string in the XIB file, the key doesn't change, it stays the same. So for example, if it was previously this:

/* Class = "NSButtonCell"; title = "Button"; ObjectID = "67"; */
"67.title" = "Button";

And we change "Button" to say "Press Button":

/* Class = "NSButtonCell"; title = "Button"; ObjectID = "67"; */
"67.title" = "Press Button";

Then when this is uploaded to Pootle's templates (to overwrite the strings file there), and the localizers click "Update against templates", this new string will actually act as a TRANSLATION for that language!

You can see what's happened for our Polish translation:

It would work if this:

/* Class = "NSButtonCell"; title = "Button"; ObjectID = "67"; */
"Button" = "Button";

Was replaced with:

/* Class = "NSButtonCell"; title = "Button"; ObjectID = "67"; */
"Press Button" = "Press Button";

Our dev tried switching to xliff, but reported back:

"did a quick tests with xliff, and we have the same problem. the xliff format allows to define source and target language, but it seems that's ignored by pootle."

Maybe he made a mistake somewhere, but atm we're out of ideas on how to fix this. How do other developers handle this?

And most importantly, how to do we undo the damage done to the existing translations (which are almost finished, but are now on hold due to this problem)?

Many thanks for any and all help with this!

[jleclanche]

Could you attach (in a gist.github.com) some problematic text files the problem can be reproduced with?

[taoeffect]

Here's an example, using Chinese and English templates. It's the same example as the one pictured above ("Please keep me informed [...]"):

https://www.taoeffect.com/other/PootleProb.zip (strings exported directly from Pootle)

Thank you so much for looking into this! Please let me know if you need anything else.

[taoeffect]

P.S. I'm a developer (am good at what I do), so if there's any way I can help you fix this bug, please let me know. Feel free to contact me via email too: http://dns.dnschain.net/id/greg

I would be happy to work with you on this fix, I'm just unfamiliar with the Pootle codebase.

[jleclanche]

@taoeffect If you come in the #pootle channel and ping me (jleclanche) on Monday afternoon I can give you some tutoring. It'll be limited because I'm not too familiar with this part of the code either.

[taoeffect]

@jleclanche see you've received my ping. :)

[comradekingu]

@taoeffect Discussion is now in https://gitter.im/translate/pootle This is assumed to have been fixed if there is no reply.