On Saturday 28 Sep 2002 4:38 pm, Florent Guillaume wrote: > > > (yes, this sucks. The problem is that browsers dont specify the > > > character encoding used in form submissions. At some point we need to > > > discuss the way forward on this issue....)
> Just to be clear, this is an HTML attribute of the <form> tag. For > instance: > > <form action="foo" ... accept-charset="UTF-8"> > ... > </form> > > This instructs the browser it should send the content of the form in the > accepted charset. Yes, accept-charset could be part of a full solution to this problem, but I dont think it is a whole solution.... Are you suggesting that a method could assume its form submissions would always be made in utf-8? That would cause problems if a submission was made from: * some other form that didnt have an accept-charset * some non-browser code that synthesizes http requests A further problem is that we want this decoding to be performed in ZPublisher, but that that point in the publishing process it doent know which method is going to be called. That means the utf8 assumption cant be made independantly for each method. One answer to this problem is when browsers include the charset attribute in "multipart/form-data" POST requests. ZPublisher knows unambiguously what encoding was used by the browser. Sadly I cant see a nice way to do the same for GET requests _______________________________________________ Zope-Dev maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
