Re: [RFC] i18n.pathencoding

From: Junio C Hamano <gitster@pobox.com>
Date: Sep 4, 2012, 17:19 UTC
Message-ID: <7vvcftbt8o.fsf@alter.siamese.dyndns.org>
In-Reply-To: <CACsJy8A1GnhTeMzwXwA1C96pp0ERskxZC=SO+QE2__pfwmChow@mail.gmail.com>

Nguyen Thai Ngoc Duy <pclouds@gmail.com> writes:

Show 16 quoted lines

> On Sat, Sep 1, 2012 at 1:11 PM, Torsten Bögershausen <tboegi@web.de> wrote:
>> diff --git a/parse-options.c b/parse-options.c
>> index c1c66bd..5840c18 100644
>> --- a/parse-options.c
>> +++ b/parse-options.c
>> @@ -476,7 +476,7 @@ int parse_options(int argc, const char **argv, const char *prefix,
>>                 usage_with_options(usagestr, options);
>>         }
>>
>> -       precompose_argv(argc, argv);
>> +       reencode_argv(argc, argv);
>>         return parse_options_end(&ctx);
>>  }
>
> If you have to re-encode command line arguments, what about paths
> coming --stdin or a file?

That problem is inherited from the MacOS precompose topic this one builds on. Not that it is unimportant to fix, though.