Rod Taylor writes:
> Recently, I've been using Openoffice for a first cut and Conglomerate to
> clean the document up. Of course, that uses a strict XML version and I
> normally prefer xincludes to entity based includes.
If you can find/propose/develop an XML-based setup that has the same
functionality as our current setup, I wouldn't mind switching. Some
things that I see as requirements are:
1. Does the HTML output look at least as good as the current output? (The
default DocBook XSLT stylesheets do not, AFAIR.)
2. Is there a toolchain that can create PDFs, that actually work on our
input files? (FOP does not, AFAIR; PassiveTeX is a pain to set up.)
3. Is there a (mature) toolchain to create man pages?
4. Is there a quick way to verify the validity of the entire document?
5. How does the speed of the new toolchain compare to the current one?
6. What to do about the parameter entities?
7. How hard is it to set up the toolchain? (xsltproc is pretty wide
spread and would be acceptable. Java-based tools such as saxon seem like
trouble.)
--
Peter Eisentraut peter_e(at)gmx(dot)net