Dieter Maurer <[EMAIL PROTECTED]> wrote: > Florent Guillaume wrote at 2005-7-1 20:43 +0200: > > ... > >The problem is on import, you don't really know if a non-ascii string > >should be stored as unicode or as an encoded str. And the software > >may break if it gets something it doesn't expect... > > That's why the whole Python world including Zope (it does with Zope 3) > and CMF should follow Java and require "for text always use Unicode". > And for non-text, CMFSetup should use a specialize "binary" type.
Again, I couldn't agree more. My problem here is backward compatibility. Florent -- Florent Guillaume, Nuxeo (Paris, France) CTO, Director of R&D +33 1 40 33 71 59 http://nuxeo.com [EMAIL PROTECTED] _______________________________________________ Zope-CMF maillist - Zope-CMF@lists.zope.org http://mail.zope.org/mailman/listinfo/zope-cmf See http://collector.zope.org/CMF for bug reports and feature requests