Posted by jtuchel on Oct 06, 2011; 8:04am
URL: https://forum.world.st/VAST-Seaside-and-Ajax-Serialization-tp3874926p3877363.html

Hi,

I've prepared a Mini-Test Application and attached it here as a filein for VAST.

Once you've loaded the app, it will show an input field with the text 'Häusle in Böblingen für 100 €'. You can do a form submit by clicking on the submit button and see the results in the input field: the very same text as is was in the input field.
Clicking on the Link for Ajax Serialization renders the serialized string that was sent back to the server using jQuery and Ajax (XMLHttpRequest) You can clearly see that all the non-7 bit ASCII-characters get screwed, because the Browser (Firefox 7.0.1 in my case) sends them as UTF-8, although the page is rendered with a Charset setting of iso-8859-15.

I've spent quite a while on approaches to force the Ajax callback to send with 8859-15 encoding, but obviously haven't found a solution.

My guess is that this can only be solved by switching the app to utf-8 and adding a correct Codec (The "unfinished" GRVASTUtf8Codec) to the Sst Adapter.

...because implementing the same component in the latest Seaside-3.0.6 oneclick - Image works like a charm if the app is registered as a utf-8 application and the Comanche Adapter is switched to utf-8 encoding, while using an 8859-15 encoding in the Comanche Adapet shows the very same behaviour on Pharo as it does on VAST.

Any ideas?

--
You received this message because you are subscribed to the Google Groups "VA Smalltalk" group.
To view this discussion on the web visit https://groups.google.com/d/msg/va-smalltalk/-/JsgcpMu2W_MJ.
To post to this group, send email to [hidden email].
To unsubscribe from this group, send email to [hidden email].
For more options, visit this group at http://groups.google.com/group/va-smalltalk?hl=en.