When I use this character map:

<xsl:character-map name="default">
		<xsl:output-character character="&lt;" string="&#60;" />
		<xsl:output-character character=">" string="&#62;" />
		<xsl:output-character character="&amp;" string="&#38;amp;" />
</xsl:character-map>

the unexpected behaviour occurs. When I remove the output-characters
and use this one:

<xsl:character-map name="default"/>

There is no problem.

I am using Saxon 9


On Fri, Nov 13, 2009 at 4:37 PM, Christopher R. Maden <crism@xxxxxxxxx>
wrote:
> Tom T wrote:
>> I'll change my example.
>>
>> Financial Times, "ErdoDan Grubu'na"
>>
>> creates
>>
>> B  <meta name="description"
>> B  B  B  B  B  B  content='Financial Times, &#34;ErdoDan Grubu'na&#34;'
>> B  B  B  B  B  B  />
>>
>> I now have an attribute that is marked up by single quotes containing
>> a single quote. IE6 for one cannot deal with this.
>
> That is clearly in error.
>
> Is this happening *with* your output character mapping in force, or
> *without*?
>
> If without, then the XSLT processor has a severe bug. B If with, then it
> may be happening because of your character mapping.
>
> ~Chris
> --
> Chris Maden, text nerd B <URL: http://crism.maden.org/ >
> bThe State is that great fiction by which everyone tries to live at
> B the expense of everyone else.b b FrC)dC)ric Bastiat, bLbC	tatb
> GnuPG Fingerprint: C6E4 E2A9 C9F8 71AC 9724 CAA3 19F8 6677 0077 C319