X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=0.0 required=5.0 tests=AWL,BAYES_00,J_CHICKENPOX_55,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 22:42:40 +0800 Lines: 46 Message-ID: References: <20090509100231 DOT GR21324 AT calimero DOT vinschen DOT de> <20090509154400 DOT GS21324 AT calimero DOT vinschen DOT de> <20090512083037 DOT GO21324 AT calimero DOT vinschen DOT de> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit 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: <20090512083037.GO21324@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-12 16:30, Corinna Vinschen wrote: > On May 12 15:49, Lenik wrote: >> 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. > > That depends on the package maintainers and it will certainly not be > done within just a couple of days. After all, the Cygwin distro is > a volunteer effort. > > > Corinna > Is there any hint on how to add locale support to existing packages at source code level? I guess that a specific package maintainer maybe work on a central version, so any change to `grep' or `unzip' for example, will be applied on that central version, so various distros like RHEL, Ubuntu, etc. can share the same changement? If so that is, my changement on `grep' may be required to be test/return-test on the various distros, and only if the package maintainer considers the changement won't break the consistency between the various distros, he will then accept the changes and release it to the cygwin? If I changed a specific package in cygwin distro, I shall send to that specific package maintainer, right? And I still think it may be better to add locale support in cygwin layer(maybe it's not enabled by default, though), if you write a program operates with path names, (most programs access files) you won't do anything about locale settings in common sense, and I didn't see there is necessary to setlocale or somewhat before fopen/fstat() operations in that famous APUX book. C:\Profiles\Shecti> set LANG=zh_CN.GBK& cat 你好 123 C:\Profiles\Shecti> set LANG=C& cat 你好 123 C:\Profiles\Shecti> set LANG=& cat 你好 cat: 你好: No such file or directory The default LANG isn't C neither GBK in codepage 936, I guess it is set to GB2312, but I'm not sure. How can I know the default LANG? 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/