From: Kenichi Handa <handa@m17n.org>
Cc: emacs-pretest-bug@gnu.org, fx@gnu.org, emacs-devel@gnu.org
Subject: Re: case-table functions clobbering extra slots
Date: Wed, 2 Feb 2005 11:57:51 +0900 (JST) [thread overview]
Message-ID: <200502020257.LAA19480@etlken.m17n.org> (raw)
In-Reply-To: <E1CuvLc-0007j3-Ko@fencepost.gnu.org> (message from Richard Stallman on Sat, 29 Jan 2005 11:21:20 -0500)
In article <E1CuvLc-0007j3-Ko@fencepost.gnu.org>, Richard Stallman <rms@gnu.org> writes:
> Downcase of dotted-I is dotted-i (`i'), but, in
> lang. env. other than Turkish, upcase of dotted-i must be
> dotless-I (`I'). So we need
> (set-downcase-syntax dotted-I dotted-i table)
> Ok, if we need them both, please add both.
I've just installed these changes:
o lisp/case-table.el
Add set-upcase-syntax and set-downcase-syntax, modify
th other function to maintain upcase table.
o lisp/international/characters.el, lisp/international/latin-5.el:
Setup cases of GREEK-FINAL-SIGMA, Y-WITH-DIAERESIS,
I-WITH-DOT-ABOVE, DOTLESS-i.
o src/casefiddle.c:
Enable casify_object to change characters of different
byte size. Fix casify_region to work on such a case
correctly.
o src/insdel.c
Fix bugs of replace_range_2.
Now, upcase/downcase commands on the above characters seems
to work correctly.
But, I found case-fold searching and regexp matching doesn't
work as expected. For instance, searching for DOTLESS-i
ignores `i' and `I' but find I-WITH-DOT-ABOVE. On the other
hand, all of the following returns nil:
(staring-match "DOTLESS-i" "i")
(staring-match "DOTLESS-i" "I")
(staring-match "DOTLESS-i" "I-WITH-DOT-ABOVE")
It seems that this behaviour is because compile-pattern is
given a downcase table and search_buffer is given a canon
table and an equiv table, but I still don't understand
the underlying logic of this difference.
---
Ken'ichi HANDA
handa@m17n.org
prev parent reply other threads:[~2005-02-02 2:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <rzq7jmbd6at.fsf@loveshack>
[not found] ` <E1Cr43e-0007Sz-3j@fencepost.gnu.org>
[not found] ` <rzq651rvie5.fsf@loveshack>
[not found] ` <E1Cs577-0008Mb-WC@fencepost.gnu.org>
[not found] ` <rzqu0p5rq35.fsf@loveshack>
[not found] ` <200501260656.PAA16289@etlken.m17n.org>
[not found] ` <200501270316.MAA20608@etlken.m17n.org>
[not found] ` <E1CuHye-0006BN-VV@fencepost.gnu.org>
[not found] ` <200501280007.JAA24856@etlken.m17n.org>
[not found] ` <E1CuWt5-00069J-6x@fencepost.gnu.org>
[not found] ` <200501290053.JAA00216@etlken.m17n.org>
[not found] ` <rzqy8eaobws.fsf@loveshack>
[not found] ` <200501310021.JAA09264@etlken.m17n.org>
[not found] ` <E1Cvy6i-0005gA-OQ@fencepost.gnu.org>
[not found] ` <200502012320.IAA18638@etlken.m17n.org>
2005-02-02 0:33 ` case-table functions clobbering extra slots Miles Bader
2005-02-03 6:40 ` Richard Stallman
[not found] ` <E1CuvLc-0007j3-Ko@fencepost.gnu.org>
2005-02-02 2:57 ` Kenichi Handa [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
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=200502020257.LAA19480@etlken.m17n.org \
--to=handa@m17n.org \
--cc=emacs-devel@gnu.org \
--cc=emacs-pretest-bug@gnu.org \
--cc=fx@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).