From: Eli Zaretskii <eliz@gnu.org>
To: tomas@tuxteam.de
Cc: emacs-devel@gnu.org, mattiase@acm.org
Subject: Re: case-insensitive string comparison
Date: Wed, 20 Jul 2022 14:35:21 +0300 [thread overview]
Message-ID: <834jzcm2yu.fsf@gnu.org> (raw)
In-Reply-To: <YteHEnoZ76JcEtNZ@tuxteam.de> (tomas@tuxteam.de)
> Date: Wed, 20 Jul 2022 06:39:46 +0200
> Cc: Mattias Engdegård <mattiase@acm.org>
> From: <tomas@tuxteam.de>
>
> One case (heh) which gets too little attention in that
> (good) ref is "i" "ı" vs. "İ" vs. "I". You've to decide
> on a language environment to get a chance of doing it
> right (in Latin languages there are only 1 and 4, and
> they map to each other, in Turkic languages 1 and 3
> correspond, as 2 and 4 do).
>
> The ref to the Unicode FAQ [1] from your ref shows that
> even the Unicode folks have given up on that. To me, it
> looks like an especially sleazy way to admit "well, folks,
> we've messed up on this one".
>
> Human languages are a messy mix, in which politics figures
> prominently. Unicode reflects that.
This could be hard on the Unicode Consortium, but relatively easy in
Emacs: just bind the case table of the current buffer to something
reasonable around code which performs case-insensitive comparison.
next prev parent reply other threads:[~2022-07-20 11:35 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-19 17:27 case-insensitive string comparison Sam Steingold
2022-07-19 18:06 ` Mattias Engdegård
2022-07-19 18:56 ` Sam Steingold
2022-07-20 4:39 ` tomas
2022-07-20 11:35 ` Eli Zaretskii [this message]
2022-07-20 13:30 ` tomas
2022-07-19 18:16 ` Stefan Kangas
2022-07-19 19:39 ` Roland Winkler
2022-07-19 22:47 ` Sam Steingold
2022-07-20 2:21 ` Roland Winkler
2022-07-20 3:01 ` Stefan Monnier
2022-07-20 16:22 ` Sam Steingold
2022-07-25 14:23 ` Sam Steingold
2022-07-25 15:58 ` Eli Zaretskii
2022-07-25 19:39 ` Sam Steingold
2022-07-26 13:05 ` Eli Zaretskii
2022-07-26 14:16 ` Sam Steingold
2022-07-26 15:53 ` Eli Zaretskii
2022-07-26 16:00 ` Sam Steingold
2022-07-26 16:16 ` Lars Ingebrigtsen
2022-07-26 14:43 ` Robert Pluim
2022-07-25 19:37 ` Bruno Haible
2022-07-26 3:24 ` Richard Stallman
2022-07-26 8:00 ` Helmut Eller
2022-07-26 12:21 ` Eli Zaretskii
2022-07-27 2:58 ` Richard Stallman
2022-07-31 8:24 ` Eli Zaretskii
2022-07-26 14:28 ` Sam Steingold
2022-07-26 15:42 ` Sam Steingold
2022-07-26 16:10 ` Eli Zaretskii
2022-07-26 18:56 ` Bruno Haible
2022-07-26 19:30 ` Eli Zaretskii
2022-07-20 16:24 ` Roland Winkler
2022-07-20 17:06 ` Sam Steingold
2022-07-20 17:16 ` Eli Zaretskii
2022-07-20 17:12 ` Eli Zaretskii
2022-07-20 17:37 ` Roland Winkler
2022-07-20 17:50 ` Eli Zaretskii
2022-07-20 18:10 ` Roland Winkler
2022-07-20 18:16 ` Eli Zaretskii
2022-07-20 18:18 ` [External] : " Drew Adams
2022-07-21 6:56 ` Eli Zaretskii
2022-07-21 14:19 ` Roland Winkler
2022-07-21 15:53 ` Eli Zaretskii
2022-07-21 16:35 ` Roland Winkler
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=834jzcm2yu.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=mattiase@acm.org \
--cc=tomas@tuxteam.de \
/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).