[Zope-dev] IUnicodeEncodingConflictResolver moronosity

[Marius Gedminas]

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(self, context, text, expression):
>           logging.warn('You should register an '
>                        'IUnicodeEncodingConflictResolver that matches '
>                        'your content')
>           return text.decode('ascii','replace')
> 
> ...and delete that devil spawn turd that is PreferredCharsetResolver?

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.

Marius Gedminas
-- 
http://pov.lt/ -- Zope 3/BlueBream consulting and development
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: Digital signature
Url : http://mail.zope.org/pipermail/zope-dev/attachments/20100922/984f578c/attachment.bin