X-Recipient: archive-cygwin AT delorie DOT com DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 33D7C385734E DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com; s=default; t=1690622674; bh=RHuxJRuaAkaBwnTwatebjiS37RBDpqmkHvpc942SrUU=; h=Date:To:Subject:References:In-Reply-To:List-Id:List-Unsubscribe: List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To:Cc: From; b=QoR4X0B7DCUfo8k47Uny60aR0M57nTlDCbxLPGbQ8VvDebh4A+5IEaCPIulmKKpNv fcyyHNrshJAEhnn8R03wqHYJMni86c9MS8FFjz9LSG6WTLkZQCnqbaZd36CJ0uBqw6 Jd8TFsVohjWcYF/UAlnC74qiDutT32hP/RWNEkLw= X-Original-To: cygwin AT cygwin DOT com Delivered-To: cygwin AT cygwin DOT com DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org CBDB43858C41 Date: Sat, 29 Jul 2023 11:23:52 +0200 To: Bruno Haible Subject: Re: GB18030 locale Message-ID: Mail-Followup-To: Bruno Haible , cygwin AT cygwin DOT com References: <3884636 DOT 3uDm00564X AT nimes> <24556977 DOT snJFCo28Jb AT nimes> <4641755 DOT FJ9Bj1ZfmD AT nimes> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <4641755.FJ9Bj1ZfmD@nimes> X-BeenThere: cygwin AT cygwin DOT com X-Mailman-Version: 2.1.29 Precedence: list List-Id: General Cygwin discussions and problem reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Corinna Vinschen via Cygwin Reply-To: cygwin AT cygwin DOT com Cc: Corinna Vinschen , cygwin AT cygwin DOT com Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: cygwin-bounces+archive-cygwin=delorie DOT com AT cygwin DOT com Sender: "Cygwin" On Jul 28 21:54, Bruno Haible via Cygwin wrote: > Corinna Vinschen wrote: > > test-fnmatch-5.sh is SKIPped because we don't support zh_CN.GB18030. > > Hmm? When I read winsup/cygwin/release/3.5.0 and the commit > 5da71b6059956a8f20a6be02e82867aa28aa3880, it seems the zh_CN.GB18030 > locale (which on native Windows is called "Chinese_China.54936") > should be supported. You're right, I always had the idea to add GB18030 support and forgot that I supposedly did that in 5da71b605995 ("Cygwin: add support for GB18030 codeset"), sorry. However, on debugging this, I see it's totally broken. Trying to fix this in the existing functions is futile. We need dedicated support functions for GB18030, kind of like the FreeBSD functions, just with extra support for surrogate pairs, as with our UTF8 stuff. Corinna -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation: https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple