---- On Thu, 05 Aug 2010 08:37:34 -0700 Norbert Hartl wrote ----
I'm trying to port the newest XML Parser from squeaksource to gemstone. In XML-Parser-AlexandreBergel.73 there is a unicode test introduced with a longer unicode xml snippet. From this release on I cannot load or merge anything.
Besides that the xml snippet looks very strange it loads in pharo but not in gemstone. Unpacking the mcz on the console and examine the content showed that the encoding is indeed weird. I don't know what it is but it is neither ascii nor utf-8. Pharo loaded the snippet into a WideString instance.
How does monticello handle WideString instances when written to a file?
Norbert
It appears those were added to ensure the parser didn't choke on non-UTF-8 input. However, it probably should choke on such input (except in external unparsed entities), and regardless, if such a test is to be added, the non-UTF8 characters should not appear in the literal source code of a method; this was the source of subtle image and package character encoding issues like the one you encountered. I have removed it.