8. Translations

The mechanism of solution translations has changed in V7 of the software. Previously, a set of dashboards was translated separately and imported via a separate XML file. This resulted in multiple copies of the same dashboards, but just with translated Datafeeds, Datasets, Components and Dashboards

In this version, the translated terms are actually held against the original set of dashboards in the database. Let’s take for example the “Executive Summary” dashboard. There’s a component called “Top 20 Users” with a “Cost Centre” as the second data point.

The title of “Top 20 Users” is actually stored as a small JSON value in the database, where the English viewers of “en” will see “Top 20 Users”. Should that value be translated – via the change of the “Language” in the Users’ settings, a new locale code is generated for that code against that “Top 20 Users” title. For example, in the database for that component we’ll have a code of “en” with a corresponding value of “Cost Centre”, but when a French users signs in, their locale is “fr” and that components’ corresponding value is “Centre de Coûts”.

What this allows us to do is provide a singular set of dashboards for Intuitive for Print, but with multiple translations built into them. Changing the translation is as simple as changing the Users’ language via their User Settings. At the time of writing, the currently available languages built into the Intuitive for Print dashboards are English, French and German.

This flexibility also allows us to support multiple markets within a single language. If you refer to the module on “Organisations”, you are able to define a currency symbol for that customer. This means we can support multiple regions with one language against multiple currencies. For example, an English version of the dashboards but supporting the use of the currencies GBP (£), USD / AUD / NZD ($), ZAR (R) etc. Similarly, for French markets in either Euros or Dollars.