From: "Mattias Engdegård" <mattiase@acm.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: kehoea@parhasard.net, larsi@gnus.org, 11309@debbugs.gnu.org
Subject: bug#11309: 24.1.50; Case problems with [:upper:] and Cyrillic, Greek
Date: Tue, 8 Dec 2020 17:57:32 +0100 [thread overview]
Message-ID: <65B5A1CC-9D3D-495B-951D-733C9C0B355E@acm.org> (raw)
In-Reply-To: <83ft4g70ci.fsf@gnu.org>
8 dec. 2020 kl. 17.02 skrev Eli Zaretskii <eliz@gnu.org>:
> AFAIR characters that don't have an upper-case
> form map to themselves when downcased. E.g.
>
> (upcase ?1) => ?1
This is not about the Lisp (upcase x) function but the C upcase(x) function, which uses the upcase table directly.
They affect the uppercasep and lowercasep functions which are used in the regexp engine. Thus we get uppercasep(ß)=lowercasep(ß)=false which is wrong.
The logic of 'lowercasep' may need to be changed because its use of upcase and downcase which return their argument if the respective table has no entry for it. Let's see what can be done.
next prev parent reply other threads:[~2020-12-08 16:57 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-22 10:11 bug#11309: 24.1.50; Case problems with [:upper:] and Cyrillic, Greek Aidan Kehoe
2020-12-07 17:24 ` Lars Ingebrigtsen
2020-12-07 22:14 ` Mattias Engdegård
2020-12-08 14:48 ` Mattias Engdegård
2020-12-08 16:02 ` Eli Zaretskii
2020-12-08 16:57 ` Mattias Engdegård [this message]
2020-12-08 17:05 ` Eli Zaretskii
2020-12-09 14:37 ` Mattias Engdegård
2020-12-09 15:46 ` Eli Zaretskii
2020-12-10 9:36 ` Mattias Engdegård
2020-12-10 14:17 ` Eli Zaretskii
2020-12-10 15:48 ` Mattias Engdegård
2020-12-10 15:53 ` Lars Ingebrigtsen
2020-12-11 9:18 ` Mattias Engdegård
2020-12-11 15:26 ` Lars Ingebrigtsen
2020-12-08 16:10 ` Andreas Schwab
2020-12-08 16:19 ` Mattias Engdegård
2020-12-08 17:01 ` Basil L. Contovounesios
2020-12-08 17:04 ` Mattias Engdegård
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=65B5A1CC-9D3D-495B-951D-733C9C0B355E@acm.org \
--to=mattiase@acm.org \
--cc=11309@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=kehoea@parhasard.net \
--cc=larsi@gnus.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 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.