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

Wolfgang Sourdeau developer@opengroupware.org
Thu, 23 Aug 2007 14:27:32 -0400


On 2007-08-23 12:04:57 -0500 St=E9phane Corth=E9sy <stephane@sente.ch> w=
rote:

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

I have already tried that and it didn't change anything. I think this fi=
eld is only meant for the client to understand which kind of encoding it=
 can use.

>From http://www.w3.org/TR/html401/interact/forms.html#adef-accept-charse=
t:

"accept-charset =3D charset list [CI]
    This attribute specifies the list of character encodings for input d=
ata that is accepted by the server processing this form. The value is a =
space- and/or comma-delimited list of charset values. The client must in=
terpret this list as an exclusive-or list, i.e., the server is able to a=
ccept any single character encoding per entity received.

    The default value for this attribute is the reserved string "UNKNOWN=
". User agents may interpret this value as the character encoding that w=
as used to transmit the document containing this FORM element."

I don't know it it is even useful...


Wolfgang