16 Oct
2012
16 Oct
'12
4:01 p.m.
On Tue, 16 Oct 2012, Fred Cisin wrote:
It was caused by the unicode character used as an apostrophe in the
"visitor's center" part of the subject line (I used a standard apostrophe
in my example here). My guess is it happened from cutting and pasting part
of the subject line from a website?
>>>
Re: A petition to Apple's Leadership Team - Create a public
>>> venue / visitors center
>> It was NOT ASCII.
>> What I got was:
>> =?Windows-1252?B?UmU&IEEEgcGVCaXRpb24gdG8gQXBwbGUncyBMZWFkZXJzaG1wIFR
>> and so forth!
> Subject: =?windows-1252?Q?A_petition_to_Apple=27s_Leadership_Team_-_Creat?=
> =?windows-1252?Q?e_a_public_venue_/_visitor=92s_center?=
> Absolutely bizarre. This must be a MIME feature that I'm not
> familiar with.
On Tue, 16 Oct 2012, Mouse wrote:
See RFC 1522.
Thank you. I did.
What "NON ASCII" characters "needed" to be "corrected" in
the original
subject line (reproduced at the top of this message) to justify such
corruption? I got ONE that was COMPLETELY incomprehensibly
garbled, and am getting
the rest with extraneous "[Windows 1252]"s sprinkled throughout. I can
easily wade through that; it is just annoying.
(I am currently reading this on PINE in a unix shell account - am I
being pressured into using Outhouse?)
I'm using Alpine and it apparently handled it since I never even noticed
until it was brought up. I do purposefully run a UTF-8 capable terminal
emulator though.