Miguel wrote:
The third solution would require to modify Jmol.js to add the correct
JmolApplet_<lang>.jar to the archive.
Q: How does one detect language within the browser?
Q: Would people want to choose a localization other than the one that is
set as their browser default?
I think we can see the language selection of the Applet in two
completely different ways :
1) the applet uses the language configured by the user in the browser.
That's the current behaviour
In this situation, I don't know how to detect the language in JavaScript.
Maybe someone else can answer this question.
But, I am not sure this behaviour is the best one.
2) the applet uses the language chosen by the designer of the webpage
(either the language of the html page itself, or a tag in the applet ?)
This would be an entirely new behaviour, but it could be a better behaviour.
For example, in the Jmol website, currently you get :
- a page in the language that is best suited for your browser
configuration (decided by Apache). You can view the page in an other
language by clicking on one of the flags.
- an applet in the language that is best suited for your browser
configuration (decided by the applet itself). You *cannot change* the
applet language by clicking on one of the flags, only by changing your
browser configuration.
With this new behaviour, the language of the applet would match the
language of the webpage, letting the user fully decide which language he
wants (if the website has translated pages).
Nicolas
-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
Jmol-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jmol-developers
