On Thursday 26 May 2005 00:34, Daniel Leidert wrote:
> Am Mittwoch, den 25.05.2005, 23:41 +0200 schrieb Nicolas Vervelle:
> > How can we be sure that we don't (won't) have other similar problems
> > with strings that should not be translated ?
Good catch. I'll review the code...
> I don't underst
Am Mittwoch, den 25.05.2005, 23:41 +0200 schrieb Nicolas Vervelle:
> Daniel Leidert wrote:
>
> >Don't care about .pot and .po files. They are updated after running
> >update-po target in build-i18n.xml. xgettext searches all given .java
> >files for translatable strings (which are marked as
> >'GT
Daniel Leidert wrote:
Don't care about .pot and .po files. They are updated after running
update-po target in build-i18n.xml. xgettext searches all given .java
files for translatable strings (which are marked as
'GT._("string_to_translate")'). So you don't need to edit .pot or .po
files manual
Am Mittwoch, den 25.05.2005, 23:11 +0200 schrieb Nicolas Vervelle:
> I don't know if you find the translatable Strings in the source code
> manually or automatically.
> In org/openscience/jmol/app/Jmol.java, the ..._WINDOW_NAME constants
> should not be translated: they are internal constants us
I forgot to say that I only found this by accident because Eclipse gave
a warning in this code.
I hope no other problems exist or can occur.
Nicolas
Nicolas Vervelle wrote:
Hi Egon,
I don't know if you find the translatable Strings in the source code
manually or automatically.
In org/opensc
Hi Egon,
I don't know if you find the translatable Strings in the source code
manually or automatically.
In org/openscience/jmol/app/Jmol.java, the ..._WINDOW_NAME constants
should not be translated: they are internal constants used in the
history file.
I could modify Jmol.java but I don't k
