Tim wrote,
| This is `quoted-printable' encoding (colloquially called
| `quoted-unreadable' for good reason) ...
I call it "quoted-unprintable" because anything quoted from me after seeing
it is unprintable.
| ... and is probably not under the users' control.
The pass through a qp filter is probably not, but the user's original inclu-
sion of overlong lines, high-bit characters, or trailing spaces certainly is
under his/her control. The only things qp messes up that I think the sender
had any business writing in the first place -- for text in languages other
than English I'd also make an exception for high-bit characters -- are an
equal sign or a capital F against the left margin. Otherwise, any mangling
by a qp filter is within the user's control to prevent.
Moreover, I've seen mail setups that qp only those messages that seem to need
it: an equal sign or a leading capital F won't trigger it, but a long line, a
high-bit character, or a trailing space will (and when that happens, there go
the capital F's and the equal signs). When the text is in English, that cer-
tainly is under the sender's control.
Is there anyone here who hasn't seen the results when qp text is re-qp'ed?
All the equal signs added by the first qp'ing are changed to =3D, so an
actual equal sign becomes =3D3D, and a leading F becomes =3D46, and a
trailing space becomes =3D20, and an inserted line break becomes =3D (which
had meant an equal sign after the first qp'ing).
