From: Andreas Schwab <schwab@suse.de>
Cc: Kenichi Handa <handa@etl.go.jp>, eliz@is.elta.co.il, emacs-devel@gnu.org
Subject: Re: regex and case-fold-search problem
Date: Sat, 24 Aug 2002 18:16:25 +0200 [thread overview]
Message-ID: <jed6s8mduu.fsf@sykes.suse.de> (raw)
In-Reply-To: <20020824010307.GA8549@gnu.org> (Miles Bader's message of "Fri, 23 Aug 2002 21:03:07 -0400")
Miles Bader <miles@gnu.org> writes:
|> On Sat, Aug 24, 2002 at 09:51:46AM +0900, Kenichi Handa wrote:
|> > I mean that the concept of character range itself is not good. A character
|> > code is just an identifier of a character. We usually don't think about "a
|> > range of identifiers" (e.g. "symbols in the range between t and nil" is
|> > nonsense).
|>
|> Yeah, but character ranges make perfect sense in many local contexts.
|> E.g., [0-9], or [<0>-<9>] where <0> and <9> are `wide' digits from some
|> character set.
What does [A-Z] mean in EBCDIC? [0-9] is a special case, because ISO C
requires that 0,1,2,3,4,5,6,7,8,9 are consecutive in the execution
character set. But in many locales the collating sequence <A> - <Z>
contains more that just the upper case letters from the English alphabet.
Andreas.
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux AG, Deutschherrnstr. 15-19, D-90429 Nürnberg
Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2002-08-24 16:16 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-23 6:25 regex and case-fold-search problem Kenichi Handa
2002-08-23 15:56 ` Eli Zaretskii
2002-08-24 0:51 ` Kenichi Handa
2002-08-24 1:03 ` Miles Bader
2002-08-24 9:42 ` Eli Zaretskii
2002-08-24 16:16 ` Andreas Schwab [this message]
2002-08-26 1:54 ` Miles Bader
2002-08-26 16:11 ` Stefan Monnier
2002-08-26 21:51 ` Richard Stallman
2002-08-24 9:39 ` Eli Zaretskii
2002-08-26 1:29 ` Kenichi Handa
2002-08-26 2:31 ` Miles Bader
2002-08-25 22:21 ` Kim F. Storm
2002-08-23 17:36 ` Stefan Monnier
2002-08-23 21:52 ` Stefan Monnier
2002-08-24 1:16 ` Kenichi Handa
2002-08-25 18:52 ` Stefan Monnier
2002-08-26 1:56 ` Kenichi Handa
2002-08-24 10:40 ` Kai Großjohann
2002-08-26 21:51 ` Richard Stallman
2002-08-29 8:53 ` Kenichi Handa
2002-08-29 12:33 ` Kim F. Storm
2002-08-29 13:38 ` Kenichi Handa
2002-08-29 15:00 ` Kim F. Storm
2002-08-29 16:00 ` Stefan Monnier
2002-08-30 1:11 ` Kenichi Handa
2002-08-30 19:19 ` Richard Stallman
2002-08-30 19:19 ` Richard Stallman
2002-08-30 20:08 ` Stefan Monnier
2002-09-01 13:15 ` Richard Stallman
2002-09-01 16:26 ` Stefan Monnier
2002-09-02 14:54 ` Richard Stallman
2002-09-02 16:58 ` Stefan Monnier
2002-09-04 14:13 ` Richard Stallman
2002-09-04 16:04 ` Stefan Monnier
2002-09-05 18:02 ` Richard Stallman
2002-09-06 1:00 ` re-search-forward seems to be broken Miles Bader
2002-09-06 20:03 ` Richard Stallman
2002-08-31 6:14 ` regex and case-fold-search problem Eli Zaretskii
2002-09-01 13:14 ` Richard Stallman
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=jed6s8mduu.fsf@sykes.suse.de \
--to=schwab@suse.de \
--cc=eliz@is.elta.co.il \
--cc=emacs-devel@gnu.org \
--cc=handa@etl.go.jp \
/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).