last time I checked
there were some differences between Microsoft Unicode and ISO Unicode.
it was some years ago, by some I mean 4, but at that point in time it was
necessary to download special fonts to properly
render Russian and the characters above that because there Unicode was offset by a byte or so somewhere after English.
Don't know if the problem still exists , don't know if it's useful for you to know, but it is the type of bug they are
unlikely to fix because it breaks compatibility with non windows platforms, which usually falls under Microsoft's we're big and don't care umbrella.
hope it is useful,
Christopher-----Original Message-----
From: Keith Rogers [mailto:[EMAIL PROTECTED]
Sent: Monday, March 08, 2004 8:45 AM
To: [email protected]
Subject: Re: Avoiding the escaping UTF-8 unicode textNo question - XMLSpy. Been using it for about 3 1/2 years. You need a Unicode font installed, of course.Don't know if this is your problem, but what happens in Windows UTF-8, e.g., in Notepad, is that the file starts with the UTF-8 encoding bytes (actually, UTF-16 flags FFFE or FEFF encoded as UTF-8). Not every parser likes to see those.. (Older versions of XMLSpy, for instance, didn't but the new version doesn't complain.)I use vi to open UTF-8 (DTD/XML/XSL) files I get from other sources (localizers) and remove the 3 leading flag bytes if I see them. XMLSpy does not write those bytes itself. This seems to keep the Linux versions of Xerces/Xalan happy.
Nick Bastin <[EMAIL PROTECTED]> wrote:...
Does anybody have a favorite XML editor for windows that correctly
supports unicode?Also, we're having some trouble moving cross-platform with UTF-8 encoded files - moving between Solaris and Win32 seems to be a pretty good way to screw up your files.
