Florent Guillaume wrote at 2005-7-4 15:01 +0200:
>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
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
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 Zop
On 1 Jul 2005, at 20:17, Dieter Maurer wrote:
Florent Guillaume wrote at 2005-7-1 17:19 +0200:
In many places, CMFSetup exports and imports things like titles and
descriptions. For instance, for the workflow states and transitions.
These fields can often, outside the USA, contain non-ascii stri
Florent Guillaume wrote at 2005-7-1 17:19 +0200:
>In many places, CMFSetup exports and imports things like titles and
>descriptions. For instance, for the workflow states and transitions.
>These fields can often, outside the USA, contain non-ascii strings.
>How do we export and reimport them ?
