From: Eli Zaretskii <eliz@gnu.org>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: 59275@debbugs.gnu.org
Subject: bug#59275: Unexpected return value of `string-collate-lessp' on Mac
Date: Mon, 21 Nov 2022 15:31:38 +0200 [thread overview]
Message-ID: <8335ac4eo5.fsf@gnu.org> (raw)
In-Reply-To: <877czokbpk.fsf@localhost> (message from Ihor Radchenko on Mon, 21 Nov 2022 07:28:55 +0000)
> From: Ihor Radchenko <yantar92@posteo.net>
> Cc: 59275@debbugs.gnu.org
> Date: Mon, 21 Nov 2022 07:28:55 +0000
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> >> Reliable sorting.
> >> In particular, I am looking for a better PREDICATE argument for
> >> `sort-subr' for case-sensitive and case-insensitive sorting of strings.
> >
> > In the strict order of Unicode codepoints? Use compare-strings.
>
> Thanks for the clarification.
> After further considerations, it looks like we should still use
> `string-collate-lessp' on Org side as it yields expected results if libc
> properly implements the collation.
Is the feature that uses it intended to be used only on glibc platforms
(which basically means GNU/Linux)? If not, I'm surprised that you arrived
at this conclusion. It is the 180 deg opposite of what I think you should
have decided.
Once again: locale-specific collation order is inherently unpredictable in
its results, and should only be used when the locale-specific order is a
_must_, like when sorting people's names for a telephone directory.
> Maybe change
>
> If your system does not support a locale environment, this function
> behaves like `string-lessp'.
>
> to
>
> Some operating systems do not implement correct collation (in specific
> locale environments or at all). Then, this functions falls back to
> case-sensitive `string-lessp' and IGNORE-CASE argument is ignored.
Fine with me.
next prev parent reply other threads:[~2022-11-21 13:31 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-15 4:08 bug#59275: Unexpected return value of `string-collate-lessp' on Mac Ihor Radchenko
2022-11-15 9:51 ` Robert Pluim
2022-11-16 3:47 ` Ihor Radchenko
2022-11-15 13:46 ` Eli Zaretskii
2022-11-15 15:05 ` Ihor Radchenko
2022-11-15 15:16 ` Eli Zaretskii
2022-11-16 1:34 ` Ihor Radchenko
2022-11-16 13:00 ` Eli Zaretskii
2022-11-21 7:28 ` Ihor Radchenko
2022-11-21 13:31 ` Eli Zaretskii [this message]
2022-11-22 1:24 ` Ihor Radchenko
2022-11-22 12:56 ` Eli Zaretskii
2022-11-23 10:39 ` Ihor Radchenko
2022-11-23 14:58 ` Eli Zaretskii
2022-11-24 2:22 ` Ihor Radchenko
2022-11-24 7:23 ` Eli Zaretskii
2022-11-26 2:03 ` Ihor Radchenko
2022-11-26 8:06 ` Eli Zaretskii
2022-11-26 8:47 ` Ihor Radchenko
2022-11-26 9:22 ` Eli Zaretskii
2022-11-27 14:00 ` Maxim Nikulin
2022-11-27 14:23 ` Eli Zaretskii
2022-11-27 15:19 ` Maxim Nikulin
2022-11-27 15:42 ` Eli Zaretskii
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://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8335ac4eo5.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=59275@debbugs.gnu.org \
--cc=yantar92@posteo.net \
/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.savannah.gnu.org/cgit/emacs.git
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).