Simon Marlow wrote:
Simon, is there any change to accept XML instead of
SGML for the official GHC documentation?
Sven Panne was working on this recently. Sven - any news?
Not really, but there are no deep technical reasons for this, just a lack of
time. First of all we should agree on the required target formats, which should
be dvi, ps, pdf, and html IMHO. The next thing are the supported DocBook XML
toolchains, there are quite a few of them:
1) (open)jade-based ones:
a) Eric Bischoff's docbook2{dvi,ps,pdf,html} tools
b) The DocBook toys db2{dvi,ps,pdf,html}
2) XSLT-based ones:
a) xmlto, a wrapper around xsltproc
b) pure xsltproc / saxon / xalan
3) XSLT/FO-based ones (needs some support from 2), too):
a) PassiveTeX
There are of course a lot more tools out there, but not all can generate all needed
formats or are heavily specialized (like meinproc). Option 2b) is too fragile IMHO,
because one would have to specify a lot of paths, options etc., which will be too
tricky to get working reliably. Option 3a) doesn't really offer an improvement over
the rest, only an additional tool is required for building, so it's not really the
way to go currently.
So I propose the following: Let autoconf find out which toolchain is supported
(docbook2foo, db2foo, or xmlto) and make our conversion scripts a simple wrapper
around it, no need for the current CATALOG fiddling at all. The SGML docs are
almost XML already, so let's change this, too, and nuke all SGML support from
fptools.
If nobody yells, I'll make the necessary changes for the HEAD. But first I'll have
to finish Doom 3, of course... >:-)
Cheers,
S.
_______________________________________________
Cvs-fptools mailing list
[EMAIL PROTECTED]
http://www.haskell.org/mailman/listinfo/cvs-fptools
