jtu...@objektfabrik.de
unread,Oct 5, 2011, 11:40:12 AM10/5/11Sign in to reply to author
Sign in to forward
You do not have permission to delete messages in this group
Sign in to report message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to va-sma...@googlegroups.com
I have a long standing problem with VA Smalltalk and Seaside. It's been there since Seaside is supported on VA ST.
The problem is: if I do a serialize of a form or a single input field via Ajax, the contents of the field will always be received as UTF-8 even though my app is configured to deliver pages in ISO-8859-15.
Normal callbacks work like a charm, but not Ajax serialize()-calls like this:
html form: [
html text: 'You can enter test text here:'.
html textInput
callback: [:txt| self serializedString: txt];
with: (self serializedString ifNil: ['Häusle in Böblingen für 100 €']).
html break.
html anchor
onClick: ((html jQuery ajax serializeForm),
...
with: 'Serialize with Ajax'.
]
I have tried overriding almost every method in the system that sets the content type of pages, ajax calls, JSON gets etc. I also tried exchanging the WASstServerAdapters Null Codec vs. the GRVASTLatin1Codec, in probably all possible combinations, but the result on the server will always be the String 'HÀusle in Böblingen fÌr 100 €'.
Serializing twice will make things worse.
So my question is:
Has anybody found a solution for the problem (and no, setting the Application's charSet to utf-8 is no solution at all!).
Will we really have to wait for VA ST to come with UTF-8 Support to avoid this problem? If so, when is this going to happen. I will have to port our project to Pharo for an important demo if we don't see a solution for this soon...
Thanks for reading
Joachim