[OGo-Developer] multipart/form-data and text encoding

Stéphane Corthésy developer@opengroupware.org
Wed, 29 Aug 2007 23:15:42 +0200


On Aug 25, 2007, at 1:10 AM, Helge Hess wrote:

> On 23.08.2007, at 19:04, Stéphane Corthésy wrote:
>> I think I had the same kind of problem with WebObjects, and solved  =

>> it by setting the 'accept-charset' attribute on the form element:  
>> this tells the client to use the passed charset, not a  
>> 'random' (server's POV) one.
>
> Hm, actually this maked me wonder whether we should always set the  
> WOForm accept-charset to the response contentEncoding() if not  
> specified otherwise.
> This would probably make the form behaviour more predictable?


That is a good idea.


> Actually: does someone know which browsers submit forms in  
> encodings other than the encoding of the originating HTML page?


IIRC, I had troubles with Windows IE 6, which was sending me some  
Windows Latin1 chars which are not in ISOLatin1 table (some quote  
character). I think some clients use their system default encoding:  
WinLatin1 from Windows, MacOSRoman from MacOS 9.

Stéphane


> Thanks,
>   Helge
> -- 
> Helge Hess
> http://www.helgehess.eu/
>
>
> --
> OpenGroupware.org Developer
> developer@opengroupware.org
> http://mail.opengroupware.org/mailman/listinfo/developer