This is the mail archive of the
mailing list for the Cygwin project.
Re: 1.7.0-48: [BUG] Passing characters above 128 from bash command line
- From: "Edward Lam" <edward at sidefx dot com>
- To: cygwin at cygwin dot com
- Date: Sat, 30 May 2009 16:05:55 -0400 (EDT)
- Subject: Re: 1.7.0-48: [BUG] Passing characters above 128 from bash command line
I'm reposting since I didn't mean to send this privately.
On Fri, May 29, 2009 17:22, Alexey Borzenkov wrote:
> Here, when I use russian Windows and I don't have LANG set (or when I
> have LANG=en_US.UTF-8), filename will be utf-8 multibyte string. So
> both, russian and european/chinese/japanese filenames will be valid.
> Now there are three possibilities:
How does the filename get to be a utf-8 multibyte string if you created
the filename from an ANSI application? Since it sounds like Russian
Windows uses a code page different from UTF-8.
> And again, you must have misunderstood me. In my opinion: truncation
> is a bug (should use replacement character, or fail exec altogether),
> expecting utf-8 is not (if you tried to cat your copyright.txt on a
> Linux box that uses utf-8, what would you expect to see on the
Ok, so where's the bug tracker so I can log a bug?
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html