Am Montag, den 16.05.2005, 21:00 +0200 schrieb Egon Willighagen: > On Monday 16 May 2005 09:27, [EMAIL PROTECTED] wrote: > > De: Egon Willighagen <[EMAIL PROTECTED]> > > >I was wondering wether using Gettext [1] for > > > internationalisation/localisation would be something to give a try. > > > Gettext is GNU's well established system for translation software; it's > > > the PO file system. Good utils are available for translating and > > > maintaining PO files, like KBabel [3]. > > > > > >I don't have practical experience with it, other than translating the > > >chemicalMIME package. I am exploring this, but it should not be that hard. > > > > It could be useful to have a common i18n/l10n mechanism for all the > > translations. IMHO, it must have the following features: > > - A good free tool for editing that works on Unix AND Windows (KBabel > > requires KDE, hence Unix), easy to setup, but that can also work if manual > > editing is done on the files. > > PO files are simple text files, and can be edited like any other text file. > *In addition* they can be edited with special PO editors like KBabel. > Another is the crossplatform (yes, including WinX) poEdit [1].
Or gtranslator for GNOME desktops. [..] > > - If an existing text is slightly modified (for example, orthograph), the > > translations are still valid. > > Yes, these are called fuzzy I think... They are marked as 'fuzzy', right. > > - Deleted texts are easy to find or are > > removed automatically from the translated parts. > > Yes, that's what gettext does I think... I don't know yet how the updating > exactly works, but I'll figure that out... There are several update mechanisms. The easiest and mostly used is: xgettext --default-domain=my_domain .... mv my_domain.po my_domain.pot msgmerge -q --output-file=tmp.po my_lang.po my_domain.pot The last step creates a file tmp.po, which is an update of my_lang.po. New text parts are added, changed text parts are marked as fuzzy and removed text parts are now at the end of the file and commented out. > > > - Works for every kind of file: Java, XML, HTML, script, ... > > gettext works for many things... Java, C, etc... > Daniel Leidert (who does > Jmol's Debian GNU/Linux package) has used it for other text files You mean intltool and/or xml2po | poxml (both use gettext as backends). intltool is used to translate special formats (special text and XML files for glade, gnome-mime-data or shared-mime-info). xml2po and poxml can be used to translate XML docbook files (but only xml2po from the gnome-doc-utils has support for chunked XML files). If you have your own DTD, then you can write your own python script to use xml2po to translate your XML documents. [..] > > Among the points above, for me the main point is that it must work both > > under Unix and Windows (and maybe OS X, I don't know if someone is using it > > for development) so that everyone can work on the translations. I don't > > have an easy access to a Linux computer, so I want to be able to continue > > working on Windows. > > I think the general procedure is that a POT files is created from the Java > source files... and people localize this POT file. I'll try to find Ant > support for it, but otherwise: would you have major problems with having this > POT file updated offline, by someone with access to a UNIX machine? IMO you need to add the gettext infrastructure (gettextize -c --force) and then you could provide a short Makefile (instead of Makefile.in.in) for this problem. > Translatable strings don't change that often... It's common to make a string freeze (e.g. before a new release), update the PO-template file and all localized PO files and then send them to the translators. It's not common to change the translation after every change in the source code Regards, Daniel ------------------------------------------------------- This SF.Net email is sponsored by Oracle Space Sweepstakes Want to be the first software developer in space? Enter now for the Oracle Space Sweepstakes! http://ads.osdn.com/?ad_id=7412&alloc_id=16344&op=click _______________________________________________ Jmol-developers mailing list Jmol-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jmol-developers
