giacomo wrote:
>
> On Sun, 16 Dec 2001, Stefano Mazzocchi wrote:
>
> I have some experience in using cocoon to generate html sites and pdf
> books with full validation turned on. So I might be of help in this
> concern (yes, cocoon is able to do that out of the box with support for
> CATALOG mappings to overcome the hassle of SystemID pointing into the
> file system instead of using http URLs).
>
> Another point is (yes, guys, it comes again) shouldn't we move to a
> more "official" DTD for our docs?
I'm going to come up with the DTD discussion RSN. Please, hold it for
now.
> The Avalon project already has parts
> of their documents written in DocBook as well as XSLT stylesheets to
>
> 1. transform DocBook to html and pdf (addmittedly only a subset
> of DocBook)
> 2. convert the cocoon DTDs you've mentioned somewhere below
> to the DocBook DTD (for legacy reasons :).
>
> In a documentation build system based on cocoon I'm using I've choosen
> an evolutionary approach to support various DocBook elements by adding a
> XSLT template like this:
>
> <xsl:template match="node()" priority=".-1">
> <xsl:message>
> THE ELEMENT <xsl:value-of select="name(.)"> ISN'T YET SUPPORTED
> </xsl:message>
> <xsl:copy>
> <xsl:apply-templates/>
> <xsl:copy>
> </xsl:template>
>
> <xsl:template match="@*" priority="-1">
> <xsl:copy>
> <xsl:apply-templates/>
> <xsl:copy>
> </xsl:template>
>
> These templates lead to show during the build process each element used
> in the xdocs without explicit support made available.
That's a good suggestion, thanks.
The DTD dicussion will be next.
--
Stefano Mazzocchi One must still have chaos in oneself to be
able to give birth to a dancing star.
<[EMAIL PROTECTED]> Friedrich Nietzsche
--------------------------------------------------------------------
---------------------------------------------------------------------
In case of troubles, e-mail: [EMAIL PROTECTED]
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
