What is the difference between es and es-419 in iOS localization? - ios

I have been trying to implement Latin America Spanish language support and I am not supporting the Spanish variant of Spain. How do I separate these two? I thought, es is for Spain variant and es-419 for Latin America Variant. so I added es-419 but my localised string is showing up for es variant as well.

According to https://en.wikipedia.org/wiki/Language_code
es – Spanish, as shortest ISO 639 code.
es-419 – Spanish appropriate for the Latin America and Caribbean region, using the UN M.49 region code

I can't reproduce any issue.
Here's how I tested. I localized my app for English (the base) and for Spanish (Latin America), aka "es-419". I have a Localizable.strings file, and it exists in both localizations.
So:
if I run under English, I get my English string
if I run under Spanish (Latin America), I get my Spanish string
if I run under Spanish, I get my English string — and that is what I expect, as I am not localized for that dialect
So it seems to me that this works as expected. I'm not reproducing any issue as described by the OP.

I don't know about iOS localization but I think I can help clarify the problem
you see, the code es alone just refers to the Spanish language in general, it doesn't specify any variants.
the code for Spain variant of Spanish is es-es,
where the second "es" means Spain
so maybe you can see if your localised string is showing up for the es-es variant? if it doesn't then maybe the problem is solved :)

Related

Localization issue - specific x generic

This is my problem. I have this simplified chinese and spanish translations that I am about to add to my application. When adding these localizations to my app I am presented with a list of locales like
Simplified Chinese China
Simplified Chinese Macau
Simplified Chinese Hong Kong
Simplified Chinese Singapure
Traditional Chinese China
Traditional Chinese Macau
Traditional Chinese Hong Kong
Traditional Chinese Singapure
and I have also an option that is just Chinese.
The same happens to spanish, a lot of specific spanish options plus just spanish.
How does this work? I mean, is this option Chinese a kind of "wild card" that will work for all people speaking chinese, independently if their devices are set for tradidional or simplified in any country speaking chinese?
You can read all about the variations of Chinese here: Varieties of Chinese. Bottom line is that different variants relate to geography and geopolitics, so be careful and make sure the translation you are getting is one you want.
The situation is similar with Spanish. Plain ("es") is presumed to be European Spanish. See Spanish Dialects and Varieties for more info.
To your question, "ES" is generic, in the sense that it will be the fallback Spanish language on the device. If you only have a localization for ES, then that localization will be chosen whether you select "Spanish" or "Spanish (Mexico)". From linguistic standpoint, the common meaning for "ES" is European Spanish.
With Chinese, the story is a bit different. There is no generic Chinese to fall back to. If you intend to target mainland China, go for Chinese (Simplified). If you want to target Chinese population outside China, simplest choice is Chinese (Traditional).

iOS and OS X: When does Base localization take precedence?

Say you have a localized resource that is in en.lproj and Base.lproj. If someone runs the app in, say, Spanish, is the Base.proj resource loaded over the en.lproj one?
Generally, what happens when an resource for the user's preferred language is not found, and when does the system fall back to Base resources?
Base is used whenever the translation for the user language is not define. Including if you have done 99% of string transition to "French", and you should display one of this 1% left on a French iPhone => the base will be use.
I like to have base = english. If a user did not have is natural language translated, he will se the english version.
Some people think different. We all have our reason ;-)
They said, use "code" for base, if you miss to translate you will see code instead of english. Easy to "debug" missing translation.
I said, if you miss to translate a string, the user will see the english version. He will probably said "Oh no ! again this english ! This soft is not well translate !". I already be in that situation 1000 times may be more. Nethertheless, I was able to translate the english sentence to my natural language... not sure to be able to translate a "code"...
If none of your defined languages is not equal to the one which the user has its phone language, then the Base takes place.
Suppose you have 3 localizations, english, spanish and french, and of course you have your based localize. If french or spanish or english are not the phone language, then the base specified by you will be set.

Localisation issue (Welsh)

