Hi!
Laurence Rowe wrote:
> On 2 March 2011 11:29, yuppie wrote:
>> Laurence Rowe wrote:
>>> On 2 March 2011 10:00, yuppiewrote:
Martin Aspeli wrote:
> I don't know what setPageEncoding() does, though.
It sets a response Content-Type header with the first charset
proce
On Wed, Mar 02, 2011 at 09:16:14AM +0100, Wolfgang Schnerring wrote:
> Hello Brian,
>
> it's taken a while, but I finally had a chance to review your branch(es).
Great!
> * Brian Sutherland [2011-02-12 18:57]:
> >> > On Tue, Feb 01, 2011 at 09:32:11AM +0100, Wolfgang Schnerring wrote:
> >> >> I
On Thu, Mar 03, 2011 at 11:04:12AM +0100, Sylvain Viollon wrote:
> On Wed, 02 Mar 2011 09:16:14 +0100
> Wolfgang Schnerring wrote:
>
> > Hello Brian,
> >
>
> Hello,
>
> > it's taken a while, but I finally had a chance to review your
> > branch(es).
> >
> > * Brian Sutherland [2011-02-12 18
Hello,
On Fri, 4 Mar 2011 10:15:18 +0100
Brian Sutherland wrote:
> > In zope.app.wsgi all those idiosyncracies are more or less
> > handled by a WSGI middleware. I guess you can reuse it.
> >
> > One of the purpose of the zope.app.wsgi implementation was to be
> > able to convert the exi
Am 04.03.2011, 08:58 Uhr, schrieb yuppie :
> If we always send UTF-8, their current implementation doesn't make much
> sense to me. Don't know if we really should try to fall back to all the
> charsets mentioned in Accept-Charset. But at least we should *always*
> try UTF-8 decoding first.
Hiya,
Charlie Clark wrote:
> Am 04.03.2011, 08:58 Uhr, schrieb yuppie:
>
>> If we always send UTF-8, their current implementation doesn't make much
>> sense to me. Don't know if we really should try to fall back to all the
>> charsets mentioned in Accept-Charset. But at least we should *always*
>> try UT
On Fri, Mar 04, 2011 at 10:25:59AM +0100, Sylvain Viollon wrote:
>
> Hello,
>
> On Fri, 4 Mar 2011 10:15:18 +0100
> Brian Sutherland wrote:
>
> > > In zope.app.wsgi all those idiosyncracies are more or less
> > > handled by a WSGI middleware. I guess you can reuse it.
> > >
> > > One of
Hi again!
Based on the discussion I modified my proposal:
- Products.Five.browser.decode should be marked as deprecated. It
implements charset negotiation without making sure the 'Vary' header is
set correctly. Fixing this will cause other caching issues.
- The setPageEncoding() function will
Summary of messages to the zope-tests list.
Period Thu Mar 3 12:00:00 2011 UTC to Fri Mar 4 12:00:00 2011 UTC.
There were 106 messages: 8 from Zope Tests, 4 from buildbot at pov.lt, 38 from
buildbot at winbot.zope.org, 11 from ccomb at free.fr, 45 from jdriessen at
thehealthagency.com.
Test f
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> Subject: FAILED : ZTK 1.0dev / Python2.4.6 Linux 64bit
> From: ccomb at free.fr
> Date: Thu Mar 3 22:13:09 EST 2011
> URL: http://mail.zope.org/pipermail/zope-tests/2011-March/033836.html
>
> Subject: FAILED : ZTK 1.0dev / Python2.6.5 Linux 64bit
Am 10.02.2011, 07:07 Uhr, schrieb Christian Theune :
> Who's coming? Who's interested? Any topic suggestions?
I'll be there and hoping to finalise my work on CMF so that we can release
2.3
Is anyone bringing copies of the DZUG Brochure on Zope?
Charlie
--
Charlie Clark
Managing Director
Clar
Hello from the grok department,
On 4 March 2011 11:48, Brian Sutherland wrote:
> On Fri, Mar 04, 2011 at 10:25:59AM +0100, Sylvain Viollon wrote:
>>
>> Hello,
>>
>> On Fri, 4 Mar 2011 10:15:18 +0100
>> Brian Sutherland wrote:
>>
>> > > In zope.app.wsgi all those idiosyncracies are more or le
12 matches
Mail list logo