pgp/mime vs in-line pgp

[Atom 'Smasher']

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

> The big problem with inline is non-ascii text: when the senders charset
> differs from the receivers, the receivers MUA is likely to convert the
> message before displaying/storing - breaking the signature (not an
> issue when the receiver's MUA directly supports GPG/PGP.)
>
> I'm not sure, but I can imagine that there may be problems with line
> wrapping, too, on conversions to/ftom quoted-printable.
==========================

please disregard my previous response to this... i was "thinking out loud"
and accidently hit send.

anyway, what if gpg supported quoted-printable input? how much of the
problem would that solve?


	...atom

 _________________________________________
 PGP key - http://atom.smasher.org/pgp.txt
 3EBE 2810 30AE 601D 54B2 4A90 9C28 0BBF 3D7D 41E3
 -------------------------------------------------

	"Generally, news reporting and punditry are
	 respectful of the rich and disdainful of the poor."
		-- Syndicated columnist Norman Solomon
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (FreeBSD)
Comment: What is this gibberish?  -  http://atom.smasher.org/links/#digital_signatures

iEYEARECAAYFAkB8TC8ACgkQnCgLvz19QeN3RACePlsdoEk4VCxZQ4oSoJpclMGf
jogAoJD9h/CVFbqycPV6DJyF8mDZQ5T1
=3EO6
-----END PGP SIGNATURE-----