Hello!
When creating a new CocoaTouch/iOS project Xcode sets the development language to english. As we have usually clients from Germany I then add German (and maybe more languages) and change the development language to "Germany". So I would expect exported language files will use german as reference language.
But on "General" tab of project settings it still reads "Englisch - Development Language". And when I do "Export for Localization..." Xcode only gives me the following to optinos:
- "Existing translation" with "German"
- "Development Language Only"
The former one results in a .xliff file that has "en" as source-language and "de" as target-language set. The latter produces a .xliff file with no target-language and source-language "en".
Steps to Reproduce:
1. Setup a new project in Xcode
2. Add a new languages (e.g. German and French) in projects "General" tab
3. Select Info.plist and choose one (e.g. Germany) of the newly added languages as "Localization native development region"
4. Go back to projects "General" tab and see what is the current Development Language AND/OR export localization file.
Tried restarting Xcode. Tried changing the language of my MacBook Pro (which I have set to English usually) to German and restarting it before setting up a new project.
Xcode (at least): 6.3.2 until 7.1-beta
OS X (at least): 10.10.3 to 10.10.5
This is a huge drawback for us, as every non-english project's translation produces a lot of overhead. First in getting the localization file (.xliff) right for the translator(s). And then again before being able to import them in Xcode again. In both cases a lot of search-n-replace and fiddeling with source and target languages in the XML is necessary. Which makes it time consuming and error prone.
As I couldn't find any one complaining about the same problem, and only a few about native development region problems in general, I assume that either this is a kind of "special" use-case or we do something wrong here.
I filed a bug report (21342263) to apple's bugreporter, which was closed 6 days afterwards and marked as duplicate of 16759779 - which is still "open". Unfortunatly no-one at Apple bothered to give any hints on workarounds, or possible solutions. Neither am I able to see/get more information about bug report 16759779.
Does anyone here has an idea how we might get this right?
Thanks a lot in advance!
All the best,
Gabriel