On Tue, Sep 30, 2008 at 11:12 AM, <[EMAIL PROTECTED]> wrote: > The one thing it doesn't do is expose the decoding rules for the higher- > level applications to deal with. I am pretty sure I don't understand how > the interaction between filesystem encoding and user locale works in that > case, though, so I can't immediately recommend a way to do it.
You can ask what the filesystem encoding is with sys.getfilesystemencoding(). On my Linux box I can make this return anything I like by setting LC_CTYPE=en_US.<whatever> (as long as <whatever> is a recognized encoding). There are probably 5 other environment variables to influence this. :-( Of course that doesn't help for undecodable filenames, and in that case I don't think *anything* can help you unless you have a lot of additional knowledge about what the user might be doing, e.g. you know a few other encodings to try that make sense for their environment. -- --Guido van Rossum (home page: http://www.python.org/~guido/) _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
