+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? J.F. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dieter Maurer Sent: September 5, 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 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.) Python. -- Dieter _______________________________________________ Zope-CMF maillist - Zope-CMF@lists.zope.org http://mail.zope.org/mailman/listinfo/zope-cmf See http://collector.zope.org/CMF for bug reports and feature requests _______________________________________________ Zope-CMF maillist - Zope-CMF@lists.zope.org http://mail.zope.org/mailman/listinfo/zope-cmf See http://collector.zope.org/CMF for bug reports and feature requests
