X-Recipient: archive-cygwin@delorie.com X-Spam-Check-By: sourceware.org Date: Fri, 12 Mar 2010 17:25:57 +0100 From: Corinna Vinschen To: cygwin@cygwin.com Subject: Re: 1.7.1-1: In cmd.exe shell, how to pass multi-byte characters to bash? Message-ID: <20100312162557.GR6505@calimero.vinschen.de> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <186f30571003120807v7d09f3a5u71245cb96f87c6cb@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <186f30571003120807v7d09f3a5u71245cb96f87c6cb@mail.gmail.com> User-Agent: Mutt/1.5.20 (2009-06-14) 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 Mar 13 00:07, bootleq wrote: > When typing command in Windows XP cmd.exe shell, with multi-byte > characters, for example: > bash -c 'echo ???' > result in: > bash: $'echo \357\274\241': command not found > expected result: > ??? > > This would be problematic when writing Windows scripts to invoke bash commands. Simplest solution: Write bash scripts instead. Other than that, check the latest developer snapshot from http://cygwin.com/snapshots/. It contains a patch which might fix your problem. And either way, make sure the environment locale settings are matching your Win32 environment. See the User's Guide. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple