From: Daniel L. <dan...@gm...> - 2005-05-28 10:20:38
|
Am Samstag, den 28.05.2005, 11:12 +0200 schrieb Nicolas Vervelle: > Daniel Leidert wrote: > > >Better copy Jmol.pot to your_language_code.po (e.g. fr.po, pl.po or to > >whatever language you want to translate). Then begin with the headers: > >Replace 'PACKAGE VERSION', 'FULL NAME <EMAIL@ADDRESS>', ... and > >especially 'CHARSET' with the appropriate values. Then begin to > >translate. 'msgid "..."' contains the untranslated string. 'msgstr ""' > >is the place for the translated string. > > > I am really a beginner with po files, so forgive if the questions are > dumb ;) > > I have downloaded poEdit for Windows to make the translation and I am > starting to use it. > > One interesting feature seems to be that you can view quickly the Java > file where the translation will be used (menu Edit / see references or > right click on the translation) but it doesn't work. I have never used such a feature :) > I guess it's because the base directory is not defined. When I try on > the first translatable string, I get the following error message: > "Error opening file > E:\Java\Jmol-HEAD\src\org\jmol\translation\Jmol\org\jmol\applet\Jmol.java" > Is it possible to define something in the .pot file so that each > translator could automatically use this feature ? I am sorry, but I don't know, how to realize that. The problem is: the location part is currently written relative to src/ to avoid an every-time-update of the location-string (e.g. I have Jmol in /home/..., Egon has it in /mnt/... etc.pp). I did not find a way to write it relative to ${Jmol.po.dir}, which would be necessary to allow the feature you are talking about. Maybe you have an idea? I will ask several Java-newsgroups. > The same text is used in several places because it's the same word in > English for several situations. > But the translation in French is different depending on the situation. > How can I do this ? I am not completely sure. > For example : "None" are used in the menu in several places but it can > be translated to "Aucun" or "Aucune" depending on the gender: There are IMO several possibilities: E.g. one common is to translate it as msgid "None" msgstr "Aucun(e)" or msgstr "Aucun/Aucune" Is there any argument against this practice (it's IMO only a minor issue)? Or maybe you find a better English string to workaround this problem. Regards, Daniel |