From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [216.205.24.124]) by sourceware.org (Postfix) with ESMTP id 57F013857C61 for ; Thu, 14 Jan 2021 10:00:46 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 57F013857C61 Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-501-VMKjAaDWN1Cph8I5_ZIALA-1; Thu, 14 Jan 2021 05:00:40 -0500 X-MC-Unique: VMKjAaDWN1Cph8I5_ZIALA-1 Received: from smtp.corp.redhat.com (int-mx05.intmail.prod.int.phx2.redhat.com [10.5.11.15]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 1CA3915730; Thu, 14 Jan 2021 10:00:39 +0000 (UTC) Received: from oldenburg2.str.redhat.com (ovpn-114-66.ams2.redhat.com [10.36.114.66]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 8CCAA669EC; Thu, 14 Jan 2021 10:00:37 +0000 (UTC) From: Florian Weimer To: Bruno Haible Cc: bug-gnulib@gnu.org, Paul Eggert , libc-alpha@sourceware.org, Adhemerval Zanella Subject: Re: [PATCH 1/2] posix: User scratch_buffer on fnmatch References: <20210104202528.1228255-1-adhemerval.zanella@linaro.org> <87turkaaot.fsf@oldenburg2.str.redhat.com> <6269852.OAlbKWrXbI@omega> Date: Thu, 14 Jan 2021 11:00:35 +0100 In-Reply-To: <6269852.OAlbKWrXbI@omega> (Bruno Haible's message of "Thu, 14 Jan 2021 00:36:31 +0100") Message-ID: <87bldrsurg.fsf@oldenburg2.str.redhat.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.1 (gnu/linux) MIME-Version: 1.0 X-Scanned-By: MIMEDefang 2.79 on 10.5.11.15 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain X-Spam-Status: No, score=-6.7 required=5.0 tests=BAYES_00, DKIMWL_WL_HIGH, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, RCVD_IN_DNSWL_LOW, RCVD_IN_MSPIKE_H3, RCVD_IN_MSPIKE_WL, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on server2.sourceware.org X-BeenThere: libc-alpha@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Libc-alpha mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Jan 2021 10:00:48 -0000 * Bruno Haible: > Paul Eggert asked: >> > By the way, how important is it to support awful encodings like >> > shift-JIS that contain bytes that look like '\'? If we don't have to >> > support these encodings any more, things get a bit easier. > > Here we are talking about locale encodings, and Shift_JIS (as well as > SHIFT_JISX0213) are not usable as a locale encoding in glibc. See e.g. > [1], [2]. > > That's the reason why no Shift_JIS locale is listed in > glibc/localedata/SUPPORTED. [3] > [1] https://sourceware.org/bugzilla/show_bug.cgi?id=3140 > [2] https://sourceware.org/legacy-ml/libc-alpha/2000-10/msg00311.html > [3] https://sourceware.org/git/?p=glibc.git;a=blob;f=localedata/SUPPORTED We used to have a fully supported product based on the original Shift-JIS. It did not require glibc changes (we package both localedef and the locale sources, so it's easy to build custom locales), but other GNU components had to be patched. > Florian Weimer wrote: >> There is a Shift-JIS variant which is ASCII-transparent (Windows-31J, >> it's also specified by WhatWG/HTML5), so from a glibc point of view, it >> would be just an ordinary charset like any other. >> >> But feedback we have received is that the users who want Shift-JIS >> really want the original thing. >> >> We do not presently support either variant downstream, but one potential >> way forward would be to turn Windows-31J into a fully supported glibc >> charset with a corresponding ja_JP locale (which would imply downstream >> support as well), and just hope that it displaces the original Shift-JIS >> in the future. > > I don't think there's a real need for that. In the years 1995 ... 2005 > there was a lot of resistence against Unicode in Japan, because > Unicode maps several slightly differently looking glyph images to the > same glyph/character (even for Western encodings, for example the > Polish accents look a bit different than the French ones), and - at > the time - Unicode did not have means to disambiguate these, thus > people complained about "characters are rendered incorrectly if you > use Unicode". This has been resolved for more than 10 years already. We saw commercial demand for Shift-JIS much later than that. I think an official Windows-31J-based ja_JP would still be welcomed at this point. A Windows-31J locale could be added to localedata/SUPPORTED. We have not done that yet because someone wanted to look into alignment between Windows, HTML/WhatWG and what we currently have in the source tree, but that hasn't happened yet, unfortunately. Thanks, Florian -- Red Hat GmbH, https://de.redhat.com/ , Registered seat: Grasbrunn, Commercial register: Amtsgericht Muenchen, HRB 153243, Managing Directors: Charles Cachera, Brian Klemm, Laurie Krebs, Michael O'Neill