From: Paul Eggert <eggert@cs.ucla.edu>
To: Bruno Haible <bruno@clisp.org>
Cc: bug-gnulib@gnu.org
Subject: Re: LC_COLLATE in the C locale
Date: Wed, 18 Dec 2019 08:27:02 -0800 [thread overview]
Message-ID: <05cbd4fe-5480-5075-3413-b3ae613992a4@cs.ucla.edu> (raw)
In-Reply-To: <8726723.BRRUbPPWXg@omega>
On 12/18/19 2:29 AM, Bruno Haible wrote:
> Hi Paul,
>
>> I do have a qualm in that coreutils (and I assume others) interpret !hard_locale
>> (LC_COLLATE) as meaning that the locale is unibyte and uses native byte
>> comparison.
> Isn't this warranted by section "LC_COLLATE Category in the POSIX Locale" in
> <https://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap07.html> ?
I don't see where that section requires unibyte.
>> As I recall on some platforms (macOS maybe?), the C locale uses
>> UTF-8 so this interpretation isn't correct.
> UTF-8 has the nice property that byte-per-byte comparison and codepoint-per-
> codepoint comparison are equivalent.
True, so the code that assumes strcmp == strcoll should work. But I think some
code specifically assumes unibyte. Presumably that code should also check
MB_CUR_MAX, which should be enough in practice (even though it doesn't suffice
in theory).
next prev parent reply other threads:[~2019-12-18 16:27 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-17 13:45 hard-locale: make multithread-safe Bruno Haible
2019-12-17 14:08 ` Tim Rühsen
[not found] ` <20191226221225.GA800@HATZ>
2019-12-27 10:51 ` string types Bruno Haible
2019-12-28 13:14 ` ag
2019-12-28 18:28 ` Paul Eggert
2019-12-28 20:44 ` ag
2019-12-28 22:40 ` Paul Eggert
2019-12-29 9:19 ` Bruno Haible
2019-12-29 17:13 ` ag
2019-12-29 20:02 ` ag
2019-12-29 21:24 ` Tim Rühsen
2019-12-31 9:53 ` Bruno Haible
2020-01-06 10:34 ` Tim Rühsen
2020-01-06 12:46 ` Bruno Haible
2020-01-06 16:08 ` Tim Rühsen
2020-01-06 16:49 ` Tim Rühsen
2019-12-18 1:45 ` hard-locale: make multithread-safe Paul Eggert
2019-12-18 8:51 ` Bruno Haible
2019-12-21 6:33 ` Bruno Haible
2019-12-18 10:29 ` LC_COLLATE in the C locale Bruno Haible
2019-12-18 16:27 ` Paul Eggert [this message]
2019-12-18 10:46 ` hard-locale: make multithread-safe Bruno Haible
2019-12-24 23:36 ` Bruno Haible
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=05cbd4fe-5480-5075-3413-b3ae613992a4@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=bruno@clisp.org \
--cc=bug-gnulib@gnu.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).