charset problem

[Adrian 'Dagurashibanipal' von Bidder]

--=-O8C6NegOgiq8lsGL6BBq
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

On Thu, 2002-05-30 at 23:42, Marc Mutz wrote:

> The answer is simple: Don't use --comment with anything but US-ASCII=20
> characters. Comment: is an _ASCII_ armor header. This name alone should=20
> tell you why what you try is a bad idea.

Just curious: is there anything said (rfc, developer opinion, ...) about
the =3D?charset?x?encoded string?=3D encoding in armor headers?

cheers
-- vbi


--=20
secure email with gpg            avbidder@fortytwo.ch: key id 0x92082481
                                 avbidder@acter.ch:    key id 0x5E4B731F


--=-O8C6NegOgiq8lsGL6BBq
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)

iD8DBQA89zezwj49sl5Lcx8RAvYUAKCNXgrMfyRIItVFSOIuC1PKww+fOACfQX7S
wDFoRgb5SEIRFcwhIVXR+I8=
=HUba
-----END PGP SIGNATURE-----

--=-O8C6NegOgiq8lsGL6BBq--