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

[Helge Hess]

On 23.08.2007, at 21:26, St=E9phane Corth=E9sy wrote:
> As I understand it, if my form has accept-charset=3D"utf-8", then the =20=

> client has to return form data encoded in UTF-8 - not ISOLatin1, =20
> nor any other encoding. Thus, on the server-side, you can safely =20
> decode form data from UTF-8. Isn't it what's happening?

Yes, but how does SOPE know that the previous transaction was in =20
UTF-8 if the client doesn't transfer that information in the content-=20
type? Those are two separate HTTP transactions.

As mentioned we could add a special WOFormCharset form value (like =20
Google does), or we could let the WOApplication decide if it knows =20
that it always generates UTF-8 (which I think is what Wolfgang's =20
patch does).

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