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

Helge Hess developer@opengroupware.org
Thu, 23 Aug 2007 23:25:19 +0200


On 23.08.2007, at 21:59, St=E9phane Corth=E9sy wrote:
> Server sets the accept-charset attribute, so, when it receives the =20
> form's submission, it should also now which accept-charset had been =20=

> set before.

Well, its the application (XYZ) which sets the accept-charset, and =20
the framework (SOPE) which needs to decode it :-) So the app must =20
tell the framework ..., which brings us to:

> The easiest case, for developer, is to always set accept-charset to =20=

> the same value, and to invoke -[WORequest =20
> setDefaultFormValueEncoding:] (with =20
> formValueEncodingDetectionEnabled set to NO). That's what I did, IIRC.

Hm:
---snip---
- (void)setDefaultFormValueEncoding:(NSStringEncoding)_enc {
   if (_enc !=3D NSUTF8StringEncoding || _enc !=3D =
NSASCIIStringEncoding)
     [self notImplemented:_cmd];
}
---snap---
Looks we miss this for WO compat :-)

Thanks a lot,
   Helge

PS: of course the *real* issue is still the clients which do not =20
properly set the charset in the content-type :-(
--=20
Helge Hess
http://www.helgehess.eu/