i used to give the user a language choice. set(_lang, english); for example.
Then i do if(_lang == english, set(layer[x].html, data:html_info_english)); etc etc..
now you need just to make a <data> thing for every language..

The rest of the interface like showtext etc you could do the same way or like if but then ...layer[x].html, get(blabla));

works for me.

Tuur

I would propose no IF solution where you have e.g. separate xml for all languages and just using one lang_var read data depending on what value is set.



somewhere you have to set what is active language: set(lang_var,en);

Accesing data with: get(group[get(lang_var)].group[object_2].value);

You can see code example in multilang side menu plugin: here you can donwload and explore

Yes that is also possible. I use that as well sometimes.. But at the end it is the same, and sort of the same amount of code, i suppose.

Tuur

In both cases we need to have texts defined and will occupy certain amount of memory for it but when it comes to question should we use 10 IF in case we have 10 languages than proposal should be obvious.
Not to have:
if(_lang == english, set(layer[x].html, data:html_info_english));
if(_lang == deutch, set(layer[x].html, data:html_info_deutch));
.
.
.
if(_lang == italian, set(layer[x].html, data:html_info_italian));

for each attribute you have multilingual dependent can be only one:
e.g. set(layer[x].html,get(data[get(lang_var)].html.value);

I think this is also easier for Krpano engine when IF statements are optimized as much as possible. At least I try to avoid /reduce them if possible.

mmm i suppose you are right..
i call actually the action 'english' where things are set..
Tuur