I’d like to start out with some basic explanation of the i18n process when approached from an i OS developer’s point of view.
Lets get this out of the way to start – you want to be doing i18n/l10n (localization).
However the language has diverged so much between the two countries that i OS & OS X have a specific selection for Portugal Portuguese.
When this language selection is chosen (with Brazil as the selected region), NSLocale’s full string representation of the locale is outputted as , to see if that was the country code we were looking for.
Dallas wrote a similar post describing the i18n process he and his team went through on the Android application.NSLocale is one of those classes that you really need to get familiar with, as even though it’s function might seem simple (provide access to the system’s locale), it’s got a lot of moving parts.The first oddity is the class-level methods available: means if your user opens your app, backgrounds it, changes their locale in settings, and then comes back, your app will start getting the new locale changes immediately.Let’s take a look at the first major tripping point: i18n vs l10n.It’s almost hard to imagine one without the other, as internationalization and localization are really two sides of the same coin.