Am Dienstag, den 27.09.2005, 18:52 +0200 schrieb Nicolas Vervelle: > Miguel wrote:
[..] > >Q: Are the gettext tools written in Java? > > Unfortunately, no, probably C. C. But they are developed to provide a translation system for a bunch of programming languages - including Java. > >Q: Are they licensed under an open-source license? > > > > > Yes, they are Gnu tools, under GPL / LPGL license. The tools itself are written under GPL license. libintl(.jar|.so) is licensed under LGPL. > >If so, then we should see if we can check things into the Jmol CVS so that > >they are automatically downloaded as part of the CVS checkout process. > > > >A few years ago I did a lot of work so that the xml/xsl documentation > >stuff was checked into CVS so that there was not a lot of 'external' setup > >required in order to run. > > > >If possible, I would like for it to continue to be the case that I can > >walk up to a fresh machine, install Java, check out Jmol, and build it. > > > > > I understand that concern, and I share it. I don't share it. Distribution packages should always be preferred, because they contain fixes and are especially build for the machine/architecture running on. > That would be nice to keep it > this way. > At the moment, I don't see how if we keep gettext tools. > But I am not really ready to give on gettext, it's *very* helpful to > keep the translations uptodate > (at least for Jmol itself, I am not sure about the documentation part) > Maybe other people working with the translations can give their feeling > about it. Please note, that the usage of xml2po/gettext for the documentation is optional and not a "must". build-i18n-doc.xml is not part of build.xml. And for all those who do not have the gettext tools or xml2po installed: You only need to copy the .pot file to Jmol*Guide_LANG.po and translate it to take part in the documentation translation. xml2po/gettext only make it easier to keep track of changes in the original documents and so make translators work easier. > Concerning Jmol application and applet, the current situation is that > gettext tools are only needed when : > 1) creating a new version of Jmol (otherwise the distribution doesn't > contain translations) > 2) keeping the translation files uptodate with the Java code > So, for most people, gettext tools are *not required*. > If need be, we could get rid of case 1) by adding generated messages > classes under CVS (not pretty). Possible, but then please do NOT provide them with the source distribution. Pre-compiled files should not be distributed - in every case. > Case 2) needs only to be done from time to time on 1 computer (since the > result is committed under CVS) > > If someone has an idea on how to manage to keep easy translation and > easy build together, I am really interested. Well, let us fix bugs. The new translation system is quite easier than the old one. I know, that Mac is currently not supported, but that is because I don't have a Mac system. I can only test on Windows and (Debian) Linux systems. So please Mac users: Help us fixing build-i18n.xml to work on Mac. Regards, Daniel ------------------------------------------------------- This SF.Net email is sponsored by: Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl _______________________________________________ Jmol-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jmol-developers
