Just confirmation, I finally performed this test, and my experience
mirrors Jon's. I use Mail.app on MacOS X which I suppose is uncommonly,
multilinguistically savvy, it displayed all the characters correctly.
GnuPG and the associated plugin handled the signature fine.
On Tuesday, April 16, 2002, at 12:16 AM, Thomas Roessler wrote:
-----BEGIN PGP SIGNED MESSAGE-----
On 2002-04-15 17:38:13 -0700, Jon Callas wrote:
The reason I dropped it is because some implementers claim that
base OpenPGP with armoring is deprecated. This is *not* the case.
With all due respect, OpenPGP with armoring gets you into all kinds
of hell as soon as you want to sign more than just us-ascii text,
and as soon as you want to verify the signature on a system
different from the one the signature was created on. This is, in
particular, the case when users have to feed PGP with a recoded
version of the message. Such recoding may be necessary in order to
properly display the message to you.
Here's a test - this message is encoded in utf-8, it's clearsigned,
and here is a number of special characters: € ä ö ü æ ç
Using widespread Windows software, can you find a messaging program
which (1) verifies the signature AND (2) correctly displays the
special characters (Euro symbol, a-umlaut, o-umlaut, u-umlaut, ae
ligature, c-cedilla)? Please tell us.
If you can come up with wording that says MIME is great, but so is
armoring, send it and I'll look at it.
How about this?
Note: A specification for using MIME to encapsulate OpenPGP
signed or encrypted messages, and for signing and encrypting
complex MIME objects with OpenPGP, can be found in RFC 3156.
I'll send a separate message with somewhat more on the character
set issues later today.
Thomas Roessler <roessler(_at_)does-not-exist(_dot_)org>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
-----END PGP SIGNATURE-----