From: Eli Zaretskii <eliz@gnu.org>
To: npostavs@users.sourceforge.net
Cc: ynyaaa@gmail.com, 23833@debbugs.gnu.org
Subject: bug#23833: 24.5; assoc-string with CASE-FOLD may fail
Date: Thu, 23 Jun 2016 22:25:53 +0300 [thread overview]
Message-ID: <83eg7n3dxa.fsf@gnu.org> (raw)
In-Reply-To: <83k2hf3mki.fsf@gnu.org> (message from Eli Zaretskii on Thu, 23 Jun 2016 19:19:09 +0300)
> Date: Thu, 23 Jun 2016 19:19:09 +0300
> From: Eli Zaretskii <eliz@gnu.org>
> Cc: ynyaaa@gmail.com, 23833@debbugs.gnu.org
>
> > From: Noam Postavsky <npostavs@users.sourceforge.net>
> > Date: Thu, 23 Jun 2016 11:53:00 -0400
> > Cc: ynyaaa@gmail.com, 23833@debbugs.gnu.org
> >
> > Would it not make more sense if upcase converted dz into DZ?
>
> We want to go by what UnicodeData.txt says:
>
> 01F1;LATIN CAPITAL LETTER DZ;Lu;0;L;<compat> 0044 005A;;;;N;;;;01F3;01F2
> 01F2;LATIN CAPITAL LETTER D WITH SMALL LETTER Z;Lt;0;L;<compat> 0044 007A;;;;N;;;01F1;01F3;01F2
> 01F3;LATIN SMALL LETTER DZ;Ll;0;L;<compat> 0064 007A;;;;N;;;01F1;;01F2
>
> The problem here is that both DZ and Dz name dz as their lower-case
> variant, and Emacs can only have one pair. So we chose the other one
> for the upcase conversion. We could switch them, but one of them will
> necessarily be lost, this way or another.
On second thought, I think you are right, and swapping the pairs will
yield better results, so I've just did that on master for these and a
few other similar characters.
Of course, this doesn't resolve the original issue in any way, since
characters that have title-case will still fail the OP's test.
Thanks.
prev parent reply other threads:[~2016-06-23 19:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-23 12:01 bug#23833: 24.5; assoc-string with CASE-FOLD may fail ynyaaa
2016-06-23 12:26 ` Noam Postavsky
2016-06-23 15:11 ` Eli Zaretskii
2016-06-23 15:53 ` Noam Postavsky
2016-06-23 16:19 ` Eli Zaretskii
2016-06-23 19:25 ` Eli Zaretskii [this message]
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=83eg7n3dxa.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=23833@debbugs.gnu.org \
--cc=npostavs@users.sourceforge.net \
--cc=ynyaaa@gmail.com \
/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.