[Seaside] WAKomEncoded vs WAKomEncoded39

goran at krampe.se goran at krampe.se
Thu Nov 22 22:45:26 UTC 2007


I am setting up a Seaside app and... well, since I am from Sweden we
have funny chars to deal with. So I picked WAKomEncoded39 and all was
well to begin with (3.9, latest KomHttpServer).

Then I started adding forms with text fields and hey, they enter Squeak
as utf8!

Hrm. So I started looking and realized that, ok, funny enough
WAKomEncoded inherits from WAKomEncoded39 and actually only additionally
*does* the utf8ToSqueak thing on the posted fields - which is what I am
lacking. So... well, fine. Everything seems dandy using WAKomEncoded!

So I am serving utf8, and all my funny chars are nice inside Squeak
(iso) - but... is the confusion here due to late changes in
KomHttpServer or?

regards, Göran

More information about the seaside mailing list