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

[Helge Hess]

On 23.08.2007, at 19:04, St=E9phane Corth=E9sy wrote:
> I think I had the same kind of problem with WebObjects, and solved =20
> it by setting the 'accept-charset' attribute on the form element: =20
> this tells the client to use the passed charset, not a =20
> 'random' (server's POV) one.

Hm, actually this maked me wonder whether we should always set the =20
WOForm accept-charset to the response contentEncoding() if not =20
specified otherwise.
This would probably make the form behaviour more predictable?

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

Thanks,
   Helge
--=20
Helge Hess
http://www.helgehess.eu/