-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Eric S. Raymond writes:
Alan Cox <alan(a)redhat.com>:
> RFC822 is problematic because \n and ":" can occur as part of multibyte
> symbols so dumb tools make dumb errors. It works for email only because
> SMTP uses some brain damaged "so dont do that" rules.
Not a problem. I'll just specify that the input is expected to be UTF-8 and
screw all that multibyte crap. World's going that direction anyway.
er, UTF-8 *is* multibyte ;)
However, using UTF-8 should be OK, alright, since UTF-8 multibyte
sequences must contain bit 7 set in all chars, so "\n" and ":" will
not
show up as bytes. viz:
http://www.cl.cam.ac.uk/~mgk25/unicode.html#utf-8
notes 'no ASCII byte (0x00-0x7F) can appear as part of any other
character.'
- --j.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)
Comment: Exmh CVS
iD8DBQE/rAkdQTcbUG5Y7woRAvwmAKC1ELoZO3WPPcAUY7mxaNHsDpzcLACePd/I
Zx6Ouq6469oRQUzk7XQD1gw=
=5ncM
-----END PGP SIGNATURE-----