From: Jacob Welsh <jacob+musl@welshcomputing.com>
To: musl@lists.openwall.com
Subject: Re: [musl] Locale support considered harmful noise
Date: Wed, 19 Feb 2020 21:28:10 +0000 (UTC) [thread overview]
Message-ID: <alpine.DEB.2.00.2002191946030.23857@ny4.eemta.org> (raw)
In-Reply-To: <543bcfcc-41f8-6960-8b6a-8e7fd5f01a01@adelielinux.org>
On Tue, 18 Feb 2020, A. Wilcox wrote:
> Why do you not believe that musl could provide any of these features
> using clear and concise code?
I fully expect it could. The point at issue however is whether it should
be done at all.
> I have been personally impacted by the lack of LC_COLLATE support.
I have been personally "impacted" by its presence in glibc, but perhaps
I'm not the sort of "real world" user whose needs you would like to
represent.
> This will allow non-English speakers the ability to understand the
> errors that are happening on the computers they own.
You may be overestimating a bit there the abilities of most English
speakers to "communicate with their computers" or specifically to decode
error messages; anyway, what your approach actually does is to fragment
the knowledge base and herd people *away* from where they might find the
best information.
Now, this dispute is at least as old as the Protestant Reformation so I do
not expect or require it to be settled here.
> In fact, musl is *not* conformant to the POSIX standard *because* it
> does not implement the requisite locale support.
We're prepared to fork POSIX or any other document that proves necessary.
Not like it's hard.
On the other hand, I suppose someone will get right to work translating
POSIX and all the musl code and commentary to every presently spoken
language, because after all they look mighty Anglocentric to me and no one
coder's needs matter more than another's.
Sarcasm aside, I'm satisfied that our differences have been made clear and
am happy to let it rest.
Yours truly,
J. Welsh
http://fixpoint.welshcomputing.com/
next prev parent reply other threads:[~2020-02-19 21:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-18 19:38 Jacob Welsh
2020-02-18 21:42 ` A. Wilcox
2020-02-18 22:23 ` Hadrien Lacour
2020-02-18 23:29 ` [musl] race condition in sem_wait Sebastian Gottschall
2020-02-19 0:46 ` Sebastian Gottschall
2020-02-19 3:39 ` Rich Felker
2020-02-19 8:26 ` Sebastian Gottschall
2020-02-19 14:13 ` Rich Felker
2020-02-19 4:07 ` Bobby Bingham
2020-02-19 21:28 ` Jacob Welsh [this message]
2020-02-19 22:06 ` [musl] Locale support considered harmful noise Rich Felker
2020-02-19 3:36 ` Rich Felker
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=alpine.DEB.2.00.2002191946030.23857@ny4.eemta.org \
--to=jacob+musl@welshcomputing.com \
--cc=musl@lists.openwall.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
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 NNTP newsgroup(s).