Localizations. Why I have to export the development language translation?

Question

Created Dec ’15

Replies 1

Boosts 0

Participants 2

Hi experts.

I am adding internationalization to my project. I am reading "Localizing Your App" at https://developer.apple.com/library/mac/documentation/MacOSX/Conceptual/BPInternational/LocalizingYourApp/LocalizingYourApp.html.

I cannot understand why my first step is to "export the development language". My development language is English. When I export it, 'en.xliff' file is created. This is OK. But I cannot import it. It does not contain 'target-language'.

To add new language, I just add a language and export it for localizations. When it is translated, I need to import it. That is clear.

Can anybody clarify why to export the development language?

Maybe I missed something.

Regards,

Valery.

Boost

Answer 1

bob133 OP

Dec ’15

Hi, Valery. The idea behind the XLIFF export/import feature is that you would create the app in your native language, then export it out so you can send the file to a translation company. They will take what you've written (the development language) and translate it into whatever language you're requesting, then give you back another XLIFF file for that language, and you can import that into your project. You wouldn't need to import anything for a language you already have in your project.

0