Subject: RE: Encoding problem From: Kay Michael <Michael.Kay@xxxxxxx> Date: Mon, 31 Jan 2000 10:41:02 -0000 |
You might be content but I'm not! It's a new bug, 5.1/018 for future reference. Fixed in next version. The failure actually occurs if the attribute value contains any non-ASCII character, however expressed, and it also applies to other instructions whose content generates text, e.g. xsl:message, xsl:comment, and xsl:processing-instruction. It's all due to the confusion between "utf-8" and "UTF8"... in different Java VMs. Mike Kay -----Original Message----- From: David Halsted [mailto:halstedd@xxxxxxxxxx] Sent: 29 January 2000 22:57 To: xsl-list@xxxxxxxxxxxxxxxx Cc: SAXON XSL Discussion List Subject: Encoding problem If I do <xsl:element name="input"> <xsl:attribute name="name">name</xsl:attribute> <xsl:attribute name="type">text</xsl:attribute> <xsl:attribute name="value"> <xsl:value-of select="@name" /> </xsl:attribute> </xsl:element> and @name contains a numeric Unicode entity, Saxon chokes. On the other hand, if I do <input name="name" type="text" value="{@name}"/> it works fine. Thanks to Steve Tinney for the hint. Mind you, I don't understand why this is so, but I'm content. Dave Halsted XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
Encoding problem, David Halsted | Thread | RE: Encoding problem, sara . mitchell |
Re: transform each character of a s, David Carlisle | Date | Re: transform each character of a s, Phil Lanch |
Month |