Egon Willighagen wrote:
> 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).
> 
> Daniel, 
> 
> UTF-8 files, or UNICODE in general, should be added as binary files to CVS 
> [1]. Please readd them as binary.

Ok. I added the po(t) and the German translation as binary (cvs add
-kb). I hope, that was right. I've never had problems with UTF-8 encoded
xml files at my own CVS server. Good to know.

Regards, Daniel





-------------------------------------------------------
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

Reply via email to