On Wed, Sep 22, 2010 at 09:24:11AM +0100, Chris Withers wrote:
> On 21/09/2010 23:59, Marius Gedminas wrote:
> > If this means Zope2-the-application becomes unusable out of the box if
> > you've non-ASCII data in your database, then I'm -1.
>
> I'd call having the odd '?' shown in pages and a warn
On Wed, Sep 22, 2010 at 09:34:59AM +0100, Chris Withers wrote:
> On 22/09/2010 03:50, Andreas Jung wrote:
> > I also strongly object such a change in the default behavior.
>
> I'm sorry, but WHAT?
>
> > I did a
> > lot of testing of the current implementation and configuration with
> > various br
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chris Withers wrote:
> On 22/09/2010 09:58, Andreas Jung wrote:
>> If you think it is crap then I cam happy to accept that (and I don't
>> mind much because Zope 2 is not my radar right now). You are committer
>> and you can fix my crap. Blame me for h
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chris Withers wrote:
> On 21/09/2010 21:18, Andreas Jung wrote:
>> I can not recall all details but at the time of the integration of the
>> Zope 3 ZPT engine the unicode resolver approach was the best thinkable
>> solution for dealing all possible edg
On 22/09/2010 09:58, Andreas Jung wrote:
> If you think it is crap then I cam happy to accept that (and I don't
> mind much because Zope 2 is not my radar right now). You are committer
> and you can fix my crap. Blame me for having written this crap but you
> could also blame me for having on this
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chris Withers wrote:
> On 22/09/2010 03:50, Andreas Jung wrote:
>> I also strongly object such a change in the default behavior.
>
> I'm sorry, but WHAT?
>
>> I did a
>> lot of testing of the current implementation and configuration with
>> various b
On 21/09/2010 21:18, Andreas Jung wrote:
> I can not recall all details but at the time of the integration of the
> Zope 3 ZPT engine the unicode resolver approach was the best thinkable
> solution for dealing all possible edgecase where encoding issues may pop
> *for the sake of backwards compatib
Am 22.09.2010, 10:24 Uhr, schrieb Chris Withers :
> I'd call having the odd '?' shown in pages and a warning in your logs
> telling you about the problem in clear terms versus sporadic total
> failures by way of unicode exceptions a lot more usable, rather than the
> current situation, which is co
On 22/09/2010 03:50, Andreas Jung wrote:
> I also strongly object such a change in the default behavior.
I'm sorry, but WHAT?
> I did a
> lot of testing of the current implementation and configuration with
> various browsers and Zope applications and add-ons in order to make the
> Zope 3 ZPT engi
On 21/09/2010 23:59, Marius Gedminas wrote:
> On Tue, Sep 21, 2010 at 07:39:46PM +0100, Chris Withers wrote:
>> So, would anyone object if I change the default, on both trunk and the
>> 2.12 branch to some variant of:
>>
>> class BasicEncodingConflictResolver(object):
>>implements(IUnicodeE
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Marius Gedminas wrote:
> On Tue, Sep 21, 2010 at 07:39:46PM +0100, Chris Withers wrote:
>> So, would anyone object if I change the default, on both trunk and the
>> 2.12 branch to some variant of:
>>
>> class BasicEncodingConflictResolver(object):
>>
On Tue, Sep 21, 2010 at 07:39:46PM +0100, Chris Withers wrote:
> So, would anyone object if I change the default, on both trunk and the
> 2.12 branch to some variant of:
>
> class BasicEncodingConflictResolver(object):
> implements(IUnicodeEncodingConflictResolver)
>
> def resolve(se
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
First, cool down for a moment.
Second, I discussed all those issues with my special friend in some
Launchpad ticket years ago (+ a huge amount of private discussions).
I can not recall all details but at the time of the integration of the
Zope 3 ZPT e
Am 21.09.2010, 20:39 Uhr, schrieb Chris Withers :
> So, would anyone object if I change the default, on both trunk and the
> 2.12 branch to some variant of:
> class BasicEncodingConflictResolver(object):
> implements(IUnicodeEncodingConflictResolver)
> def resolve(self, context, text, e
On 21/09/2010 19:32, Hanno Schlichting wrote:
> Because there's not all that many people left using plain Zope 2 and
> upgrading to new versions.
Well, or they assume they must be doing something wrong because of this
default.
> The rest is using Plone, which has its own version of this:
>
> def
On Tue, Sep 21, 2010 at 8:17 PM, Chris Withers wrote:
> I like the idea of IUnicodeEncodingConflictResolver, ...
[...]
> Why has no-one noticed this?
Because there's not all that many people left using plain Zope 2 and
upgrading to new versions.
The rest is using Plone, which has its own versi
Am 21.09.2010, 20:17 Uhr, schrieb Chris Withers :
> To boot, when things go wrong, nobody suspects this miserable little
> turd because it's hides itself nicely by just returning the original
> text, leaving the bemused reader to wonder why some UA's fail and some
> succeed, pointing the finger in
Hi All,
It's been a a while since I had a good rant on a Zope list, but this
really takes the biscuit.
Andreas, what on *earth* were you thinking with PreferredCharsetResolver?!
I like the idea of IUnicodeEncodingConflictResolver, but
PreferredCharsetResolver is in the realms of totally batshi
18 matches
Mail list logo
