>> Oh dear God...
>>
>> https://bugzilla.mozilla.org/show_bug.cgi?id=98168
>>
>> Short story: Using the xsl:text disable-output-escaping='yes' setting
>> doesn't work. It's supposed to allow you to output arbitrary text, and
>> it works with IE, but not with Firefox. And it appears they're trying to
>> claim it's IE that's broken, not Firefox. >_<
>
> Actually both are standards compliant:

> The spec concludes that "Since disabling output escaping may not work
> with all XSLT processors and can result in XML that is not well-formed,
> it should be used only when there is no alternative."

Ah. So in fact, the W3C specification is broken, since /clearly/ a 
system should not be specified to suddenly produce completely incorrect 
output if an optional feature is not implemented.

*sigh*

Meanwhile, it looks like my only options are either to start memorising 
Unicode code points by ID, or to save my XSL file as UTF-8 and watch the 
encoding get screwed up every time I touch the file...

(Let's not even get into the question of why the standard character 
names /only/ work in HTML, and not all SGML file types...)

Post a reply to this message