OK so I have been working on an app that will be available in multiple languages.
I have managed to get it working in the main languages, such as French, German, Spanish and English.
I have also now managed to get the app to use different regions within a language such as en_GB, en_US etc etc so all is good - thanks to this guide:
http://hamishrickerby.com/2010/07/23/iphone-ipad-localizations-regions/
One of the most important languages for me is Welsh. Apple allows me to set my iPhone to welsh by choosing British English as my language and region format as Welsh (United Kingdom).
I have created the Welsh language localisation within my app and translated my bits but I don't seem to be able to apply it.
My idea was that if the users language was set to British English that I could have a button on the main view that would allow the user to chose Welsh. Is this possible and what would be the best way to implement it.
Ideally if the user has already set their language to British english and has the region format to welsh they will get the welsh language version of the app just like the french would automatically get the french language version and the spanish will get the spanish version of the app etc but as most welsh speaking users will have their phone set to United Kingdom as they are not aware of the Welsh Region setting in iOS.
I would like the app to detect if the current language is British English and display a button on the home screen where the user can switch to Welsh Language. I have managed to display this button (only if user language is British English) but have no idea how to link it to change the language?
Anyone have any ideas or maybe a suggestion on the best way to implement my goal.
Thanks in advance.
Unfortunately, as you've identified, Welsh isn't a fully supported language on iOS. Until Apple supports it properly, you'll have to implement a bit of a workaround.
It seems as though the main solution is to have both English and Welsh .strings files (like you would with other languages), but manually load the required language, using
[[NSBundle mainBundle] localizedStringForKey:yourString value:#"" table:#"Welsh"];
#"Welsh" could be another language there, depending on what you want to load. You'll have to implement some control within your app so that users can change the language themselves. Check out the example project linked to in this blog post by translation company Applingua - it shows one way of encapsulating this code into a language provider class.

Can I convert my application to any language?

I am doing R & D on this Topic. How can I change any language of my application from English?
For example, My Application is in English and now I want to change it in to any local language like Hindi, Gujarati, Sanskrit. So is it possible with iPhone/iPad. If yes then please give me brief idea. I know the localization but don't know it support other languages or not?
The list of supported languages is listed here:
http://www.apple.com/iphone/specs.html
English (U.S.), English (UK), French (France), German, Traditional
Chinese, Simplified Chinese, Dutch, Italian, Spanish, Portuguese
(Brazil), Portuguese (Portugal), Danish, Swedish, Finnish, Norwegian,
Korean, Japanese, Russian, Polish, Turkish, Ukrainian, Hungarian,
Arabic, Thai, Czech, Greek, Hebrew, Indonesian, Malay, Romanian,
Slovak, Croatian, Catalan, and Vietnamese
Although this list changes with new OS releases.
For more information about localising an app, you should take a look at the Apple documentation:
http://developer.apple.com/library/ios/#documentation/MacOSX/Conceptual/BPInternational/BPInternational.html

Similar languages when submitting to Apple's AppStore

I am uploading a new App which is localized in 10 languages to the Apple AppStore.
Apple offers several languages with country specific options such as
Canadian French
Mexican Spanish
Brazilian Portuguese
We have set up localizations for French, Spanish and Portuguese.
On the iPhone, an App defaults to the closest language available. For example, an iPhone set to "Brazilian Portuguese" will use the regular Portuguese localization instead of the English default localization.
Is it the same on the AppStore? Do we need to also set "Mexican Spanish" or will customers from Mexico default to Spanish (instead of the defaulting to English)?
edit:
To clarify, this is not about whether we should localize to these dialects (we already decided against that when making the app), but whether the store page shown to the customer will be displayed in the closest dialect or english.
For example, will a Mexican user automatically see the Spanish version (the closest language) or the default language (English)?
I can confirm that the closest available language is selected by the App Store.
For example in the Mexican App Store if you have Spanish set up but not Mexican Spanish, Spanish will show up. This app has Spanish activated on iTunes but not Mexican Spanish and everything is in Spanish on the Mexican App Store.
https://itunes.apple.com/mx/app/id502222888
The language that is displayed on the App Store depends also on the user's language settings since they set the language query parameter. The URL format used by Apple with the language query parameter is:
https://itunes.apple.com/tw/app/id502222888?l=zh where tw is Taiwan and l=zh is the Chinese language.
The language query parameter is not always used.
For example in Germany, even if you set the another language via the query parameter it will be ignored and the German language will show up since it is the only language for that location:
https://itunes.apple.com/de/app/id502222888?l=fr
While in Canada that has both English or French, you can use the language query parameter:
https://itunes.apple.com/ca/app/id502222888?l=fr
To answer my own question: No, Apple does not automatically choose the closest language on the AppStore.
Here is an example of the Mexican AppStore using English despite standard Spanish being present:
Let's start with Spanish. As far as I know Spanish (Mexico) is considered International Spanish, which is fairly similar to English (USA).
I don't know about French, so I might be wrong here but I believe French (France) would be perfectly understandable by the Canadians.
As for Portuguese... Well, in this case you did something that I believe should be the other way round. I read on the Internet that Portuguese government (?) recently pass a reform so that regular Portuguese would be similar in terms of grammar with Brazilian Portuguese. You see as Brazil is much bigger country, Brazilian version is much more common. Therefore I don't think it is OK to use regular Portuguese in Brazil (there might be some problems) but it is probably just about right to use Brazilian Portuguese in Portugal.
There is also the case of Chinese. As in Simplified vs Traditional. If you ever going to localize your application into Chinese (not the easiest thing to do), Traditional is the one to be used in Hong Kong, Taiwan and Macao whereas Simplified is the one they use in China (mainland) as well as in Singapore.
It would be very inappropriate to confuse them (i.e. try to sell Simplified version to the Taiwanese).

Resources