Re: [docbook-apps] Re: client side transformation using docbook-xsl

[Richard Rosenberg <richrosenberg@earthlink.net>]

Thanks for the excellent idea, an identity transform using the provided 
customization facility is a much better way to go. I guess at this point I 
can no longer see the forest for the trees. . .

I filed a bug for #1, requesting a fix to deal with the Firefox mime-type 
security error:

http://sourceforge.net/tracker/index.php?func=detail&aid=2039122&group_id=21935&atid=373747

Thanks to this list the learning curve is starting to flatten out. 

Best regards,

Richard




On Tuesday 05 August 2008 08:00:23 you wrote:
> For #2, you could do an identity transform on l10n.xml to resolve all
> the entities in one go, then set the parameter l10n.xml to your custom,
> resolved version of the file <xsl:param name="l10n.xml"
> select="document('path/to/your/resolved/version/of/l10n.xml')"/>. That
> should keep Firefox from every looking at the l10n.xml that's in the
> distribution. Here's an xslt that does the identity transform:
>
>   <xsl:stylesheet version="1.0"
>     xmlns:xsl="http://www.w3.org/1999/XSL/Transform";>
>
> 	<xsl:output method="xml" indent="no"/>
>
>     <xsl:template match="@*|node()">
>       <xsl:copy>
>         <xsl:apply-templates select="@*|node()"/>
>       </xsl:copy>
>     </xsl:template>
>
>   </xsl:stylesheet>
>
> For #1, perhaps you could log a bug and ask that VERSION be renamed to
> VERSION.xsl in the distribution.
>
> David