Qlik Community

QlikView App Development

Discussion Board for collaboration related to QlikView App Development.

Announcements
Make your voice heard! Participate in the 2020 Wisdom of Crowds® Survey. BEGIN SURVEY
Not applicable

Localization

I know there are some older posts on this but the links are broken. I also know the Finance Controlling app has localization however the module comments are all in Germen so I can't understand exactly what's happening. Does anyone have a simple application that has multiple languages? I'm trying to do English and Mandarin and I understand there also may be some issues interpreting the character set; any tips on that would be much appreciated.

1 Solution

Accepted Solutions
Highlighted
Partner
Partner

Localization

Here is a simple version of how-to from QlikTech experts.

No experience on Mandarin so can't say much about it, but the document has an email address to contact at QlikTech if you need further help in this matter. You may try that.

View solution in original post

5 Replies
Highlighted
Not applicable

Localization

We recently had a thread on the subject: http://community.qlik.com/forums/t/16001.aspx

This is from the new forum, so everything should still be accessible.

I think the main requirement for localization was to put your field names into a table with a field for each language. A Lookup was then used to pull the field name for the chosen language (which was stored in a variable).

Highlighted
Partner
Partner

Localization

Here is a simple version of how-to from QlikTech experts.

No experience on Mandarin so can't say much about it, but the document has an email address to contact at QlikTech if you need further help in this matter. You may try that.

View solution in original post

Highlighted
Not applicable

Localization

Thank you both. Helpful attachment!

Highlighted
Not applicable

Localization

I saw the answer to this post and thought that finally someone has solved the Localization issues for QlikVeiw. But then again no. The proposed solution, as others I have seen, is depending on one prerequisite; all labels for each language are unique. If not: the FieldIndex and FieldValue functions will return wrong labels. The labels are set within the charts, so the lookup function will not help... (unless I explicitly set all labels in the loading script).

Example:

Label English Norwegian

lblOnly Only Bare

lblSbdy Somebody Noen

lblFew A few Noen

lblOthrs Others Andre

In this example two English words are translated to two Norwegian words with the same syntax, but different semantics. If this happens, the lookup for Norwegian, normally using FieldValues and FieldIndex, will return the wrong value when finding the translation of "A few", as the second value of "Noen" will be seen as redundant by QlikView... the error will affect all the succeeding values.

For small applications this might not seem like a problem, but wait until you start to play with an application with tens of tabs and hundreds of graphs and list boxes... and you then try to outsource the job to someone not understanding all the languages in your application... 😉

Any others with the same experience? Any other solutions to this than the dirtiest of dirty tricks - the pipe separated string - creating the following interesting, but unique values (I used the § character as the | is so tiny...);

Label English Norwegian

lblOnly Only§lblOnly Bare§lblOnly

lblSbdy Somebody§lblSbdy Noen§lblSbdy

lblFew A few§lblFew Noen§lblFew

lblOthrs Others§lblOthrs Andre§lblOthrs

Then of course you need to add a left() and an index() function as well to dissect out the label you want to show...

Highlighted
Not applicable

Re: Localization

hey , i am working on a similar application but on a personal edition . Cant open the attachment. Can you please help?