Miguel wrote:
...
Maybe the best solution for the dealing with the size would be to put
each language in a separate JmolApplet_xx.jar.
This way, only one language will need to be downloaded (except for
English where the translation is inside the code)
If that would work then it would be good.
But if they are in individual .jar files then it might be the case that
all of the translation .jar files would have to appear in the 'archive'
parameter to the applet/object tag. That would have a negative impact on
Jmol.js and .html pages.
I think, most page authors don't want a translated applet in an
untranslated page, or they want an applet with a defined language,
this could be achieved by e.g. in RasMol the script command
English
resets the GUI of the application to the defined language (or Spanish,
French, Italian) or for the Jmol applet by forcing a specific language
in the archive parameter.
I think, it would be a feature if the page author has to add the
translation .jar files to the object tag willingly.
Jmol.js could evaluate the xml:lang of the html document to determine
which translation .jar should be loaded.
Regards, Jan
-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. Download
it for free - -and be entered to win a 42" plasma tv or your very own
Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
Jmol-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jmol-developers
