Check for a list of languages to manage on the net.
When visits have dozens of different languages, I'm curious about the html.lang.en and html.lang.de proposed...
We have around ten languages on our side, managed like this :
<layer name="layer1" html="get:language[get(lang)].layer1_html" .../>
<layer name="layer2" url="get:language[get(lang)].layer2_url" .../>
<language name="en-UK" layer1_html="english html" layer2_url="english img" .../>
<language name="en-US" layer1_html="US html" layer2_url="US img" .../>
<language name="nl-BE" ..../>
<language name="fr-FR" .../>
<language name="fr-CA" .../>
...
works kind of well with many languages.
what is still not handled on our side is in case the layer1_html attribute is not filled in for a given language, there will be some empty string displayed. we thus need to be very rigourous in filling all <languages>. Actually, it would be nicer to define the fact en-UK is default and if no attribute layer1_html is found in language[nl-BE] then krpano would read layer1_html in the language[en-UK] node .
Interested in the "attribute.variable" thing though, and better if it is not restricted to languages only (currently this attribute.variable is restricted to devices for instance), and if it is constantly assessed (should not require a reload).
Florian