-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Monday 06 May 2002 18:03, Charles Lindsey wrote:
<snip>
So perhaps we should still be looking at other possibilities for local
part, such as RFC 2047. Yes that needs care to ensure it is done
canonically, but that is just a matter of insisting that the whole
local-part be treated as exactly one encoded-word.
A base64-encoded UTF-8 encoded-word.
Else, you will get ambiguity arising from different implementations encoding
different octets and in different charsets. E.g., some might encode latin1
space as =20, others as _.
So essentially, you'd have to:
- - encode to (shortest possible) UTF-8
- - apply base64 encoding
- - prepend "=?utf-8?b?"
- - append "?="
OTOH, encoding to "shortest possible UTF-8" surely involves some kind of
normalization of the Unicode representation of the local-part. So we're back
where the large tables come into the game...
But at least a heap of current mailers would _display_ the stuff without
modifiications...
Marc
- --
Marc Mutz <mutz(_at_)kde(_dot_)org>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)
iD8DBQE82CcQ3oWD+L2/6DgRAtoTAKC8H1vUj0TA1dpBo443D/RkUwSOeACfXHyL
FrTiry7jWYlXvwt+VQbPYk0=
=uG/d
-----END PGP SIGNATURE-----