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) 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. Next: I found the next cyclic dependency during my work to provide common Debian packages. The point is, that I need jmolApis.jar and jmolIO.jar for compiling the CDK-classes, and then I need the CDK-classes for compiling Jmol(Applet). So I patched build.xml, that I can compile the jmolApis.jar and jmolIO.jar only (without compiling the whole source). Means: I made a apisio.classes files and the targets apis-jar/io-jar depend on their own project-path and classes-directory. Q: Can I add this to the upstream build.xml? It will not affect the upstream. It is only for compile _only_ jmolApis.jar and jmolIO.jar, without compiling the whole Jmol source. Next: The source contains the whole sample directory. The point is, the unpacked source is about 50MB and the sample directory > 40MB large. Excluding the samples-directory from the source-tarball would result in a extremely decreased the size of the source-tarball and the source directory. The Developers Guide says, that the samples should be tested before distributing a package. But IMHO, the samples can also be downloaded via cvs or distributed _besides_ the source archive as an own archive. Not all people, which will download and compile Jmol are package maintainers. So they don't need the sample directory (IMHO) Q: Can we agree to exclude the sample directory from the source tarball and better distribute the samples in their own tarball? 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
