On 2 March 2011 10:00, yuppie <y.2011@wcm-solutions.de> wrote:
Hi Martin!
Martin Aspeli wrote:
- After traversal and before calling the object ZPublisher.Publish.publish should figure out if the object expects zope.publisher behavior. Either we use a new interface for this or we use zope.publisher.interfaces.browser.IBrowserPage: AFAICS in Zope 2 land only zope.formlib and z3c.form based views implement IBrowserPage.
Isn't this in zope.browserpage now?
No.
- plone.z3cform uses a modified version of processInputs and doesn't use setPageEncoding. Can anybody explain why? I guess that are no z3c.form specific reasons. Maybe the changes can be merged back to Zope?
processInputs() in Five was very buggy. I thought I'd merged those changes into Zope 2?
Well. You were the last person who touched both. But the changes are quit different:
http://svn.zope.org/Zope/trunk/src/Products/Five/browser/decode.py?rev=11528... http://svn.zope.org/plone.z3cform/trunk/plone/z3cform/z2.py?rev=109071&view=...
Is there still anything in plone.z3cform that should be merged into Zope 2?
I don't know what setPageEncoding() does, though.
It sets a response Content-Type header with the first charset processInputs tries for decoding.
Is the charset of the request necessarily the right choice for the response? In Plone we always serve UTF-8 encoded. Laurence