WHAT TO CONSIDER
There are some simple yet very effective tricks to make sure you won't experience any unwanted surprises when having your apps localized. By keeping in mind these tips you will avoid unnecessary questions from localizers or even statements such as "these strings cannot be localized". Keep on reading to find out how to avoid the most common mistakes.
CONTEXT CONTEXT CONTEXT
This statement is valid for every aspect of the translation business but especially true when it comes to localization.
Provide as much context as possible to your translators and they will thank you with amazingly accurate and easy to understand translations.
The best way to do this is by handing out the app to be localized itself. By being able to browse through your app the translator can check where a string in placed on the interface and apply this knowledge to his/her localization. Want an example? Here it is:
We once localized a journaling app for iPad that contained a string called "Include Sidebar Photos". Well, without the app at hand, such a string could actually mean anything. Include photos where? What photos? Include in what? What sidebar? There‘s a bunch of questions popping up in a good translator‘s mind.
Luckily we had the app at hand, could start the app on our iPad and check where the string belongs. It turned out this was a setting when exporting your journal to other file formats to include photos you added to a sidebar for the journal entries.
If for some reasons you cannot provide a copy of your app, please make sure to label the key identifiers for the strings in such a way as to easily extract context information. A good key for the "Include Sidebar Photos" string would be "Include_sidebar_photos_export_option".
THE ARTICLE: SMALL YET ESSENTIAL
Did you expect that a tiny, one lettered word such as the indefinite article "a" could make such a mess in localization? If you weren‘t aware of this, let us assure you that you are not alone.
Always bear in mind that English can be quite a straight forward language, especially in dealing with articles such as "a" and "the". Other languages though, can be a bit more diverse. Let us show you an example:
The localizable.strings for a messenger app for iPhone included a string called "%@ has sent you a %@", whereas the former %@ represents the contact that sent something and the latter %@ represents the type of media such as a photo or video.
Here's how the strings would look like:
The problem: By separating the article "a" from the variable the developer rendered this string untranslatable for certain languages. Italian for example has different articles for video and photo (due to gender differences): una foto, but un video.
A simple yet effective solution: Always include the article into the variable. This way you account for languages that might use different articles for all the options of a variable. Look below and you will see how easy the translation of these strings can be when including the article into the variable.
