On Wednesday 09 February 2005 01:37 am, Daniel Leidert wrote: > I found some issues in the documentation. JmolDevelopersGuide.docbok.xml > does not contain valid xml[1]. I fixed this. But: I use tabs (the > current source is mix of tabs and spacings) for indent and I don't use > linewrap after 80 chars for a better look. > > Q: Does anyone run into problems with such a xml file? (maybe someone > uses console for writing the dosc) > > Next: I use xml2po for translating the documentation. This means, xml2po > extracts the translatable strings from the xml and put them into a .pot > file. The translated xy.po is than turned into the translated xml (like > gettext works). > > Q: Should I upload the .pot files for the guides? Is there an interest > for having this in the CVS? IMHO it makes translation easier. It will > not affect the work of anyone. It is only an alternative to Nicolas way.
Yes, I think it's good to have the *.pot and *.po files in CVS too. Ummm... questions, just to get things clear: how is the *.po(t) updated when the original xml is changed? Do we get those nice fuzzy qualifications in the .po stuff then? Another thing, the .po method also allows to make translation statistics. Have you explored that already? BTW, thanx for starting this. Egon ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Jmol-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jmol-developers
