Mis-identification of the base language

[hotdang-ca]

As far as I can tell, my project's base language is English. However, when I Generate/Update Strings files, new strings are inserted into some other language (in this case, de-AT, though it has also and randomly selected pt).

My OneSky Project Properties does correctly have Base Language set to en, as well as having it specified in ~/Library/Application Support/OneSky/OneSkyProperties.plist

If I then upload Upload Files from this point, the one sky back-end does not receive these new strings (likely because they weren't in the base language), and i forget where in OneSky, but there is a warning/error issued regarding the string in de-AT, but not in the base language.

BUT... if I move those new strings inserted into de-AT, and move them to en, and then Upload Strings, this works correctly, and I see the new strings ready for translation on OneSky.

If i were to fathom a guess... $objects is an array, for which index 8 has the base language, as opposed to a dictionary specifying that value. I presume this is an open-source plugin, and I can try to fix by submitting a pull request?

[bretdabaker]

Hi, sorry the project is not open-source at the moment.

The OneSkyProperties.plist is actually the NSKeyedArchiver cache of project settings objects OSProject, the array is managed by the archiver/unarchiver, so it's not related to the problem.

Does it happen every time you Generate/Update Strings Files or it only happens the first time? Can you create a simple project that can reproduce the problem?

Thanks for your time!

[hotdang-ca]

Hi, same issue happening, but I'm not sure the Sample Project file itself will help you diagnose.

In this case, it dumps the new strings into the filipino language.

Steps to reproduce:
HEAD should have a new word to be localized and uploaded to one sky. Base language is EN. OneSky is configured to use EN as the base language. Generate Strings -> strings get dumped into some other language other than the base language.

Note:
Maybe it's the way I work... I start with english, I have an already established list of Strings for english, I add translations which then copy the english words in to their own localizable.strings file... then OneSky->Upload (never the XIBs..), then do translations, and later OneSky->Download, and sometime later generate new strings, and repeat.

[bretdabaker]

Thanks, will try out the sample projects soon.

[bretdabaker]

Fixed in 1.8.6