[Zope-CMF] CMFSetup: non-ascii text

Florent Guillaume fg at nuxeo.com
Mon Jul 4 09:01:30 EDT 2005

Dieter Maurer  <dieter at handshake.de> 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 Guillaume, Nuxeo (Paris, France)   CTO, Director of R&D
+33 1 40 33 71 59   http://nuxeo.com   fg at nuxeo.com

More information about the Zope-CMF mailing list