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(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.
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 conceptually insane *and* unusable ;-) Chris -- Simplistix - Content Management, Batch Processing & Python Consulting - http://www.simplistix.co.uk