Branded Oomph apps support full localisation, as provided by iOS. This applies to most user facing UI text, but may not apply to some images or content generated dynamically from the Oomph server.
Oomph uses the standard iOS internationalisation & localisation support. For more information, see Apple's documentation on Internationalization and Localization.
Localising to Your Language
If you would like your Oomph app localised in your language, please contact your Account Manager or firstname.lastname@example.org.
You will need to provide:
A translated version of Localizable.strings in your language.
A translated version of the help screens, for portrait & landscape orientation.
You must also ensure that when you add metadata to your app (issue title, description, etc.) it is localised in your language.
Please note that some UI elements cannot be localised at this point, as they are provided by Oomph servers (for example, the feedback screen).
Localisation in Oomph works by using the system configured locale to load the appropriate language translations. For example, a user with an iPad set to use French as their language would see French translations for all user interface elements. By default Oomph is localised in Australian English (very similar to British English).
The Localizable.strings file is a simple text file which can be edited with any text editor (vi, emacs, TextMate, TextEdit, TextPad, Notepad, etc.). It consists of keys & values in the following form:
“Key” = “Value”;
The key shows you an English description of the piece of text, the value is the translation of that phrase into the target language. Each of the keys and values are enclosed in double quotes and terminated with a semicolon.
To provide a translation, translate the key into the target language and replace the existing value. So for example the Dutch translation of “Favourites” might be written as:
“Favourites” = “Favorieten”;
Some values contain places where other text is substituted when the app is running (substitution characters). For example, when in QA mode the following text is displayed at the top of the screen to highlight the version of the app that is running:
App Magdata Version : 11 App Store Magdata Version : 12
12 are dynamic. The line for this in the localisation file looks as follows:
“App Magdata Version : %d \nApp Store Magdata Version : %d” = “App Magdata Version : %d \nApp Store Magdata Version : %d”;
Where these substitution characters exist in a value, you should leave them in place when providing a translation. They must exist in the translated value provided, but it is up to you to ensure they are placed in the location that makes grammatical sense in the target language.
Substitution characters might include:
\n - Newline character. \t - Tab character. %d - Decimal number. %@ - Text.