On 2006-05-04 07:48:34 +0000, Rocco Rutte wrote:
> The errors remain. I have everything installed which should matter to
> the build process (i.e. DocBook DTDs). For me, the attached patch solves
> the problem. I'm not that much of an XML expert, but it looks like mutt
> used the wrong doctype for the DTD it requests so I ask for applying it.
The DOCTYPE is incorrect:
<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.1.2//EN"
The version doesn't match. However, I don't think this could lead
to errors. Are you sure you don't have incorrect catalog files?
You can try with --load-trace to see which documents (including
those defining the entities) are loaded.
> which is ugly. Also, personally I don't like being limited to DocBook
> only. In my opinion, DocBook is an intermediate format people convert to
> to get fancy HTML output, but it's not really suitable for humans to
> write docs in.
Well, DocBook + PIs may be sufficient.
> In the very end, I think a custom mutt XML dialect is much better as
> it allows us to have the documentation much more consistent. That
> means we could have tags to reference functions and variables and
> let XSL add a '$' (plus the link) for variables and '<>' for
> functions (plus the link) automatically. The XSL processing from it
> to DocBook will take around a second since now it's only the DocBook
> XSL stylesheets taking that long.
> IMHO it would be cool to have just:
I think this should be <varname>header_cache_verify</varname>.
> and let XSL expand it to:
> because that's what it's for.
But the source would still be DocBook. One could also write:
and process the makelink PI to generate the link.
Vincent Lefèvre <vincent@xxxxxxxxxx> - Web: <http://www.vinc17.org/>
100% accessible validated (X)HTML - Blog: <http://www.vinc17.org/blog/>
Work: CR INRIA - computer arithmetic / SPACES project at LORIA