The processor is always at liberty to ignore disable-output-escaping. Saxon
uses a very simple serializer configuration for xsl:message. I wasn't
actually aware this would take no account of d-o-e, but it doesn't greatly
surprise me.

If you care about these things you can plug in your own MessageEmitter to
handle all aspects of xsl:message formatting and routing.

Michael Kay
http://www.saxonica.com.

> -----Original Message-----
> From: Florent Georges [mailto:darkman_spam@xxxxxxxx]
> Sent: 21 May 2006 00:48
> To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
> Subject: RE:  Escaping of xsl:text in xsl:message
>
> Michael Kay wrote:
>
> > If in doubt, read the spec:
>
>   Yes, I don't know why I didn't think that myself.  Thanks
> for the exerpt.  But with the following script:
>
>     <xsl:transform xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
>                    version="2.0">
>
>       <xsl:template match="/">
>         <xsl:message>
>           <xsl:text disable-output-escaping="yes"> -> </xsl:text>
>         </xsl:message>
>       </xsl:template>
>
>     </xsl:transform>
>
> the '>' must not be escaped, right?  I wonder if it is the
> case, 'cause Saxon 8.7.1j escapes it.
>
>   Regards,
>
> --drkm
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> ______________________________________________________________
> _____________
> Faites de Yahoo! votre page d'accueil sur le web pour
> retrouver directement vos services prifiris : virifiez vos
> nouveaux mails, lancez vos recherches et suivez l'actualiti
> en temps riel.
> Rendez-vous sur http://fr.yahoo.com/set