X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-0.6 required=5.0 	tests=AWL,BAYES_20,SPF_PASS
X-Spam-Check-By: sourceware.org
Message-ID: <4A26AB81.3070408@sidefx.com>
Date: Wed, 03 Jun 2009 12:57:37 -0400
From: Edward Lam <edward AT sidefx DOT com>
User-Agent: Thunderbird 2.0.0.21 (Windows/20090302)
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: 1.7.0-48: [BUG] Passing characters above 128 from bash command   	line
References: <3f0ad08d0905290852xe41338alfda89c622f92f677 AT mail DOT gmail DOT com> 	 <4A204149 DOT 2050009 AT sidefx DOT com> 	 <e2480c70905291337g6c8bcca7xd0baba79c84629db AT mail DOT gmail DOT com> 	 <4A2051E5 DOT 6060600 AT sidefx DOT com> 	 <20090602205440 DOT GF23519 AT calimero DOT vinschen DOT de> 	 <4A26782C DOT 9040207 AT sidefx DOT com> 	 <20090603142755 DOT GM23519 AT calimero DOT vinschen DOT de> 	 <3f0ad08d0906030803o2686f633v2a2e5d1345a6381e AT mail DOT gmail DOT com> 	 <20090603155130 DOT GB22513 AT calimero DOT vinschen DOT de> 	 <3f0ad08d0906030917h79f2c96ev385b7134b2b93b38 AT mail DOT gmail DOT com> <3f0ad08d0906030922h299be7bdv86266e0be88140ac AT mail DOT gmail DOT com>
In-Reply-To: <3f0ad08d0906030922h299be7bdv86266e0be88140ac@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

IWAMURO Motonori wrote:
> And, I think that UTF-8 is best solution when the setting of LC_CTYPE
> category is C.
> 
> 2009/6/4 IWAMURO Motonori <deenheart AT gmail DOT com>:
>> I think that this problem is caused by missing setting the locale
>> environment variable.
>> Therefore, I think that the problem can be solved by compelling the
>> setting with setup.exe.

That's not a bad idea. I'm thinking of some option in the installer to 
provide legacy compatibility.

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