X-Recipient: archive-cygwin@delorie.com X-SWARE-Spam-Status: No, hits=-1.0 required=5.0 tests=AWL,BAYES_00,J_CHICKENPOX_41,SPF_PASS X-Spam-Check-By: sourceware.org Message-ID: <4A268C22.8070305@sidefx.com> Date: Wed, 03 Jun 2009 10:43:46 -0400 From: Edward Lam User-Agent: Thunderbird 2.0.0.21 (Windows/20090302) MIME-Version: 1.0 To: cygwin@cygwin.com Subject: Re: 1.7.0-48: [BUG] Passing characters above 128 from bash command line References: <3f0ad08d0905290813m39999f81q918e94e3c960eb3f@mail.gmail.com> <4A200287.8030403@sidefx.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> In-Reply-To: <20090603142755.GM23519@calimero.vinschen.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Id: 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 Corinna Vinschen wrote: > What's left as questionable is the LANG=C default case. Due 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? Anybody having a strong opinion > here? I'm not clear on what you're proposing here. Are you suggesting that if the conversion from LANG to UTF-16 fails, that we also try a second attempt from the default system code page to UTF-16? -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/