default fsenc patch

[Martin Pool]

On 24 January 2012 14:59, Eli Zaretskii <eliz at gnu.org> wrote:
>> From: Martin Pool <mbp at canonical.com>
>> Date: Tue, 24 Jan 2012 09:52:24 +1100
>> Cc: Bazaar <bazaar at lists.canonical.com>
>>
>> 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
>> instead.
>
> On Windows, it should be UTF-16 instead (assuming that "wide"
> a.k.a. Unicode APIs are used).

Yes, this issue only arises on non-Apple Unix.  On Windows and Mac OS
X the file name encoding is defined by the OS, independent of locale.

-- 
Martin