From: Nathan Trapuzzano <nbtrap@nbtrap.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 17130@debbugs.gnu.org
Subject: bug#17130: 24.4.50; Deficient Unicode case folding
Date: Sat, 29 Mar 2014 16:01:10 -0400 [thread overview]
Message-ID: <878ursydod.fsf@nbtrap.com> (raw)
In-Reply-To: <87txair0g7.fsf@ivytech.edu>
Eli Zaretskii <eliz@gnu.org> writes:
>> I know. But if Emacs doesn't do Unicode folding, what is there other
>> than lower/upper variants?
>
> You can make it have whatever you like, because you can set up
> buffer-specific tables.
Makes me wonder if whoever implemented the CANONICALIZE slot had Unicode
folding in mind.
>> Finding the non-canonical variants is not something that happens (at
>> least in principle) during case-insensitive matching.
>
> The case database is not only for searching.
>
>> There is no reverse mapping when it comes to folding. There can't be,
>> since multiple characters can fold into the same character.
>
> You can use the case of the string being replaced as guidelines.
> E.g., if the replaced string was capitalized, you can capitalize the
> replacement.
I think you're still conflating case conversion and case folding. As I
said, there is no case called "fold". There's just upper, lower, and
title. And the fact that these three overlap is already a problem for
case-preserving replace. I spent most of my last email trying to
explain this.
next prev parent reply other threads:[~2014-03-29 20:01 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-28 12:07 bug#17130: 24.4.50; Deficient Unicode case folding Nathan Trapuzzano
2014-03-28 15:51 ` Eli Zaretskii
2014-03-28 19:31 ` nbtrap
2014-03-29 6:45 ` Eli Zaretskii
[not found] ` <87ob0pnptc.fsf@nbtrap.com>
2014-03-29 13:15 ` Eli Zaretskii
2014-03-29 14:03 ` Nathan Trapuzzano
2014-03-29 14:45 ` Eli Zaretskii
2014-03-29 15:29 ` Nathan Trapuzzano
2014-03-29 17:37 ` Eli Zaretskii
2014-03-29 18:31 ` Nathan Trapuzzano
2014-03-29 18:36 ` Nathan Trapuzzano
2014-03-29 19:51 ` Eli Zaretskii
2014-03-29 20:15 ` Nathan Trapuzzano
2014-03-30 2:45 ` Eli Zaretskii
2014-03-29 19:50 ` Eli Zaretskii
2014-03-29 20:01 ` Nathan Trapuzzano [this message]
2019-09-29 14:23 ` Lars Ingebrigtsen
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=878ursydod.fsf@nbtrap.com \
--to=nbtrap@nbtrap.com \
--cc=17130@debbugs.gnu.org \
--cc=eliz@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).