From: "Alejandro Colomar (man-pages)" <alx.manpages@gmail.com>
To: наб <nabijaczleweli@nabijaczleweli.xyz>
Cc: linux-man@vger.kernel.org
Subject: Re: [PATCH 1/2] rpmatch.3: remove first-character-only FUD
Date: Wed, 22 Sep 2021 11:12:30 +0200 [thread overview]
Message-ID: <64095d5a-e561-d024-5256-2dccdd3b6de8@gmail.com> (raw)
In-Reply-To: <38855813-ada0-24e1-2482-711d82af3e2a@gmail.com>
Hi наб,
On 9/22/21 1:25 AM, Alejandro Colomar (man-pages) wrote:
> Since the C locale is the most important one, IMHO, and it is as
> problematic as the BUGS section mentions, I think we should keep the
> warning, and maybe add a mention that it depends on the locale. What do
> you think?
I mean, I agree with you that rpmatch(3) is **the correct** way of
checking for a yes/no user response, but the programmer should also be
aware of locale's (and especially the C locale) problems, so that he can
also do some extra work and try to fix the locale he expects to use.
However, I also see it good if we move this bug to where the problem
really is (instead of here, which is where the problem is noticed),
which would be one of the locale pages (nl_langinfo(3) for example, as
you said).
Thanks,
Alex
--
Alejandro Colomar
Linux man-pages comaintainer; https://www.kernel.org/doc/man-pages/
http://www.alejandro-colomar.es/
next prev parent reply other threads:[~2021-09-22 9:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-21 13:46 [PATCH 1/2] rpmatch.3: remove first-character-only FUD наб
2021-09-21 13:46 ` [PATCH 2/2] rpmatch.3: clarify availability to glibc, Fx, and AIX наб
2021-09-21 15:20 ` [PATCH 1/2] rpmatch.3: remove first-character-only FUD Alejandro Colomar (man-pages)
2021-09-21 16:06 ` наб
2021-09-21 23:25 ` Alejandro Colomar (man-pages)
2021-09-22 9:12 ` Alejandro Colomar (man-pages) [this message]
2021-10-02 12:18 ` [PATCH v2 1/2] rpmatch.3: clarify " наб
2021-10-02 17:32 ` Alejandro Colomar (man-pages)
2021-10-02 12:18 ` [PATCH v2 2/2] rpmatch.3: clarify availability to glibc, Fx, and AIX наб
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=64095d5a-e561-d024-5256-2dccdd3b6de8@gmail.com \
--to=alx.manpages@gmail.com \
--cc=linux-man@vger.kernel.org \
--cc=nabijaczleweli@nabijaczleweli.xyz \
/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