From: "Daniel Leidert" <[EMAIL PROTECTED]> > > You have replaced "../../build/docbook-xml/docbookx.dtd" by > > "http://docbook.org/xml/4.3/docbookx.dtd";. > > Is it necessary ? > > I need it to validate the xml. Because, if xmllint can't find the DTD, > it cannot validate it, so I always use the dtd in the www (for all my > docbook files). I'm sorry, normally I changed it back to > "../../build/docbook-xml/docbookx.dtd". It seems I forgot it. I will fix > it soon.
The ../../build/docbook-xml/docbookx.dtd is extracted from the archive by build.xml during the build (target check.docbook-xml) so you could validate the xml once it has been extracted. > > Egon (I think) and I decided to make this change the other way a few weeks > > ago so that updating docbook-xml-x.y.zip in the doc folder won't need to > > modify each xml file. > > That's an interesting point, I wanted to ask you. Why do you need the > docbook-xml files/archive with the DTDs inside the source? What is the > advantage to having the DTDs inside the source? I don't know why the archive is here in the first place, it was here before I came to this project. But since it was here it was easier to point to the local dtd for maintenance purpose. For example, I just replaced the v4.3 of docbook-xml by v4.4 and I don't have to update the xml files. Nicolas ------------------------------------------------------- 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
