X-Recipient: archive-cygwin@delorie.com X-SWARE-Spam-Status: No, hits=-0.8 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: <20090603142755.GM23519@calimero.vinschen.de> References: <3f0ad08d0905290813m39999f81q918e94e3c960eb3f@mail.gmail.com> <3f0ad08d0905290852xe41338alfda89c622f92f677@mail.gmail.com> <4A200BC0.9010704@sidefx.com> <4A204149.2050009@sidefx.com> <4A2051E5.6060600@sidefx.com> <20090602205440.GF23519@calimero.vinschen.de> <4A26782C.9040207@sidefx.com> <20090603142755.GM23519@calimero.vinschen.de> Date: Wed, 3 Jun 2009 21:52:59 +0400 Message-ID: Subject: Re: 1.7.0-48: [BUG] Passing characters above 128 from bash command line From: Alexey Borzenkov To: cygwin@cygwin.com Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com On Wed, Jun 3, 2009 at 6:27 PM, Corinna Vinschen wrote: > What's left as questionable is the LANG=3DC default case. =C2=A0Due to the > 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? =C2=A0Anybody having a strong opinion > here? I am strongly against it. Because, as I showed earlier, this case: for filename in `ls`; do windowsprogram.exe $filename end Should work. Since filenames use cygwin's encoding (UTF-8 for C locale, or the value of LANG), arguments conversion should use it too. It would be confusing otherwise. -- 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/