Hi Jean-François!
Doyon, Jean-Francois wrote:
+1
Especially since the FSMetadata class isn't a mix-in so it turns out
getting to the site instance's encoding isn't easy.
Want me to file a bug?
Florent Guillaume wrote at 2006-9-4 20:38 +0200:
I'd say it would be cleaner to let the .metadata
2006 3:00 PM
To: Florent Guillaume
Cc: Doyon, Jean-Francois; Zope CMF
Subject: Re: [Zope-CMF] Re: .metadata files, latin-1 vs. unicode,and
encoding errors
Florent Guillaume wrote at 2006-9-4 20:38 +0200:
>I'd say it would be cleaner to let the .metadata specify its own
>encoding, for insta
Florent Guillaume wrote at 2006-9-4 20:38 +0200:
>I'd say it would be cleaner to let the .metadata specify its own encoding,
>for instance with a
># coding: utf-8
>at the top, and pasrse that in FSMetadata.
I find this a good suggestions -- but would use the declaration syntax
used also in (e.g.)
pe-CMF] Re: .metadata files, latin-1 vs. unicode,and encoding errors
Hi Jean-François!
Doyon, Jean-Francois wrote:
My app started throwing unicode errors, and I've tracked it down to the fact I
have accents in .metadata files.
This becomes a problem when a unicode string sneaks into the page
ehalf Of yuppie
Sent: August 28, 2006 2:25 PM
To: Doyon, Jean-Francois; Zope-CMF List
Subject: [Zope-CMF] Re: .metadata files, latin-1 vs. unicode,and encoding errors
Hi Jean-François!
Doyon, Jean-Francois wrote:
> My app started throwing unicode errors, and I've tracked it down to the f
Hi Jean-François!
Doyon, Jean-Francois wrote:
My app started throwing unicode errors, and I've tracked it down to the fact I
have accents in .metadata files.
This becomes a problem when a unicode string sneaks into the page to be
rendered, at which time StringIO.getvalue() bombs.
Normally I
