X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-1.3 required=5.0 	tests=AWL,BAYES_00,J_CHICKENPOX_41,SARE_MSGID_LONG40,SPF_PASS
X-Spam-Check-By: sourceware.org
MIME-Version: 1.0
In-Reply-To: <3f0ad08d0906030917h79f2c96ev385b7134b2b93b38@mail.gmail.com>
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>
Date: Thu, 4 Jun 2009 01:22:51 +0900
Message-ID: <3f0ad08d0906030922h299be7bdv86266e0be88140ac@mail.gmail.com>
Subject: Re: 1.7.0-48: [BUG] Passing characters above 128 from bash command  	line
From: IWAMURO Motonori <deenheart AT gmail DOT com>
To: cygwin AT cygwin DOT com
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT 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

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.
>
> 2009/6/4 Corinna Vinschen <corinna-cygwin AT cygwin DOT com>:
>>
>> http://cygwin.com/acronyms/#PCYMTNQREAIYR
>> http://cygwin.com/acronyms/#TOFU
>>
>> On Jun =A04 00:03, IWAMURO Motonori wrote:
>>> 2009/6/3 Corinna Vinschen
>>> > What's left as questionable is the LANG=3DC default case. =A0Due to t=
he
>>> > 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? =A0Anybody having a strong opini=
on
>>> > here?
>>
>>> How about the addition of the setting of the locale environment
>>> variable (like LANG) to the Cygwin installer?
>>
>> I'm sorry, but I don't understand how that's connected to the behaviour
>> of the Cygwin DLL. =A0Setup.exe is an entirely different beast.
>>
>>
>> Corinna
>>
>> --
>> Corinna Vinschen =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0Please, send mails r=
egarding Cygwin to
>> Cygwin Project Co-Leader =A0 =A0 =A0 =A0 =A0cygwin AT cygwin DOT com
>> Red Hat
>>
>> --
>> Unsubscribe info: =A0 =A0 =A0http://cygwin.com/ml/#unsubscribe-simple
>> Problem reports: =A0 =A0 =A0 http://cygwin.com/problems.html
>> Documentation: =A0 =A0 =A0 =A0 http://cygwin.com/docs.html
>> FAQ: =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 http://cygwin.com/faq/
>>
>>
>
>
>
> --
> IWAMURO Motnori <http://vmi.jp/>
>



--=20
IWAMURO Motnori <http://vmi.jp/>

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