From: Paul Eggert <eggert@cs.ucla.edu>
To: Florian Weimer <fweimer@redhat.com>, Bruno Haible <bruno@clisp.org>
Cc: libc-alpha@sourceware.org, bug-gnulib@gnu.org,
Adhemerval Zanella <adhemerval.zanella@linaro.org>
Subject: Re: [PATCH 1/2] posix: User scratch_buffer on fnmatch
Date: Sat, 6 Mar 2021 09:18:21 -0800 [thread overview]
Message-ID: <0f088c6a-3255-33b8-e177-b9ac91b86c84@cs.ucla.edu> (raw)
In-Reply-To: <87bldrsurg.fsf@oldenburg2.str.redhat.com>
On 1/14/21 2:00 AM, Florian Weimer wrote:
> We saw commercial demand for Shift-JIS much later than that.
Yes, I see Red Hat has a product enhancement for that, for coreutils,
dated 2019.[1]
Shift-JIS is still very much alive and kicking in Japan in its own
circles. Even DBCS EBCDIC is still used among old mainframe
applications.[2] I very much doubt whether we need to worry about DBCS
EBCDIC in GNU software, though.
Shift-JIS is a closer call as it's used a lot more than DBCS EBCDIC.
However, my worry is that good support for non-ASCII-safe encodings like
Shift-JIS is hard to do, and that any such support we'd add to
Gnulib/coreutils/etc. would not only increase maintenance costs and
reduce runtime performance, but also would be buggy in many oddball
corner cases (and this would have security implications).
[1] https://access.redhat.com/errata/RHEA-2019:0008
[2]
https://www.ibm.com/support/knowledgecenter/en/SS4PJT_6.0.0/cd_zos/cdzos_admin/ZOS_Overview_of_DBCS.html
next prev parent reply other threads:[~2021-03-06 17:18 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-04 20:25 [PATCH 1/2] posix: User scratch_buffer on fnmatch Adhemerval Zanella
2021-01-04 20:25 ` [PATCH 2/2] posix: Remove alloca usage for internal fnmatch implementation Adhemerval Zanella
2021-03-08 12:59 ` Florian Weimer
2021-10-20 15:12 ` Adhemerval Zanella
2021-10-21 9:54 ` Florian Weimer
2021-01-04 20:35 ` [PATCH 1/2] posix: User scratch_buffer on fnmatch Florian Weimer
2021-01-05 13:07 ` Adhemerval Zanella
2021-01-13 19:25 ` Paul Eggert
2021-01-13 19:39 ` Florian Weimer
2021-01-13 23:36 ` Bruno Haible
2021-01-14 10:00 ` Florian Weimer
2021-03-06 17:18 ` Paul Eggert [this message]
2021-03-06 20:17 ` dealing with non-ASCII-safe encodings Bruno Haible
2021-01-14 11:44 ` [PATCH 1/2] posix: User scratch_buffer on fnmatch Adhemerval Zanella
2021-01-15 6:56 ` Paul Eggert
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.gnu.org/mailman/listinfo/bug-gnulib
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0f088c6a-3255-33b8-e177-b9ac91b86c84@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=adhemerval.zanella@linaro.org \
--cc=bruno@clisp.org \
--cc=bug-gnulib@gnu.org \
--cc=fweimer@redhat.com \
--cc=libc-alpha@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).