Game Language Translations

Translating your games to multiple languages broadens your audience.

The translation console is the central repository for all your strings. Any string that you want to have translated needs to be in there.

The translation console can be found in the developer console, inside one of your games under "Translations". You first need to register a game in the developer console before you can start adding translation string.

To add new translation strings, just follow the instructions in the translation console.

Once you have translation strings registered, you can select a language in the drop down and start to translate them. You can also add additional translators by email address to get some help with other languages. These translators can only suggest translations, but can not create or modify translation ids.

Anytime a translator or you changes a translation, you need to approve the suggestion before it goes to production. You can preview the changes with the "Preview" buttons.

Go to Developers Console

To use translations, you need to call the AirConsole constructor with the option translation: true

Once you have registered a string in the translation console, you can start using it inside your code. Assuming you have registered a string welcome_screen that has the English value "Welcome to our game", you can retrieve it using:

If the users language is English, it will return "Welcome to our game".

For static html translations you can use the data-translation attribute. This will automatically fill in your static translation:

This will result in:

Translation strings can use replacement parts. For example welcome_user could be have an English value of Hi %username%. To retrieve the translated string with the username filled in, you can call:

which would result in "Hi Tom".

Replacement parts can only be used in programatically and can not be used with the static html attribute data-translation.

You should never concatenate translation strings to build a sentence. Always use replacement parts instead. Different languages have different sentence structures.

You can also use your own translation system. A quiz for example could load different questions depending on the current language. To get the current language, call:

This could also be abused to load different images depending on the users language and therefor you could use graphics containing texts.

To enable translation functionality within your Unity project, do the following on your AirConsole Game Object:

You can see the translation functionality in action in the 'translations' example scene that you can find in your plugin under Assets/AirConsole/examples/translations.

The example scene uses a few pre-defined translation strings set up for the game ID com.airconsole.plugin.unity. You can request these for testing purposes, but you cannot edit them or add more.

Request an individual translation string by id:

Request a translation with replacement parts. The values have to be passed along as aDictionary <string, string >:

You can translate multiple UI Text or Text Mesh elements (without replacement values). For it to work, thetextproperty of the UI Text or Text Mesh needs to contain the translation ID string within double curly brackets:{{welcome_screen}}

The importing/exporting translations functionality simplifies the process of working with changes on many string IDs, whether creating a new one or editing the existing ones.

The import and export buttons can be found in the side menu.

Importing Translations

The import file must have the following structure:

This is an example of the import file:

You can download a template here.

When translations are imported, the following rules apply:

Exporting Translations

Translation languages

The AirConsole platform is currently translated into the following languages: Chinese, English, French, German, Indonesian, Italian, Japanese, Korean, Portuguese, Portuguese(Brazil), Spanish, Thai, and Ukrainian, but you can provide your game in many more languages.