Re: [Jmol-developers] Issues in Jmol documentation and some questions

[Nicolas V. <nve...@cl...>]

Hi,

it's nice to see that an other translation of the documentation is being
done :)

From: "Daniel Leidert" <dan...@gm...>
> Hello,
>
> 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)

I prefer spacings (my editor is configured for tab = 2 space chars) and
lines not too long but I can live with it.

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

Well, no problem for me, but if there is both the .xml and the .pot file for
en or de, it should clearly be stated somewhere which one should be modified
manually and which is generated.

Q for personal interest :
1. What happens to sentences with formatting inside of them ?
Are they cut into several parts (I hope not) ?
For example: "The <emphasis>only</emphasis> valid
comparison operators for loop termination are
<command>&lt;</command> and <command>&gt;=</command>
... anything else is probably a bug."

2. Does xml2po works with SGML files ?


Nicolas