Date: Sat, 29 Jul 2023 11:23:52 +0200
To: Bruno Haible <bruno@clisp.org>
Subject: Re: GB18030 locale
Message-ID: <ZMTaqNf4dnbry6BD@calimero.vinschen.de>
Mail-Followup-To: Bruno Haible <bruno@clisp.org>, cygwin@cygwin.com
References: <3884636.3uDm00564X@nimes> <24556977.snJFCo28Jb@nimes>
 <ZMQP/7EphqiQNUVW@calimero.vinschen.de> <4641755.FJ9Bj1ZfmD@nimes>
MIME-Version: 1.0
Content-Disposition: inline
In-Reply-To: <4641755.FJ9Bj1ZfmD@nimes>
Precedence: list
From: Corinna Vinschen via Cygwin <cygwin@cygwin.com>
Reply-To: cygwin@cygwin.com
Cc: Corinna Vinschen <corinna-cygwin@cygwin.com>, cygwin@cygwin.com
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: cygwin-bounces+archive-cygwin=delorie.com@cygwin.com
Sender: "Cygwin" <cygwin-bounces+archive-cygwin=delorie.com@cygwin.com>

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