Hi, On Mar 22, 2013, at 5:44 AM, Andreas Jung <li...@zopyx.com> wrote:
> > I don't know much about filesystem encodings but if a FS encoding like > >>>> sys.getfilesystemencoding() > 'ANSI_X3.4-1968' > > is a system-wide setting then it is unlikely that you make an encoding > change a mandatory requirement. 'ANSI_X3.4-1968' is at least returned > on my CentOS and Ubuntu box. Reading up on the VFS unicode handling it appears that we just need to treat everything as bytestrings and encode it ourselves. The locale setting is really just an environment variable influencing library behaviour (like glib) - the kernel doesn't seem to care except for '/' and '\0'. However, you may also need to make sure that your web server treats the unicode URLs correctly and uses UTF-8 as the encoding for looking up the filenames. I have applied a fix forcing the filenames to always be encoded as UTF-8. Christian -- Christian Theune · c...@gocept.com gocept gmbh & co. kg · Forsterstraße 29 · 06112 Halle (Saale) · Germany http://gocept.com · Tel +49 345 1229889-7 Python, Pyramid, Plone, Zope · consulting, development, hosting, operations
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Catalog-SIG mailing list Catalog-SIG@python.org http://mail.python.org/mailman/listinfo/catalog-sig
