Hi Angel,
Building works fine on my computer.
The problems seems to come from the encoding used by Java when you compile
(I had to change GT.java encoding to UTF8).
I've just committed a modification to force using UTF8 when building. Tell
me if it works better.
Nico
2010/12/17 Angel Herráez
Works great, Nico!
No complains building now.
All languages display well in the menu (I see blocks for those whose fonts I
don't have, but I
guess that's fine)
The addition of language per demand is wonderful addition
I have commited a small fix - English was being displayed only in Spanish.
Angel,
The menu is broken on my computer with the last fix.
It only shows 4 lines : null - Català, ..., null - Deutsch.
Nico
2010/12/17 Angel Herráez angel.herr...@uah.es
Works great, Nico!
No complains building now.
All languages display well in the menu (I see blocks for those whose
Nico, those need to be entered in Unicode format, not like that, I think.
Bob
2010/12/17 Angel Herráez angel.herr...@uah.es
Hi Nico
I have got your changes but now I cannot build Jmol locally; I get these
messages:
Do you have any tips? My local building using Eclipse is not something
I see -- Angel, update the full Jmol, not just the src. You need a new
project settings file.
On Fri, Dec 17, 2010 at 4:36 PM, Robert Hanson hans...@stolaf.edu wrote:
Nico, those need to be entered in Unicode format, not like that, I think.
Bob
2010/12/17 Angel Herráez angel.herr...@uah.es
Bob,
It's fixed, the problem was only that there was no encoding specified for
the build, so the encoding used was depending on the computer used to build.
I changed the build to force UTF8 encoding.
Nico
On Fri, Dec 17, 2010 at 11:44 PM, Robert Hanson hans...@stolaf.edu wrote:
I see --
Bob, the month is wrong (zero-based)
__Jmol-12_11181000533D 1 1.0 0.0 0
should be
__Jmol-12_12181000533D 1 1.0 0.0 0
That's why I added one
1+ c.get(Calendar.MONTH)
--
Lotusphere
Hi,
It's available under SVN.
Nico
On Wed, Dec 15, 2010 at 1:16 PM, Nicolas Vervelle nverve...@gmail.comwrote:
2010/12/14 Angel Herráez angel.herr...@uah.es
I would rather see 3 things in the menu : the language code, the
language name in English, the language name in its own
2010/12/14 Angel Herráez angel.herr...@uah.es
I would rather see 3 things in the menu : the language code, the
language name in English, the language name in its own language.
That sounds great.
After thinking again about it, I changed my mind. We should display 3 things
in the menu :
El 13 Dec 2010 a las 11:03, Robert Hanson escribió:
Just follow the examples of the other languages.
Yes, I've found the code that does it (GT.java). It makes sense: only
languages with over 80% translated items get to the popup. The next
two candidates pt and pl are just above 50%. I doubt
Hi Angel,
There may be an easy way to add a language in the popup menu if is choosen
by the used.
When switching language, I think GT.getTranslation() is called, which may
result in a call to addBundle().
In addBundle(), we could parse the language list array, and if needed change
the false to a
Thanks , Nico
I'm not sure if it's worth the effort.
Recreation of the interface when switching language has improved in
latest versions.
There may be an easy way to add a language in the popup menu if is
choosen by the used.
More than chosen by the user, it's if chosen by script or if
I would rather see 3 things in the menu : the language code, the
language name in English, the language name in its own language.
That sounds great.
--
Lotusphere 2011
Register now for Lotusphere 2011 and learn how
I realize that certain localizations are still in an immature state,
but if the JmolApplet0_i18n_pl.jar file is included in the
distribution and the 'language =pl ' command is available and
accepted, shouldn't that language be available from the popup menu?
I have verified this situation with
Yes,
It would be better to add the language in the popup menu if it's used.
I don't know if it's complex to implement.
Nico
2010/12/13 Angel Herráez angel.herr...@uah.es
I realize that certain localizations are still in an immature state,
but if the JmolApplet0_i18n_pl.jar file is included
go ahead and do that, Angel.
2010/12/13 Angel Herráez angel.herr...@uah.es
I realize that certain localizations are still in an immature state,
but if the JmolApplet0_i18n_pl.jar file is included in the
distribution and the 'language =pl ' command is available and
accepted, shouldn't that
El 13 Dec 2010 a las 10:56, Robert Hanson escribió:
go ahead and do that, Angel.
Now that's a challenge!
I will see if I know how to ;-) Can't promise
--
Lotusphere 2011
Register now for Lotusphere 2011 and learn
17 matches
Mail list logo
