On 2018-07-01, at 19:03:32, Don Poitras wrote:
> ---
>> Mime-Version: 1.0
>> Content-Type: text/plain; charset=koi8-r; format=flowed
>> Content-Transfer-Encoding: 8bit
> ---
> I'm guessing Ed didn't intend to use a Russion character set. :) If that
> wasn't what
> was used in the email, then it was added as it progressed through the news
> servers.
>
Ed was replying to Shmuel who had headers:
Content-Type: text/plain; charset="koi8-r"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Monkey see; monkey doo?
Shmuel was apparently replying to me. My message had
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="tThc/1wpZn/ma/RB"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
The four parts were variously us-ascii and utf-8. The first occurrence
of koi8-r that I see was Shmuel's. The bottom half of koi8-r seems very
similar to us-ascii. Format=flowed would squeeze out multiple blanks.
Some component upstream in Ed's MUA converted blanks to NBSP (koi8-r?!)
intending to prevent their being squoze? Way too much DWIM here.
Simpler is better, I may switch to mutt,
gil
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN