1.7.1: unable to run the a bash script resides in chinese path using: c:\cygwin\bin\bash --login script.
Sat Feb 20 04:01:00 GMT 2010
On Fri, 19 Feb 2010 20:29:27 +0000, Andy Koppe <firstname.lastname@example.org>
>Looks like there's some sort of GBK vs UTF-8 mixup going on, because
¡éå©å°' is the same byte sequence in GBK as 'æ°æ¥æç®' is in UTF-8:
Wonderful analysis! Could you please give me some hints on the tools
used by you to obtain this conclusion?
>I take it the actual directory name is 'æ°æ¥æç®'? (Babelfish seems to be
>able to make some sense of that one but not the other.)
Yes, you're right. The actual directory name is 'æ°æ¥æç®'.
>Do you know what the encoding of your batch file is?
> And have you got
>any locale variables (LC_ALL, LC_CTYPE, LANG) set when invoking it?
I'use the following settings in the same batch file:
>>>C:\cygwin\bin\bash --login "%~dp0myscript"
>> I've found a more strange thing: If I change the batch file into the
>> following form, then it will be run smoothly:
>> @echo off
>> C:\cygwin\bin\bash --login %~dp0myscript
>> The QUOTATION MARK in the former is used to deal with the whitespaces
>> appearing in the myscript's pathname, though this is relatively rare
>> case. ?But in the latter case, if there're whitespaces in the
>> myscript's pathname, the batch will fail to run.
>Hmm, perhaps the argument mangling at program startup is using the
>ANSI codepage (i.e. GBK in this case) when it should be using UTF-8?
But, if I convert my batch file into UTF-8 (without BOM, CR/LF line
endings) format, I'll meet the following error:
¡éå©å°/RestoreName4Elsevier.sh": No such
file or directory
.: Hongyi Zhao [ hongyi.zhao AT gmail.com ] Free as in Freedom :.
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
More information about the Cygwin