RE: [Xsltsl-users] string.xsl on XP?

[Reinout v. R. <re...@va...>]

On Tue, 15 Apr 2003, Karl Kieninger wrote:

> Yes, it give a line annd postion.
>
> Invalid unicode character.
> Error processing resource
> 'file:///D:/Temp/string.xsl'.
> Line 46, Position 5714

Hm. It's unicode character 10428 he's complaining about then. (the
first one in the 10??? series). That's a perfectly valid unicode
character, see http://www.unicode.org/charts/PDF/U10400.pdf

I've found a test page for that range of characters (the 'deseret'
set) at http://home.att.net/~jameskass/deserettest.htm , you might
want to try that one in IE6.

http://www.alanwood.net/unicode/explorer.html has some info on unicode
and IE. From what I gather from the last 2 paragraphs: IE should
support all unicode character references (which is what is in
strings.xsl). There might be something with having to setup a font or
so.


All in all, it seems like an IE bug to me. That list of unicode
characters in string.xsl was put in there by me. For that, I wrote a
small script that copied the *official* unicode character list. So, it
*should* be correct.

I'm very curious about what turns out to be the problem in the end :-)

greetings,

Reinout

-- 
Reinout van Rees - re...@va... | "Utter. Crap."
                                       |
http://vanrees.org/  http://bcxml.net/ | -- Blackadder