This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: 1.7.0-48: [BUG] Passing characters above 128 from bash command line
- From: Alexey Borzenkov <snaury at gmail dot com>
- To: cygwin at cygwin dot com
- Date: Wed, 3 Jun 2009 21:52:59 +0400
- Subject: Re: 1.7.0-48: [BUG] Passing characters above 128 from bash command line
- References: <3f0ad08d0905290813m39999f81q918e94e3c960eb3f@mail.gmail.com> <3f0ad08d0905290852xe41338alfda89c622f92f677@mail.gmail.com> <4A200BC0.9010704@sidefx.com> <e2480c70905291142o2bcc65ccw2287d175dbd09dd5@mail.gmail.com> <4A204149.2050009@sidefx.com> <e2480c70905291337g6c8bcca7xd0baba79c84629db@mail.gmail.com> <4A2051E5.6060600@sidefx.com> <20090602205440.GF23519@calimero.vinschen.de> <4A26782C.9040207@sidefx.com> <20090603142755.GM23519@calimero.vinschen.de>
On Wed, Jun 3, 2009 at 6:27 PM, Corinna Vinschen
<corinna-cygwin@cygwin.com> wrote:
> What's left as questionable is the LANG=C default case. ÂDue to the
> discussion from the last month we now use UTF-8 as default encoding,
> because it's the only encoding which covers all (valid) characters.
> Sure, we could also convert the command line using the current ANSI
> codepage as Windows does it when calling CreateProcessA in this case.
>
> Maybe we should do that for testing? ÂAnybody having a strong opinion
> here?
I am strongly against it. Because, as I showed earlier, this case:
for filename in `ls`; do
windowsprogram.exe $filename
end
Should work. Since filenames use cygwin's encoding (UTF-8 for C
locale, or the value of LANG), arguments conversion should use it too.
It would be confusing otherwise.
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/