-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hello Kyle,
On Friday, March 9, 2007 at 8:08:43 -0700, Kyle Wheeler wrote:
> On Friday, March 9 at 03:32 PM, quoth Alain Bench:
>> [tamo.pgp_charsethack.1] also permits to send traditional inline PGP
>> mails in any charset of $send_charset (instead of forced
>> $send_charset="us-ascii:utf-8").
> Are there any mail clients that will decode that correctly?
Sure, and I believe Pine to be a target example. Last time I checked
(long ago), Pine was able to correctly display a Latin-1 PGP mail, but
only if the terminal had the same charset. An allegedly more standard
UTF-8 inline PGP mail would be garbled on such terminal. As would be any
other charset.
The whole thing is dead complex. But I'd say that the UTF-8 forcing,
done to comply to standards, does in fact reduce interoperability in
some circumstances. UTF-8 wants to be world universal, but fails with
old and most non-charset-aware mailers. While arbitrary charsets work in
practice, say between two Polish guys using Latin-2. But fail between a
French and a Russian, or when terminal's charset differ. You gain on one
side, lose on another: No perfect move.
Of course when people use Mutt on both sides, everything works much
better! Mutt is able to verify and display correctly inline PGP mails in
any charset, on any terminal. Provided the sender doesn't use stock
Mutt 1.4.x (because its evil application/pgp content-type doesn't cary
charset).
That's a text/plain inline signed CP-850 e acute: é
Bye! Alain.
- --
You know what I would like to do? COMPLY. I would LOVE to COMPLY. But, you know
what, Pat? I don't know where the h_ll that frickin 2-dash stupid stinkin line
is coming from, okay? Comply...
Greg K. in « Scarface III -- The Return Of The Evil Sigdashes »
-----BEGIN PGP SIGNATURE-----
iD8DBQFF8Zg+TqBX6MHEYBURAq2KAKC122bFsMVpNmmGAFjijLBNR+9vmQCgkMsT
1AEL1cAcSZVJfSqPOh1GaeA=
=6xXD
-----END PGP SIGNATURE-----
