There was a bug in the old byteToUnicodeSpec tables (missing 2's in some of
the latter entries, one of which should have been 16e02D8).

So initializeLatin1MapAndEncodings erroneously picked that over the correct
D8.

In a modern image, Sven has fixed the byteToUnicodeSpec (They're parsed
directly from the Unicode site, so at least the hope is they are correct, at
least), but the cache tables have not been updates, one can do this by
executing:

ByteTextConverter initialize.
ByteTextConverter allSubclassesDo: [:each | each
initializeLatin1MapAndEncodings].

Cheers,
Henry



--
View this message in context: 
http://forum.world.st/TextConverter-is-broken-tp4882039p4882079.html
Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Reply via email to