default fsenc patch

Martin Pool mbp at
Mon Jan 23 22:52:24 UTC 2012

On 24 January 2012 09:11, Toshio Kuratomi <a.badger at> wrote:
> To someone like us who is using a UTF-8 locale, it may seem entirely
> reasonable that we should simply ask that those people switch to using
> utf-8.  However, in countries where non-utf-8 character sets are the norm,
> people are unlikely to want to go through the trouble of A) switching
> charsets just to use bzr or B) figuring out how to rename all of their files
> from their native charset to the less efficient (for their languages) utf-8
> and then keeping them that way as they get new files from friends,
> colleagues, and the internet.

I'm definitely not saying people need to switch their files to UTF-8;
that would be totally unreasonable.

bzr already has the approach of treating filenames as real unicode: it
decodes them when reading them from disk, according to whatever the
fsenc is.

The issue I'm talking about here is just what to do when the user has
no fsenc specified by their locale.  Python/glibc effectives assumes
this means "ascii" and so it errors out when there are non ascii
strings.  We discussed whether it would be better to assume utf-8


More information about the bazaar mailing list