Re: XT outputs unusual HTML4 escape chars

Subject: Re: XT outputs unusual HTML4 escape chars
From: James Clark <jjc@xxxxxxxxxx>
Date: Sat, 31 Jul 1999 01:41:25 +0700
If you put in the result-ns attribute correctly, you will get &iacute;.
For example,

<xsl:stylesheet xmlns:xsl="http://www.w3.org/XSL/Transform/1.0";
result-ns=""
xmlns="http://www.w3.org/TR/REC-html40";>

<xsl:template match="/">
<html>&#x0ED;</html>
</xsl:template>

</xsl:stylesheet>

outputs:

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<html>&iacute;</html>

bbrosenstock@xxxxxxxxxxx wrote:
> 
> As per recommendation, I placed a result-ns attribute in my
> xml:stylesheet element, specificying the URI for REC-html40, and ran
> the xml plus stylesheet through XT rather than SAXON (which continued
> to output the unicode escape characters in the xml doc instance
> (&#x0ED; for a with an i acute, e.g.). Something did indeed happen,
> but the output was unexpected. In place of the hoped-for &iacute; in
> the source, I get two characters, namely, xc3 (hex) followed by xad
> (hex) (on the Mac this source looks like a square-root symbol and a
> not-equal symbol), which outputs HTML as capital-A with tilde and
> capital I with acute.
> 
> One further XT/SAXON difference I noticed: when I wanted <TD></TD> in my
> output (no content), it gives me <TD/> (SAXON outputs <TD></TD>),
> which the browser (IE4 on the Mac) does not read, thus messing up
> the table. If I were to rely on XT I know that I could put in a
> non-breaking space to overcome this, but I just wanted to mention
> it.
> 
> So, my question is: how do I get XT to output the correct character,
> and, is there a way to get SAXON to output normalized HTML for such
> characters?



 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list


Current Thread