Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I have found two ways to enable localization for iOS project:
I have read up so much about both the methodologies, even I have tried both the ways. But which one should be better to use and why? Please guide me.
The first choice is the right way to do.
The number 1 reason is, not all languages are of same length.
German is usually a “wider” language than English whereas Chinese is a “narrower” language.
This means, if your UIButton measures 100px x 37px in English, it needs to be 130px x 37px in German and around 70px X 37px for the Chinese version. You don’t have this finer controls when creating a localized string files. The downside is, if you are editing a XIB (like adding another button) you have to add it to all the XIBs. The workaround is to design one XIB to cater to the widest language and use localized string files, but then, your UI will not look polished. So at the end it boils down to a “polished UI for the user” vs “extra development time” and you have to make that decision.
Secondly, some languages like arabic are right to left and you have to customize the layout of the XIB to reflect that. (May be if it is a form, UILabel go on right and UITextFields on left?)