17 May
2018
17 May
'18
7:06 a.m.
On Wed, 16 May 2018, Paul Koning wrote:
There's no rational reason to MIME encode the *body* of an email, unless
of course they're using some badly written horror show that thinks HTML
and embedded graphics are perfectly acceptable. (Those people tend to
top-post as well, so they're basically irredeemable at that point. :) )
g.
--
Proud owner of F-15C 80-0007
http://www.f15sim.com - The only one of its kind.
http://www.diy-cockpits.org/coll - Go Collimated or Go Home.
Some people collect things for a hobby. Geeks collect hobbies.
ScarletDME - The red hot Data Management Environment
A Multi-Value database for the masses, not the classes.
http://scarlet.deltasoft.com - Get it _today_!
On May 16, 2018, at 8:28 PM, geneb via cctalk
<cctalk at classiccmp.org> wrote:
On Wed, 16 May 2018, Ed Sharpe via cctalk wrote:
You mean "=C2=A0" ? Ed's mail has a Mime encoding
"quoted-printable",
not sure why. If your mail reader doesn't know how to handle Mime
headers, you'd see those encoding markers as actual text rather than as
the character they are supposed to represent. C2 A0 is UTF-8 for
"non-breaking space" which explains why many others haven't noticed
anything odd. OK I see there is a mix of photos in this
directory!
some tape reader some drum 2 separate topics.
Ed, I don't know if you (or anyone else) can see this, but there's two
junk characters at the end of every word you write. I see it in Alpine and it makes your
text nearly unreadable. :)