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

[Helge Hess]

On 23.08.2007, at 20:27, Wolfgang Sourdeau wrote:
> I have already tried that and it didn't change anything. I think  
> this field is only meant for the client to understand which kind of  
> encoding it can use.

Yes. Didn't Google even include the charset as a query parameter in  
various URLs?
The real bug is that the browser do not specify the charset in the  
content-type (and since there are different opinions on the default,  
they should *always* specify the charset).

Anyways, I think the usual way it works is that the form values are  
in the same encoding like the originating page. If UTF-8 is used  
everywhere, it should be quite OK.

*Though* the default charset for HTTP is Latin-1, not UTF-8. So this  
is non exactly correct.
Putting the behaviour into a delegate method sounds like a sane thing  
to do, though using UTF-8 as the default (instead of Latin1) _might_  
be viable too (would need to be checked against OGo which does rely  
on Latin1).

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