Re: [xsl] Problems with apersand (&) when trying to dynamically define a character value as an attribute value.

[David Carlisle <davidc@xxxxxxxxx>]

> Have I misunderstood what you meant? 
No but the string generation wasn't quite right there are some other
banned blocks besides 0-32, which need to be avoided, xml 1..1 char
production is

[2]   	Char	   ::=   	[#x1-#xD7FF] | [#xE000-#xFFFD] | [#x10000-#x10FFFF]	
/* any Unicode character, excluding the surrogate blocks, FFFE, and FFFF. */
[2a]   	RestrictedChar	   ::=   	[#x1-#x8] | [#xB-#xC] |
                                    [#xE-#x1F] | [#x7F-#x84] | [#x86-#x9F]

from which you see that after 31, the next banned character follows
xD7FF, ie is xD800 the character thatyou (or saxon) reported.
	<xsl:value-of select="
  if ((55295 &lt; .) and (. &lt; 57344) then ' ' else codepoints-to-string(.)"/>
would sort out the -#xD7FF to #xE000- range for example.

David