On Tue, 2005-09-27 at 19:59 -0400, René Kanters wrote: > On Sep 27, 2005, at 3:05 PM, Daniel Leidert wrote: > > Am Dienstag, den 27.09.2005, 12:08 -0400 schrieb René Kanters:
[Eclipse build not using system PATH variable] > So it looks like Eclipse is the culprit. Could you take a look into Eclipse' documentation for developers? Maybe you can manipulate the behaviour somewhere. The documentation can be browsed (IIRC). [..] > >> but the import libxml2 is failing for > >> me there... So it seems that the Jmol project is starting to rely > >> more and more on external things, possibly their versions, and as a > >> result the require a more complex environment > >> > >> > > > > It only depends on gettext, not more. And gettext is a common tool. IMHO > > the advantages of the gettext translation system overbalance. > > > > It looks like the doc build also relies on python and libxml2, which > does not seem to work properly on my system. (i.e., I do have python, > but there are problems loading the libxml2). Are you sure, that Mac does not provide own packages for the libxml2-python-bindings? And BTW: xml2po is part of the gnome-doc-utils, which are essential for GNOME program documentation. Because GNOME is IIRC available for Mac, maybe gnome-doc-utils are too. > See comment below, though. > > > >> for the people that > >> (try to) contribute to maintain (can anybody say 'dependencies' :-). > >> I am not complaining, just observing here.... > >> > >> I did find some libxml2 information for Mac users (not just > >> Windows...) at http://jamesclarke.info/notes/InstallLibxml2 but do > >> not have the time right now to go through all that. > >> > >> > > > > It's only necessary, if you want to use xml2po. But to contribute in > > translation of the documentation, you don't need xml2po or libxml2, > > because you only need to copy the .pot file to .po and translate it. > > xml2po is only necessary to extract translatable strings from xml > > to po > > and merge them back to po or update po. > > > > So you basically are telling me, if I understand correctly, that I > really don't have to worry about this. Yes. I will try to explain the situation: The Guides are written in Docbook XML. To translate them, Nicolas made a copy of every XML, added a note about the original version number of the Guide in the head of every copy and then translated this copy. Using this way, it isn't easy to follow changes made to the original Guides. But there are some tools available, making it possible to also use a gettext-system (Portable Object file - .po(t)) to translate Docbook XML. One of these tools is xml2po from the gnome-doc-utils project/package. It does the following things for us: - extracts all translatable strings from a Docbook XML file and creates a .pot (portable object template) file - updates an existing .po file (containing a translation) after changes were made to guide/XML file - merges the translation from a .po file back into an XML file So if someone wants to take part in translating the documentation, he basically only needs to copy the template .pot file to a .po file and make his translations inside the .po file. The translator itself does not need xml2po nor python. > I realize that a regular build > does indeed not use these. So I am OK with that. The regular build only takes the final Guides (original + translated) and converts them to HTML. 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
