Re: 1.7.0-48: [BUG] Passing characters above 128 from bash command line

[Alexey Borzenkov <snaury at gmail dot com>]

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/