[Seaside] [VAST] Character Encodings in JQAjax>>#serializeForm
Joachim Tuchel (Lists)
lists at objektfabrik.de
Mon Sep 20 08:08:43 UTC 2010
I was afraid of this answer, especially the "you cannot do much about it" part
So for as long as VAST is not using UTF-8 internally, I can only try to make
"all" Seaside-related traffic be de/encoded between UTF-8 and my Smalltalk
If I understand correctly, in Pharo and Squeak this is achieved by using an
encoding/decoding web server (WAKomEncoded???) and not by any Seaside-related
I wonder if I can find ways to configure SST or the SST-Seaside-Adapter to
de/encode all traffic.
I'll try to find out in VAST-land and will post my results here (because I think
the guys who possibly know are not (yet) hanging around here...
Thanks for looking at this
Philippe Marschall <philippe.marschall at gmail.com> hat am 17. September 2010 um
> 2010/9/17 Lukas Renggli <renggli at gmail.com>:
> > Hi Joachim,
> > Could this be related to
> > <http://code.google.com/p/seaside/issues/detail?id=585>? This issue
> > was recently fixed in Pharo and might not have been ported to VA yet.
> To me it looks more like jQuery always uses utf-8 in serialize() .
> It doesn't look like there's much you can do about it. You might want
> to to post in their forums. It looks like your only option is to add a
> bastard processing step that detects this and converts from utf-8 to
> Latin 9.
>  http://api.jquery.com/serialize/
> seaside mailing list
> seaside at lists.squeakfoundation.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the seaside