Date: Fri, 17 Apr 2009 17:01:33 +0200
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: UTF-8 problem/bug with Cygwin 1.7
Message-ID: <20090417150133.GC9559@calimero.vinschen.de>
Reply-To: cygwin@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
References: <49E75CE7.4010004@danbbs.dk> <49E7770A.8080702@danbbs.dk> <49E77B04.8020904@danbbs.dk>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <49E77B04.8020904@danbbs.dk>
User-Agent: Mutt/1.5.19 (2009-02-20)
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

On Apr 16 20:37, Gunnar Degnbol wrote:
>
> David Korn skrev:
>>> I have a strange problem with UTF-8 characters when running bash from 
>>> the Windows command line. I hoped it would go away with the new  
>>> Cygwin 1.7.0-46, but it is still there. Now I have simplified it down 
>>> to setting LANG=en_US.UTF-8 and running bash -c "echo Ł" (where 'Ł'  
>>> can be any non-ascii character):
>> Can't reproduce this with either -45 or -46:
> I just tried with a new Cygwin installation in a VM, and I still get the  
> problem.

When starting from a non-Cygwin process, the argv array is evaluated
from the Windows command line.  Part of it is globifying arguments
and creating file lists when necessary (since the Windows parent will
not do it for the Cygwin process.  This globifying code was not
multibyte aware.  That should be fixed now in CVS.


Thanks for the report,
Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat

--
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/