Need to include multiple languages in your App?

Publishing an app to the iTunes App Store opens your work to the world and markets beyond your region.  

Currently the world has over 6,000 spoken languages. Catering for one or more of these languages may encourage the download/purchase of your app. Multiple language support within your app should be on your radar for implementation. 

Oomph is the leading multiple language app publishing platform. Oomph provides in-built support for multiple languages and regional dialects. A good example of language implementation in an Oomph app can be seen in the Cathay Pacific “Discovery” magazine. 

The illustrations below illustrate different language versions of “The Showman” section from the May 2013 Issue currently available for free download on the iTunes App Store



The English version of "The Showman" page

Chinese (Mandarin) version

Language selection interface

Language selection interface

By selecting a different language from the app interface the screen is refreshed and that language version displayed, this time in Chinese (Mandarin).

Not only do the pages reflect the language change but other features such as social sharing can also reflect the alternate language choices. 

The illustration below shows alternate email versions in both English and Chinese (Mandarin).

Alternate Language Emails

How does it work?

In Oomph, this feature is referred to as Content Localisation and, as described above, allows content to be provided in multiple languages, Oomph then renders the appropriate content based on the user's preference. This is identical to the way iOS apps are localised.

Localisation can not only be used to provide content in native language for your readers, but can also be used to tailor content for a local audience, for example to show American model on the cover of a car magazine for American readers, and a European one for German readers.

An important feature is that a single Issue can contain all available languages, this allows languages to be changed dynamically based on system settings or user override and negates the need to create multiple versions of you app.

How easy is it to implement in my app?

Adding multiple languages to your app is very flexible and straightforward. Let’s take a look at the Cathay Pacific example to see how it’s done.

The following illustration shows the folder assets for “The Showman” section of the Issue.

"The Showman" folder assets

This looks like a standard Oomph section folder with the P1-1.pdf in English. The important thing to note is the inclusion of the “zh” folder.  The zh folder contains the alternate language versions of the main pages.

"zh" folder assets

Before you produce your localised content, you should first produce the “base” or default content. This is the content that is shown if you do not provide a localisation for a particular language.  Note: You must provide base content, if you do not and only provide localised content, then the readers for whom you provide no localisations for will be shown no content!

After you've authored your base content, you can produce the localised versions. You place your localised content under the section you're localising. 

As you can see by the Cathay Pacific example the localised content is placed within a folder named “zh” which matches the language designator for Chinese defined by the International Organization for Standardization (ISO). If you wanted to support French as well you would create a set of localised content pages and place them in the section folder in a sub-folder called “fr”.

How do I create localised Social Sharing content?

As you can see there are three folders in the section folder called ShareEmail, ShareFacebook and ShareTwitter. Each of these widget folders contains base and localised content.  The example below shows the base content in the ShareEmail folder including a “zh” folder. The zh folder contains a similar collection of assets in the Chinese language. 

"zh" ShareEmail assets

The comparison illustration below shows the English body.html file and the Chinese body.html file (the Chinese version located within the zh folder)

English and Chinese (Mandarin) .html pages

So once again create your base content for any Oomph widget, export it to the relevant folder. Create your localised version and then save it into the widget folder under the language designator.

More Information

For more information visit the Ommph website at and download the free Oomph Viewer app at

Tony Redhead

93 Maud Street, Unley, SA, 5061, Australia