Products.PageTemplates.unicodeconflictresolver: doubtful determination of server encoding
Bug #254570 reported by
Dieter Maurer
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Zope 2 |
Won't Fix
|
Wishlist
|
Unassigned |
Bug Description
The unicode resolver registered by default "Products.
looks at the request and determines from its prefered encodings the encoding used by the server.
This is very doubtful as the server probably will never base its encoding on the preferences of its (varying) clients.
I suggest to add a new configuration option telling Zope which encoding is typically used by the server. In principle, the Python default encoding could be used for this, but apparently the Python community does not like to use this default encoding. That calls for a new option.
To post a comment you must log in.
As discussed internally, it is legitimate to take the preferred charsets into account. As said there is no official API for determine the internal encoding of the backend application. This is better than ignoring it. The only solution would be to introduce an official API in form of an utility that could be registered with a site-manager returning the backend encoding