Gnus development mailing list
 help / color / mirror / Atom feed
From: Richard Stallman <rms@gnu.org>
Cc: yamaoka@jpl.org, emacs-devel@gnu.org, ding@gnus.org, handa@m17n.org
Subject: Re: re-search bug?
Date: Sat, 05 Feb 2005 12:39:15 -0500	[thread overview]
Message-ID: <E1CxTtr-0001e3-IE@fencepost.gnu.org> (raw)
In-Reply-To: <87mzukl91u.fsf-monnier+emacs@gnu.org> (message from Stefan Monnier on Fri, 04 Feb 2005 09:03:59 -0500)

    That's what I would expect.  I think even the definition of "case fold
    search" is not as obvious as it seems.  Does it mean (equal (upcase X)
    (upcase Y)) or (equal (downcase X) (downcase Y)) or something yet different?

Neither of those.  It is supposed to find matches whenever the
characters are connected by any sequence of case conversions.  This
uses the canon table and the equiv table.  In search_buffer and its
subroutines, TRT refers to the canon table, and INVERSE_TRT refers to
the equiv table.  So the table passed to regex searching is the canon
table.

Definitions of these two tables:

CANONICALIZE maps each character to a canonical equivalent;
 any two characters that are related by case-conversion have the same
 canonical equivalent character...
EQUIVALENCES is a map that cyclicly permutes each equivalence class
 (of characters with the same canonical equivalent)...

A good first step would be to look at the canon and equiv table
contents, in the case that fails, and see if they correspond correctly
to the upcase and downcase tables.

      reply	other threads:[~2005-02-05 17:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-03  1:12 Katsumi Yamaoka
2005-02-03  2:23 ` Kenichi Handa
2005-02-03  3:13   ` Katsumi Yamaoka
2005-02-03 19:14   ` Richard Stallman
2005-02-04  1:14     ` Kenichi Handa
2005-02-04 14:03       ` Stefan Monnier
2005-02-05 17:39         ` Richard Stallman [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=E1CxTtr-0001e3-IE@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=ding@gnus.org \
    --cc=emacs-devel@gnu.org \
    --cc=handa@m17n.org \
    --cc=yamaoka@jpl.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.
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 NNTP newsgroup(s).