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 95FBD386F80B for ; Wed, 13 Jan 2021 19:39:22 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 95FBD386F80B 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-125-ixSQk-h4ONGBksWBAcZkAA-1; Wed, 13 Jan 2021 14:39:18 -0500 X-MC-Unique: ixSQk-h4ONGBksWBAcZkAA-1 Received: from smtp.corp.redhat.com (int-mx01.intmail.prod.int.phx2.redhat.com [10.5.11.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id C6FC91842140; Wed, 13 Jan 2021 19:39:16 +0000 (UTC) Received: from oldenburg2.str.redhat.com (ovpn-114-17.ams2.redhat.com [10.36.114.17]) by smtp.corp.redhat.com (Postfix) with ESMTPS id AC51F5B4C4; Wed, 13 Jan 2021 19:39:15 +0000 (UTC) From: Florian Weimer To: Paul Eggert Cc: Adhemerval Zanella , bug-gnulib@gnu.org, Adhemerval Zanella via Libc-alpha Subject: Re: [PATCH 1/2] posix: User scratch_buffer on fnmatch References: <20210104202528.1228255-1-adhemerval.zanella@linaro.org> <87y2h8h23r.fsf@oldenburg2.str.redhat.com> <115de832-1949-4402-92af-a055653e9ce9@linaro.org> Date: Wed, 13 Jan 2021 20:39:14 +0100 In-Reply-To: (Paul Eggert's message of "Wed, 13 Jan 2021 11:25:19 -0800") Message-ID: <87turkaaot.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.11 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: Wed, 13 Jan 2021 19:39:24 -0000 * Paul Eggert: > 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. (Asking for > a friend. :-) 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. 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