From: Eli Zaretskii <eliz@gnu.org>
To: Stephen Berman <stephen.berman@gmx.net>
Cc: 22038@debbugs.gnu.org
Subject: bug#22038: 25.1.50; Character folding issues with isearch
Date: Sat, 28 Nov 2015 20:51:50 +0200 [thread overview]
Message-ID: <837fl2ot2x.fsf@gnu.org> (raw)
In-Reply-To: <8737vqkmk3.fsf@gmx.net>
> From: Stephen Berman <stephen.berman@gmx.net>
> Cc: 22038@debbugs.gnu.org
> Date: Sat, 28 Nov 2015 19:26:20 +0100
>
> > Easiness is not the most important issue here: there's a more basic
> > problem involved. Both "ß" vs "ss" and "æ" vs "a" (or "ae") are
> > language-specific: they are only valid matches in the context of
> > specific languages. AFAIU, that is why they are not in the Unicode
> > database. And we don't yet have language-specific text processing
> > capabilities and infrastructure (well, string-collate-lessp and
> > string-collate-equalp are a beginning, but only that). So allowing
> > those by default risk running afoul of what users want.
>
> I'm not sure what you mean by "only valid matches in the context of
> specific languages", but it sounds like what Per Starbäck said about "ä"
> being considered a completely separate character from "a" in Swedish,
> unlike in German. Yet if this is a language-specific difference, Emacs
> doesn't respect it by default, since "a" does match "ä" under
> character-folding. (Or does it fail to do so when
> current-language-environment is Swedish? I suspect it doesn't.)
We simply go by the decompositions that the (language-agnostic)
Unicode database specified, and do not augment that by anything that
is only valid or relevant in the context of specific languages.
> But I know nothing about the Unicode specifications; maybe you are
> referring to a more subtle issue, which may be unrelated to my point,
> which is simply that I think it should be just as convenient for a user
> whose keyboard may lack "ß" or "æ" to match these characters by
> searching with "s" or "a" (or "e" or "ae") as it is to match "ff" by
> searching with "f". This is not a language-specific issue AFAICS.
The character folding feature is primarily a feature of search, not a
convenience feature for typing characters, although it might double as
that.
next prev parent reply other threads:[~2015-11-28 18:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-28 16:07 bug#22038: 25.1.50; Character folding issues with isearch Stephen Berman
2015-11-28 16:39 ` Eli Zaretskii
2015-11-28 17:10 ` Stephen Berman
2015-11-28 17:40 ` Eli Zaretskii
2015-11-28 18:26 ` Stephen Berman
2015-11-28 18:51 ` Eli Zaretskii [this message]
2015-11-29 6:04 ` Richard Stallman
2015-11-29 12:33 ` Character folding issues with isearch (was: bug#22038: 25.1.50; ...) Stephen Berman
2015-11-29 0:06 ` bug#22038: 25.1.50; Character folding issues with isearch Artur Malabarba
2015-11-29 9:52 ` Andreas Röhler
2015-11-29 15:52 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=837fl2ot2x.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=22038@debbugs.gnu.org \
--cc=stephen.berman@gmx.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.