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...
