X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-0.7 required=5.0 tests=BAYES_20,SPF_PASS X-Spam-Check-By: sourceware.org Message-ID: <53802.99.237.216.211.1243713955.squirrel@www.sidefx.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 From: "Edward Lam" To: cygwin AT cygwin DOT com User-Agent: SquirrelMail/1.4.9a MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com 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 > screen?) Ok, so where's the bug tracker so I can log a bug? -Edward -- 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/