On Thu, 07 Oct 1999 01:37:02 -0700 (PDT), Dick Moores
<rdm(_at_)netcom(_dot_)com>
wrote:
On Thu, 7 Oct 1999, Satoru Manita wrote:
Nope. In ISO-2022-JP encoding, Kanji-IN sequence is [ESC]$B, and
Kanji-OUT sequence is [ESC](J. A double-byte potion is sandwiched
between Kanji-IN and Kanji-OUT sequence. Thus finding Kanji in the
message body can be done by finding Kanji-IN pattern "[ESC]$B" as in
Era's posting.
Well, I sure don't _see_ those Kanji-IN and Kanju-OUT sequences.
All the Japanese code _appears_ to begin with "B", not "$B". This
Quite possibly whatever you use to view those messages is "eating" the
Esc-$ sequence instead of displaying it literally. The escape
character is frequently used for various display-formatting purposes
and so it wouldn't seem far-fetched that your terminal is reading
these "control sequences" as formatting control, and discarding them,
or doing something that is invisible to you (like perhaps returning to
"normal mode" even if the terminal was already in "normal mode",
whatever that might mean on your hardware. The real explanation is
probably technically more complicated, but this should at least give
you an idea of what I'm trying to say).
I've just done some testing attempting to use the pattern "[ESC]$B"
in this recipe:
VERBOSE=on
:0 HBc:
* ^TOrdm
* ($B)
1ESC
VERBOSE=off
Using the vi editor I typed "$B" as Ctrl+V$B, and then forwarded to
myself some of those posts with Japanese. Doesn't work, but maybe I
don't know what I'm doing.
Whatever you typed in, what I'm reading (and quoting back) doesn't
even contain the escape character anymore. (Another reason to type
some sort of replacement instead of a literal esc in mail messages.)
You need to backslash $, it means "end of line" if you don't put a
backslash in front.
/* era */
--
Too much to say to fit into this .signature anyway: <http://www.iki.fi/era/>
Fight spam in Europe: <http://www.euro.cauce.org/> * Sign the EU petition