X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-3.3 required=5.0 tests=AWL,BAYES_00,J_CHICKENPOX_84,RCVD_IN_DNSWL_LOW,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: sourceware.org To: cygwin AT cygwin DOT com From: Andy Moreton Subject: Re: [1.7] Support for CJK Character Sets Date: Sat, 04 Apr 2009 14:48:47 +0100 Lines: 25 Message-ID: References: <20090403173212 DOT 51916 DOT qmail AT web4102 DOT mail DOT ogk DOT yahoo DOT co DOT jp> <20090403192048 DOT GC852 AT calimero DOT vinschen DOT de> <20090404100909 DOT GF852 AT calimero DOT vinschen DOT de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Gnus/5.110011 (No Gnus v0.11) Emacs/22.3 (windows-nt) X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: 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 Sat 04 Apr 2009, Corinna Vinschen wrote: > On Apr 3 21:20, Corinna Vinschen wrote: >> On Apr 4 02:32, neomjp wrote: >> > [...] >> > But it failed for JIS/ISO-2022-JP and eucJP. (It was represented as >> > ASCII SO(0x0e)/UTF-8 sequence). >> > >> > What is going wrong here? What makes the file name conversion from >> > UTF-16 to these character sets to fail? Or, what am I doing wrong? >> > [...] >> > LANG=en_US.ISO-2022-JP > > Oh, btw., this is wrong. The string "ISO-2022-JP" isn't supported, > just "JIS" is. But it won't work, even with "JIS", afaics. As an aside, the man page for wcstomb(3) seems to have an incorrect prototype: int wcstombs(const char *S, wchar_t *PWC, size_t N); should be: int wcstombs(char *S, const wchar_t *PWC, size_t N); AndyM -- 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/