>> Q: What are you proposing/advocating? > > I only spoke about Nicolas mail and his suggestions/ideas/thoughts: > > [..] > | 1) the applet uses the language configured by the user in the browser. > | [..] > | 2) the applet uses the language chosen by the designer of the webpage > [..] > > IMHO the first should always be the default (and as far as I read, it > already is).
No, that is not the default. Localization is not supported in the current JmolApplet. So the current default in the JmolApplet is option 0 ... always English. > But there may be situations, where the second possibility > is maybe preferred/wanted. Let me give you a short example: a localized > HTML-manual for the applet containing example usages of the applet and > explanations. In this situation you maybe read (localized) "Use menu > item 'foobar' to do something ...". Then it would be useful, if the > applet is shown in the language used for the manual. IMHO for both it is > more useful, if we provide all languages at once for the highest > flexibility. I agree that option 2 seems useful ... more useful that option 1. So, I still do not understand what you are advocating. I said that it was OK to put all the localizations in one JmolApplet_i18n.jar file. I think that you said that you did not like that. Q: Were you complaining about downloading extra localizations? Q: What do you want to do? Miguel ------------------------------------------------------- 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
