Making a Multilingual Qlik Sense App - Page 3 - Qlik Community

Jennell_McIntire · ‎2020-02-21

A colleague of mine had translated two demos from the Demo Site to Japanese and wanted to know if we could post them on the Demo Site alongside the English versions. We decided that it would be best to combine the English and Japanese versions into one multilingual Qlik Sense app making it easier for us to add additional languages to the app as needed. It was an easy process and required only a few steps:

Create a translation sheet with all the languages that will be available in the app
Update the script to add a table of the translations and a list of the languages available in the app
Add a Language filter pane to every sheet in the app that allows only one selected value
Update sheet names, chart titles, subtitles and labels with an expression that will display the text in the selected language

Create Translation Sheet

To begin the process of making a demo multilingual, I created an Excel file with all the languages that are to be included in the app. Below is a snippet of the worksheet. The first column, Index, has a unique value which will be used in the charts and expressions to indicate what data should be displayed. The second and third columns are the languages to be used in the app. An additional column can be added for additional languages that need to be added to the app. In this scenario, I entered all the English text (sheet names, chart titles and subtitles, labels and text) and then using the Japanese version of the app, I entered the respective Japanese text. If I did not have the Japanese version of the app, I would have shared the Excel file with someone who could enter the Japanese translations for me. Preparing the Excel file in this format makes it easy to add additional languages to the app without having to update the QVF.

Snippet of Excel translation sheet

Update the Script

Once the translation sheet was created, it needed to be loaded into the data model. The script below is what I added to the demo.

On line 1, the HidePrefix system variable is used to hide all fields that begin with “#.” Starting on line 3, the Excel file is loaded. Once it is loaded, the vLanguage variable is set to the expression “=Minstring(#LANGUAGE).” This is an important step and we will take a closer look at this when we update the front-end. On line 13, the languages from the Excel file are loaded - users can select the language they would like to view from this list. These languages are then stored in the #LANGUAGE field which will be hidden from the user (since it starts with “#”).

Add Language Filter

One each sheet in the app, I added a Language filter pane using the dimension #LANGUAGE that was created in the script. Once the script is reloaded with the HidePrefix variable, the #LANGUAGE field will not be visible, but you can still use it as the dimension in the Language filter pane. I needed to see the field temporarily so I commented out the HidePrefix line in the script and reloaded so I could change a setting on the field. I only want the user to be able to select one Language at a time, so I needed to check the “Always one selected value” checkbox in the Field settings of the #LANGUAGE field. (Right click on the #LANGUAGE field and select Field settings to see the window below).

Field settings dialog window

Once my settings are saved, I uncommented the HidePrefix line and reloaded the app to hide the #LANGUAGE field again. The filter pane will look like this (image below) and only one language can be selected at any given time. When a language is selected, the vLanguage variable (that was created in the script) will store the language. This variable is used later when updating the text in the UI.

Language filter pane

Update Front-End

Now the last step is to update everything in the app that should be translated. In this scenario, I updated sheet names, chart titles and subtitles, chart labels, KPI text and text on the sheets. Here is an example of how I updated the title of the Language filter pane. In the title field, I entered:

In the snippet below from the Excel translation sheet, the Index is 64 for the text “Language” which is why I used it in the expression above for the title of the Language filter pane. This expression will return either the English or Japanese translation for Language depending on the value of the variable vLanguage.

Snippet from Excel translation sheet

Another piece of information I would like to share is how I handled Text & image objects that needed to be translated. In the screenshot below, there is heading text and body text that have 2 different formats (font size and font color).

To handle this, I created two variables, one for the heading and one for the body and in the variables, I stored the translation expression.

edit intro.png

This way, I was able to not only translate the text but format the text in a single Text & image chart two different ways.

As you can see, it is easy to make a Qlik Sense app multilingual and it is easy to update the app with additional languages as needed. Sales, Customer Experience & Churn and Supply Chain – Inventory & Product Availability are the two demos that were made multilingual. Check them out and switch between the languages to see the final results. If you are interested in doing this in QlikView, check out Chuck Bannon’s blog on this topic as well as making the data multilingual in a QlikView app.

Thanks,

Jennell

anderseriksson · ‎2023-12-14

@Igor_Amorim Qlik does not actually handle multilingual applications.
It is a workaround with the handling of the labels but all fields in the data model is monolingual.
You would have to maintain different language versions of the applications to be multilingual as the fields are used in all dimensions and measures.

dariopin72 · ‎2024-03-08

Hi,

I've found another method. Instead of using numbered row indexes to find out the correct string and different columns, one for each language, I use a row-oriented approach, and a non-numeric StringID, that is easier and more readable. My multilanguage strings data source looks like this:

To change labels, I use the following formula:

only({<StringID={'DIM_COMPANY'},LANGUAGEID={'$(=vLanguage)'}>}String)

Each user is profiled via Section Access, and has a default language, so that the variable vLanguage has the value 'IT' or 'EN'.

You can make the formula even easier to write, if you use a variable with a parameter instead of 'DIM_COMPANY'.

Oleg_Troyansky · ‎2024-03-08

@dariopin72 - great improvement!

To simplify things even more, you can use the text in the language of your choice (for example, English", and translate the text to all languages, including English again, and then your expression could look like this:

only({<Text={'Company Name'},LANGUAGEID={'$(=vLanguage)'}>}String)

Cheers,

edwin · ‎2024-03-08

you can go one step further to have cleaner expressions. you can create a variable that serves as a function:

vTranslateWord:
'$(=only({<[$translation_id]={$1}>}$(vLanguage)))'

to use this:

$(vTranslateWord('Company name'))

dependency:

you have a table with the language as fields:

$translation_id	$English	$French
Compay name	Compay name	Raison sociale

and a table of languages

$Language

English

French

and a valriable that stores the language - this can be achieved by

vLanguage
='$'&only($Language)

you can set the language in your URL:
<your URL here>/select/$Language/English

and you can extend this to fields:
vTranslateField:
[$(=only({<[$translation_id]={$1}>}$(vLanguage)))]

assuming of course you have two fields called

[Company name] and [Raison sociale]

then in your expressions:

=only(
    $(vTranslateField('Company name'))
)

=sum({<
    $(vTranslateField('Company name'))=$(vSelectedCompanies)
    }>}$order_amount
)