On Wed, 2003-10-15 at 12:29, Peter Eisentraut wrote:
> 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.)
You don't need to switch toolkits to use XML input files as the source.
Openjade and friends all support XML with the exception of xincludes
(frankly, they're the best part).
A single XML document can be generated out of several from xincluded
source with a xsltproc which is then fed that into openjade.
As far as the HTML goes, the Gnome & FreeBSD documentation teams have
put some work into making the HTML come out right -- some things come
out much better (media items). Print is still lacking, but stated above
we can still use the old toolchain for that.
Is this something that is worth investigating? I'm happy to do the work,
but my process in submitting documentation changes has been lacking (as
shown by non-acceptance).
What would you like as proof of concept for buy in prior to converting
the entire toolchain?