On Sat, Jun 01, 2002 at 10:45:58AM -0700, Craig R Hughes wrote: | dman wrote: | | d> Also keep a way to test the raw text itself, since some junk is easily | d> identified by the raw format and not so obvious after it has been | d> prepared for display. | | Well, we can have the charset translation stuff happen between | rawbody and body -- so rawbody will have the original untrsanslated | stuff, and body tests will have the processed stuff. Would that | work, or do we need to have an extra test stage, beyond the | "charset_ok" stuff?
I guess that will work. I'm just trying to think ahead, and some of
the tests (like malformed content, <iframe, or other encoded stuff)
might be easier to find before things are decoded. Maybe have some
stages between "completely raw", "converted to UTF-8", "Q-P/base64
decoded". The real test as to whether or not this is useful is to see
how easy it is to make rules at each stage.
-D
--
"...In the UNIX world, people tend to interpret `non-technical user' as
meaning someone who's only ever written one device driver."
--Daniel Pead
GnuPG key : http://dman.ddts.net/~dman/public_key.gpg
msg05970/pgp00000.pgp
Description: PGP signature
