This page is for application designers who need to have their application interface translated into different languages.

Related pages:

• Translation Table
• Translate function
• Language
• Locale

What You Can Translate

When you need to deploy a PhixFlow application across sites in different countries, you can configure some text in the application to be displayed in a different language.

• Known issue:  when a user first logs into the application the menus are translated. If the user subsequently reloads the application, the menu options revert to the source language.

PhixFlow cannot translate:

• PhixFlow messages.
• Stream attributes in analysis models.
• The data in the stream.
• Layout component dynamic text, because this displays data from the stream.
• Grid view → Basic Settings → Name. This appears as the title of the grid when it appears in a layout or dashboard.
• In a grid view → attribute action → tooltip: if this includes the action display name, it is not translated.
• Number formats. 

What PhixFlow Does to Translate Text

Translation works as follows:

1. The user opens your application
2. PhixFlow checks the user's locale.
3. For the source text in any translatable fields in the application interface, PhixFlow checks in the translation table.
4. PhixFlow finds entry code text that exactly matches the text in the interface.
5. PhixFlow matches the user's locale language to one of the translation cells.
6. PhixFlow displays the translation text for that language instead of the source text.

PhixFlow displays the source text if it cannot find any translation. This may be because:

• no translation text is defined
• the language is not present in the translation table
• the exactly matching text is not present as an entry code
• no translation table has been set up for the application.

How to Configure Translation

Set up Languages and Locales

PhixFlow is supplied with a set of languages. These populate the drop-down lists in locales and in the translation table. If you have administration privileges, you can add more languages in the repository. You cannot add languages to applications.

If the language you need is not already listed in the Translation table, add the language to the Full Repository. You cannot set up specific languages for the application. 

Can you use the Locales set for the system or copy them into your repository?

Add the locales to your application - or use an existing one?

1. In the application repository, right-click Locale and  Add Locale.
2. Enter a name for the Locale, and select a language from the Language Name drop-down list.

You can only delete a language from the repository when it is no longer used by any Locale.

Configuring Translation

Text Strings 

It is important to be consistent in capitalisation and to minimise the strings, as you need to create entries that pair the text to all the translations.

An application is able to translate text using the information in its translation table. The table contains a list of whole text strings which must exactly match those used in the application.

For each text string you must add the translation for each language you want to support. 

It is not possible to break the strings into substrings or translation. For example, you must translate  ‘First Name’ and ‘Family Name’ separately, rather than creating translation strings for 'first', 'family' and 'name'.

Create and populate the translation table

1. In the application repository, right-click Translation Table and click  Add.
2. In Basic Settings → Name, add a name.
3. In Translation Entries, add entry codes for each string that you need to translate.
4. Click  Add to open a New Translation Entry properties tab. Set:
   1. Basic Settings → Entry Code: the string that is to be translated - exactly matching how it appears in the interface.
   2. Translation Cell: add an entry for each language the string will be translated into (how?) and set:
      • Translation String to the translated version
      • Language Name to the language

Date Time Formats

Depending on a user's locale, PhixFlow can change the way it displays dates and times. The mappings are expressed using dd/MM/yyyy strings. If you want to translate month names or abbreviations, such as "January" is not translated to  "Janvier", "Jan" is not translated to "Janv", use text string translation. 

Step 1.  Create a date-time format

1. In the application repository, right-click Date Time Formats and click  Add.
2. In Basic Settings, set:
   • Name, add a name. Consider relating the name to the locale.
   • Date Time Format String: use d, M, y, H, m and s to specify the format - link to relevant page on dddmmm etc
     If you do not configure any mappings, PhixFlow uses this format to display date-times for all locales.

Step 2.  Map the format to alternative formats for each locale

1. For each locale, add a Date Style Mapping.
2. Click  Add to open a New Date Style Mapping tab. Set:
   • Date Format: use d, M, y, H, m and s to specify the format you want to use for the locale, for example dd/MM/yyyy or dd-MM-yy HH:mm:ss.
   • Date Style Name: the Date Style you created for the Locale 
     I cannot add the name and I cannot save the mapping
3. Click  OK to save and close the properties tab.

Step 3.  Add the Date Time Format to your Locale

1. In the application repository, open the locale for your application.
2. In Basic Settings → Date Style Name, select the format you just created from the drop-down list.