On Sun, May 16, 2010 at 22:57, Alexandre Bergel <alexandre@bergel.eu> wrote:
I will check your code today.
Thanks. Thinking of it, it's not really an encoding problem, rather a bug in the entity->character conversion. I guess there should be a similar test where there is an actual ellipsis character in the xml, instead of the entity. For the context, I was trying to use the twitter component in pier, to display http://twitter.com/rmod_inria (or the XML feed file, which has the ellipsis character literally as well). And now I realize our server will not be able to connect outside its DMZ, so I won't be able to use the fix :D
On 16 May 2010, at 13:35, Damien Pollet wrote:
Hi,
I have a failing test to show the problem, but I can't commit to the XMLSupport squeaksource, so I attach the MCZ here. Basically, if I parse an UTF-8 document with an entity like … (ellipsis), I don't get a Character with the correct #codePoint.
Cheers,
-- Damien Pollet type less, do more [ | ] http://people.untyped.org/damien.pollet <XML-Parser-DamienPollet.75.mcz>
-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel  http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
-- Damien Pollet type less, do more [ | ] http://people.untyped.org/damien.pollet