[z3-five] unicodes and strings in Zope 2.9's ZPT with Zope 3's i18n

[Chris Withers]

Martijn Faassen wrote:
> What the right way should be for existing Zope 2 applications I do not 
> know.

Yes, the particular problem I see is with persistent objects that have 
encoded strings as attributes. How did you guys manage the upgrading of 
existing Silva instances which were created when you still used encoded 
strings everywhere?

> For *new* Zope 2 applications, my strong recommendation would be to 
> store human-readable text as unicode, and if your text is stored 
> externally (file, rdb), to decode it into unicode as soon as possible 
> when it enters your application.

Totally agreed, although I'm not sure Zope 2's publisher helps as much 
as it should do, and I doubt any of the Zope DA's are focused this way :-S

Chris

-- 
Simplistix - Content Management, Zope & Python Consulting
            - http://www.simplistix.co.uk