Switching to Jmol-developers ....

Nico has released 11.1.33. I'd appreciate another round of testing of 
that for language in the menu and proper menu updating. I'm having a 
problem on my end setting my locale -- I set it in Windows, then 
depending upon what I open I see it automatically switching back and 
forth among different languages. So I haven't successfully tested that 
the applet loads the proper local language initially.

Egon mentioned settings in Mozilla. As far as I know, all that does is 
send the following header to a host server along with the page request:

Accept-Language: es-mx,en-us;q=0.7,en;q=0.3

or something like that. So that should have no effect on the applet itself.

Right now the way the menuing system works is not sufficient -- I have a 
hardcoded set of languages, and we are simply going down the line adding 
them to the menu:

    addCheckboxMenuItem(menu, GT._("Catalan", true), "language = \"ca\" 
#Catalan",
        id + ".ca", language.equals("ca"));
    addCheckboxMenuItem(menu, GT._("Czech", true), "language = \"cs\" 
#Czech",
        id + ".cs", language.equals("cs"));
    addCheckboxMenuItem(menu, GT._("Dutch", true), "language = \"nl\" 
#Dutch",
        id + ".nl", language.equals("nl"));

etc.

Clearly this is not sufficient. It was just a quick hack to see if any 
of this would work at all. JmolPopup should just be getting a list of 
supported languages from GT and then iterate through them to produce the 
menu. There shouldn't be anything in JmolPopup that assumes any 
knowledge of available languages. I'm going to see right now if I can 
fix that, but what I'll do is probably still not quite right. I suspect 
that what we really need is a set of properties in a property file that 
takes care of this.

One problem I foresee is that we might end up with "desired language" 
and "actual language" -- We have fr, but the user's system identifies it 
as fr-ca, and we only deliver fr. Something like that.

Bob





Nicolas Vervelle wrote:

>Angel Herraez wrote:
>  
>
>>If creating a separate new pt-BR is troublesome, I would suggest that 
>>1) the former translator is contacted, to see it (s)he is willing to maintain 
>>the pt-PT translation 
>>up-to-date
>>2) if not, Sérgio updates the existing pt localization file as he pleases (I 
>>guess that for 
>>Portuguese-speaking users, a Brazilian menu will be better than a 
>>half-English menu)
>>3) find out how many Portuguese users around, their viewpoints to this 
>>respect or their 
>>willingness to contribute translations
>>  
>>    
>>
>Currently, the "country" element is not supported by Jmol but it's 
>because we simply disabled it.
>A few modifications of the code will be needed, but not that much, so 
>adding pt_BR shouldn't be a problem.
>
>Nico
>
>PS: Angel, if you get this mail only once, can you forward it to the 
>mailing list, since it will mean it has been rejected again :(
>
>
>-------------------------------------------------------------------------
>This SF.net email is sponsored by DB2 Express
>Download DB2 Express C - the FREE version of DB2 express and take
>control of your XML. No limits. Just data. Click to get it now.
>http://sourceforge.net/powerbar/db2/
>_______________________________________________
>Jmol-users mailing list
>[EMAIL PROTECTED]
>https://lists.sourceforge.net/lists/listinfo/jmol-users
>  
>


-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Jmol-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jmol-developers

Reply via email to