From: Eli Zaretskii <eliz@gnu.org>
To: Roland Winkler <winkler@gnu.org>
Cc: monnier@iro.umontreal.ca, emacs-devel@gnu.org
Subject: Re: case-insensitive string comparison
Date: Wed, 20 Jul 2022 21:16:12 +0300 [thread overview]
Message-ID: <83czdzlker.fsf@gnu.org> (raw)
In-Reply-To: <8735evlko4.fsf@gnu.org> (message from Roland Winkler on Wed, 20 Jul 2022 13:10:35 -0500)
> From: Roland Winkler <winkler@gnu.org>
> Cc: monnier@iro.umontreal.ca, emacs-devel@gnu.org
> Date: Wed, 20 Jul 2022 13:10:35 -0500
>
> On Wed, Jul 20 2022, Eli Zaretskii wrote:
> >> Even mentioning the difficulties could be useful here.
> >
> > I'm not sure I agree. To describe all the important aspects of this
> > would take too long, and it isn't the job of our manual to document
> > this stuff. Read this if you want to know:
> >
> > https://unicode.org/reports/tr10/
>
> A footnote pointing the interested reader to this report could already
> be useful.
I'll see if we have a good place for that.
> > Not the users should build the case table, BBDB (or whatever Lisp
> > program that needs the comparison) should. It's not that hard,
> > really: if you only need ASCII, use ascii-case-table, otherwise copy
> > the standard case-table and modify it to make sure I downcases to i
> > and similarly with a few other exceptional letters.
>
> I am not sure it would be possible to predict how a default case table
> for BBDB should differ from the standard case table. BBDB might be the
> only package of a user that accumulates strings that go beyond what
> otherwise a user is dealing with regularly. If there is a sensible
> "BBDB default case table" I'd hope that this is the standard case table.
Maybe BBDB can just use the standard case table, I don't know. You
should be the judge of that: if your users don't care with I not being
equal to i case-insensitively, when the language-environment happens
to be Turkish, then you shouldn't worry about that.
> Or if not: can you suggest an emacs package that I can look into as a
> source of inspiration?
I'm not aware of any (which is not to say there isn't any, just that I
don't know).
next prev parent reply other threads:[~2022-07-20 18:16 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
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 [this message]
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=83czdzlker.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=winkler@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.
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).