App localization starts with pinpointing your target locations and languages. If a company knows of a geographic region with a potentially rich market for their goods/services, app localization can help connect them with this demographic. Identify the language, country and locale to begin the localization process
Designing for localization begins with knowing what you’ll need to support apps, like vocabulary, character spaces, left-to-right or right-to-left configuration, script necessities or wrapping constraints. One set, no more, of flexible and generous layouts is your foundation. Make sure text strings don’t go outside the borders.
Ideally, app localization uses just one layout set for all languages.
Getting Flexible
In some cases, one set won’t do, but try designing alternative layouts only when there’s no other option. Many app localization pros use alternative layouts just for languages. More layouts mean more maintenance in the long haul. Make sure right to left (RTL) and left to right (LTR) texts/layouts are equally supported. Some platforms make this easier, like Android, which introduced complete native support for RTL layouts in their 4.2 model.
Details like numbers, dates, currencies and time can vary in layout by locale, but ensure that system-offered formats are used (steer clear of app-specific formatting). Not every location will use a period in their currency, for example. Some use commas or other characters.
When assumptions are made in app localization, just like anywhere else in life, mistakes can be made. App localization involves an incredible amount of research for something as seemingly simple as knowing how an area’s basic accounting is displayed.
String Management
User interface (UI) strings must be well managed and transparent. As apps are built, avoid hard coding and dub all strings resources in a default .xml file. This makes it simpler to localize, manage and update. These strings can be taken out, translated or changed, and then put back in with the right qualifiers without shifting any code.
Get strings ready for professional translation by making sure their formatting is consistent and correct, get rid of unused strings, put comments directly into the file to cite the original version and owner, and make note of any current translations.
You should also identify resources like drawables that need to be translated. Whether or not app store listings should be translated, such as descriptions and titles, is up to you and depends largely on how well the original materials would be received in your target locale.
Finally, when preparing the translator’s package, make sure to include a terminology list for any industry-specific words or phrases which are unique to your product/company. App localization is a team effort — call Verbatim Solutions today to get the right professionals on your side.
