[Seaside] WAKomEncoded vs WAKomEncoded39

Sebastian Sastre ssastre at seaswork.com
Fri Nov 23 17:04:04 UTC 2007

Hi Goran,

	I confirm. I was needing latin chars too and WAKomEncoded39 was
working fine until about a month (or less). When I loaded all in a fresh
image the input in forms started to bring wrong chars when latin chars where

	Now I'm starting Seaside with WAKomEncoded and all works like a

Sebastian Sastre

> -----Mensaje original-----
> De: seaside-bounces at lists.squeakfoundation.org 
> [mailto:seaside-bounces at lists.squeakfoundation.org] En nombre 
> de goran at krampe.se
> Enviado el: Jueves, 22 de Noviembre de 2007 20:45
> Para: seaside at lists.squeakfoundation.org
> Asunto: [Seaside] WAKomEncoded vs WAKomEncoded39
> Hi!
> 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
> _______________________________________________
> seaside mailing list
> seaside at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

More information about the seaside mailing list