X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-0.2 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_LOW,RCVD_NUMERIC_HELO,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: sourceware.org To: cygwin AT cygwin DOT com From: Lenik Subject: Re: Cygwin programs doesn't support non-ASCII filenames Date: Tue, 12 May 2009 15:49:14 +0800 Lines: 27 Message-ID: References: <20090509100231 DOT GR21324 AT calimero DOT vinschen DOT de> <20090509154400 DOT GS21324 AT calimero DOT vinschen DOT de> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1b3pre) Gecko/20090223 Thunderbird/3.0b2 In-Reply-To: <20090509154400.GS21324@calimero.vinschen.de> X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com On 2009-5-9 23:44, Corinna Vinschen wrote: > On May 9 23:12, Lenik wrote: >> The same result, it shows that `cat' from binutils can support locale >> well, while `d' isn't. > > Ok, but that's not Cygwin's problem, just the d tool would need an > update at one point, perhaps. OTOH, what you're doing is a bit > borderline. When you start this stuff from cmd, you will have to enter > the filename in the notation valid for the locale in which the > application works. For d, which only works in the C locale, you would > have to give the pathname using the SO/UTF-8 sequences. Right now I > have no idea if there's a workaround for that, but keep in mind that > we're at the beginning of real native language support. Unfortunately > it's all a bit more complicated than on non-Windows systems, given the > UTF-16-ness of the underlying system. > I'd like to know if there is any build plan to upgrade tools like d, zip, unzip, jar, etc. to support locale settings, rather than C only. So I can tell customers when our cygwin-based scripts will work for Chinese path names. Or is there documented ways to build with locale support from source code? Currently the two tools `jar' and `unzip' which don't support locale settings prevent my scripts being widely deployed. Thank you Corinna, Lenik -- 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/