I'm doing a configuration so that I get a version running and with green tests in 1.2 You can still use the old one. Stef
Comment #2 on issue 3554 by ryd...@gmail.com: CP1252TextConverter new does not work http://code.google.com/p/pharo/issues/detail?id=3554
That's not the "right" way to do it anymore, ever since ByteTextConverter superclass was introduced. (AFAICT that was before 1.0, but after the soup implementation)
The only methods subclasses should implement are class-side methods: byteToUnicodeSpec encodingNames (languageEnvironment)
I'd suggest updating the Soup package to include the implementation found in Core, which works in all versions of Pharo.
Will it work in Squeak? I'm asking because we're using it in one of our projects and I'll be unhappy if it becomes uncompatible with Squeak the way SmaCC, OB, eCompletion, etc did.
Levente