I'm struggling with the way formlib forms handle decoding from forms.  
It looks like this gets set in BrowserView using an  
IUserPreferredCharsets adapter. The default adapter seems to be in  
zope.publisher.http and it looks like latin-1 will be set if there is  
no other charset and I'm having problems with the em-dash and en-dash  
(u'\u2013' and u'\u2013') characters automatically being converted  
from latin-1 when they are being entered as cp1252. For content that  
doesn't through this decoding I have no problems if zpublisher-default- 
encoding is set to cp1252 and the default_charset is set to cp1252 as  
well: decoding with CMFDefault.utils.decode() works just fine.

I suspect I'm missing something basic in the way charsets are handled  
but as it's a windows only IE6 environment, is the easiest solution  
writing an adapter that defaults to cp1252 if there is no  
HTTP_ACCEPT_CHARSET in the request header?

Thanks for any pointers.

Charlie Clark
Helmholtzstr. 20
D- 40215
Tel: +49-211-938-5360
GSM: +49-178-782-6226

Zope-CMF maillist  -  Zope-CMF@lists.zope.org

See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests

Reply via email to