Jutta Degener wrote:
I've implemented :binary, too, and it didn't seem like a big
overhead compared to, say, a charset conversion via iconv that
the other options ask you to do to arrive at UTF-8. Do you
remember what specifically got in your way?
Nothing earth shattering, but the [decoded] body part needs to be
expanded into space-separated hex (a 3x increase in size) in order to do
the match. This *might* be avoidable by doing the "hex dump" on the fly
for :contains and possibly :matches, but is necessary for :regex unless
using a home-grown regex function/library.
I thought about "decoding" the ascii-hex pattern and then comparing
against the content, but that prohibits patterns such as "3c 4?" Or are
patterns such as this prohibited (special pattern-matches chars can't be
used as a placeholder for a nibble)?
--
Kenneth Murchison Oceana Matrix Ltd.
Software Engineer 21 Princeton Place
716-662-8973 x26 Orchard Park, NY 14127
--PGP Public Key-- http://www.oceana.com/~ken/ksm.pgp