[Seaside-dev] Re: what happened to WASqueakUtf8Codec?

[Philippe Marschall]

2009/2/15 Philippe Marschall <philippe.marschall at gmail.com>:
> It contained a much optimized UTF8 encoding algorith that was much
> faster than the default UTF8TextConverter. Second I'm unhappy with
> GenericCodec >> #url. Just because some document somewhere says
> something that doesn't mean nothing. If you run ISO-8859-1 then your
> URL encoding will be ISO-8859-1 no matter what specs and Wikipedia
> entries say.

Oh and something else:
TextConverter newForEncoding: 'ISO-8859-1'
returns nil. That's why the old code had a special case for that one.
You see there was a reason the old code was like this. It was tweaked
and tested over a long period. If you don't understand why something
is there please ask. At the very least just test whether it works.

Cheers
Philippe