yuppie wrote:
2.) Switch completely to unicode in CMF 2.0:
Sounds like a too big change, don't think we should try that.
I think we all know this is where we need to be eventually, 2.0 seems
the right time to do that, I'd actually prefer this, even though it'll
delay the 2.0 release...
3
Hi!
A while ago I converted many message strings to i18n Message objects.
Unfortunately I didn't think enough about side effects and now the CMF
trunk (CMF 2.0) is in a rather broken state:
Message objects are unicode objects, and unless you use a Localizer or
PTS that returns non-unicode s
