X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-2.0 required=5.0	tests=BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,RCVD_IN_DNSWL_NONE
X-Spam-Check-By: sourceware.org
From: Bengt Larsson <lists DOT cygwin3 AT bengtl DOT net>
To: cygwin AT cygwin DOT com
Subject: Re: [ANNOUNCEMENT] CALL FOR TESTING: Cygwin 1.7.10
Date: Wed, 07 Dec 2011 18:50:45 +0100
Reply-To: cygwin AT cygwin DOT com
Message-ID: <lq9vd7hue8mef2rkdjpnljn12bm0r6ftum@4ax.com>
References: <announce DOT 20111206093746 DOT GA6222 AT calimero DOT vinschen DOT de> <566vd7hfmi3j980ic4m64d7bv91b5qm6uh AT 4ax DOT com> <20111207173808 DOT GA25743 AT calimero DOT vinschen DOT de>
In-Reply-To: <20111207173808.GA25743@calimero.vinschen.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
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

Corinna Vinschen wrote:
>On Dec  7 18:00, Bengt Larsson wrote:
>> Corinna Vinschen wrote:
>> 
>> >- cygwin_conv_path and cygwin_conv_path_list: In CCP_WIN_A_TO_POSIX and
>> >  CCP_POSIX_TO_WIN_A conversions, use the current Windows ANSI or OEM
>> >  charset, depending on the return value of AreFileApisANSI.  Up to Cygwin
>> >  1.7.9, both conversions used the current Cygwin charset for the conversion.
>> 
>> Is that the right thing to do? I have LANG=C.UTF-8. If I pass a
>> Windows-style filename on the command line, it's passed as UTF-8. How do
>> I then convert that to Unix-style, UTF-8?
>
>First of all, don't do that.  Use POSIX paths.
>
>Second, it's not passed as UTF-8 if the called application is a
>non-Cygwin application.  In fact, Cygwin calls CreateProcessW, so all
>strings are converted to UTF-16 (aka UNICODE) when starting a non-Cygwin
>child process.
>
>Third, as for Cygwin apps, don't use WIN_A, use WIN_W instead, because
>that's encoding agnostic:

OK, thanks.

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