• From: Bjoern Hoehrmann <derhoermi@g...>
• To: Julian Reschke <julian.reschke@g...>
• Date: Tue, 09 Jun 2009 19:07:48 +0200

* Julian Reschke wrote:
>And sure enough, when I change the XSLT's output element to use utf-8, 
>the problem goes away. The problem also occurs with us-ascii.
>
>Now, this really doesn't make sense. If the output encoding can not 
>directly encode the character, it should just be encoded using a 
>character reference.

That is not possible in comments, element names, etc. In your example
the transformation attempts to generate a warning message containing
some character outside the set of ISO-8859-1.
-- 
Björn Höhrmann · mailto:bjoern@h... · http://bjoern.hoehrmann.de
Am Badedeich 7 · Telefon: +49(0)160/4415681 · http://www.bjoernsworld.de
25899 Dagebüll · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/ 

• Follow-Ups:
  • Re: an actual MS IE XSLT issue
    • From: Julian Reschke <julian.reschke@g...>

• References:
  • an actual MS IE XSLT issue
    • From: Julian Reschke <julian.reschke@g...>