Most of us know the drill - write the app, crank out the code and localize later. Thinking about localizing your iOS app up front will save you tons of time later. I'll also talk about a great project that can help you put translation into the hands of your users.
4. What Is the Point?
• Language
• Culture
• Conventions
• Legal
5. Sounds hard.
• It can be difficult
• It’s not as easy as
translate.google.com
• It can pay off big
6. Why Localize?
• Opens up markets for your product(s)
• Apple gives “free” insertion into
localized App Stores
• Greater income
• Your power users = your translators
7. When do I start?
• From day one
• Existing application
8. What do I localize?
• Strings
• Numbers
• Dates
• Images
• Layouts
16. Looks can be deceiving
• Keys are unique to each strings file
• Don’t overload!
• UTF-16 plays hell with email
• Use the comments properly
• Positional parameters
17. Comparing & Sorting
• A a B b C c D d = English
• a, A, b, B, c, C, ä, Ä = Swedish
• Called collation
• -compare: is wrong
• Use -localizedStandardCompare:
35. Layouts
• Words can be different lengths in
another language
• Mac OS X has autolayouts
• iOS may “some day” have autolayout
• [UIBarButtonItem possibleTitles]
36. ibtool
• Separate NIBs for each locale
• Don’t make layout changes in localespecific NIB!
• Programmatically move items
• Wait until iOS 6...