On 2014-02-20, at 07:01, Blaicher, Christopher Y. wrote:

> FYI - I am running OUTLOOK 2013 on a windows 7 system and have no problem 
> with Scott's messages.
>
And I have no problem reading them with Thunderbird.  But the
problem clearly appears when reading them from the web site.
Even the Subjects are garbled.


> -----Original Message-----
> From: IBM Mainframe Assembler List [mailto:ASSEMBLER-LIST@LISTSERV.UGA.EDU] 
> On Behalf Of Walt Farrell
> Sent: Thursday, February 20, 2014 6:58 AM
>
> Something changed, Scott, in the way you're sending your messages. The ones 
> you sent to this list on "Tue, 18 Feb 2014 11:35:15 -0500" amd "Tue, 18 Feb
> 2014 11:51:23 -0500" were just fine. But starting with the one at "Wed, 19 
> Feb 2014 18:58:19 +0000" they're garbled, and Base-64 encoded due to UTF-8 
> character content, which messes up the list's web interface and archives.
>
As an example:

FWIW, one of Walt's plies contained the conventional header:

   Date:         Tue, 18 Feb 2014 16:24:52 -0500

Some troublemaker downstream (Yahoo!?) chose to
reflect this in quoted text as:

507 $ echo "Sent: ‎Tuesday‎, ‎February‎ ‎18‎, ‎2014 ‎1‎:‎24‎ ‎PM" | od -tx1
0000000 53 65 6e 74 3a 20 e2 80 8e 54 75 65 73 64 61 79
0000020 e2 80 8e 2c 20 e2 80 8e 46 65 62 72 75 61 72 79
0000040 e2 80 8e 20 e2 80 8e 31 38 e2 80 8e 2c 20 e2 80
0000060 8e 32 30 31 34 20 e2 80 8e 31 e2 80 8e 3a e2 80
0000100 8e 32 34 e2 80 8e 20 e2 80 8e 50 4d 0a

Wikipedia, which is always right, tells me that the cliche
E2808E is a Unicode Left-to-Right mark.

Why?  Grrr...!

> So something changed at your end between the messages that work properly and 
> those that are now failing. I find it interesting, too, that the timezone 
> your computer is using is different. You were previously at GMT-5 (US east
> coast) and now you're running at GMT. So perhaps what happened is that you 
> changed computers. If so, you need to configure your email client to have the 
> settings you were using before, and it's probably something to do with the 
> character encoding of your messages.
>
UTF-8 Unicode is a fact of life.  It's gratuitous of Outlook (I
suspect) to insert the Left-to-Right mark, then encode the entire
message base-64 when quoted-printable would suffice.  But it's
likewise irresponsible for LISTSERV nowadays not to deal with
Unicode and base-64.  Has anyone contacted the owners of IBM-MAIN
and ASSEMBLER-LIST about this problem, which presumably can be
solved only by L-Soft?

Redacting of time zones in quoted text is endemic among mailers;
confusing when a single thread of my correspondence may include
participants in Colorado, UK, and Australia.

-- gil

Reply via email to