> Hi, > > I think we should use the gettext tools also for the contextual menu > (application + applet). > It would make the translators work easier, and in the same process will > remove the need for the applet to look on the web server for > JmolPopupStructure.java.
Yes, that would be fine. My plan (a few years ago) was to have the popup menu file and translations on the web server. That would allow people to create their own popup menus. In practice, no one has used that mechanism. At this point I think that incorporating the menus/translations into the .jar files would be fine. > I am willing to work on it, but I want to be sure the way I was planning > to do it is ok. > > What I thought : > - modify org/openscience/jmol/ui/PopupResourceBundle to use 2 internal > ListResourceBundle (instead of ResourceBundle), see below OK > - create one derived class of ListResourceBundle for the structure > (copying JmolPopupStructure.properties into it) > - create one derived class of ListResourceBundle for the labels (copying > JmolPopupWords.properties into it) OK > - modifiy build-i18n.xml to add strings to translate into JmolApplet.pot > - includes org/jmol/translation/JmolApplet/Messages*.class into the > applet jars. > > Any comment ? I think that will be fine. Depending upon the size of the translations, it may be better for us to put them in their own JmolApplet7.jar file. At first you should do whatever is easiest for you. Miguel ------------------------------------------------------- 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
