On 2018-11-25 7:45 PM, Bill Gunshannon via cctalk wrote:
> It's not a mailing list problem. It's not even a mail problem. It's a
>
> Mail User Agent problem. It is a display problem. It is up to the
>
> users mail program to display the email as it was sent. Unless the
>
Did you really dou
It's not a mailing list problem. It's not even a mail problem. It's a
Mail User Agent problem. It is a display problem. It is up to the
users mail program to display the email as it was sent. Unless the
user doesn't want to see anything in character sets other than
their favorite. Nothing
Hi Frank and others-
Yea it is only here we have the problem. or at leased this is the only
list serve that does not like it.
I wondered if something could be handled at the listserv end or not but
I have littleknowledge of list serves alas...
Sad when people spent
On 11/25/18 4:32 PM, Bill Degnan via cctalk wrote:
Most mail servers sending inbound messages to the list include the
encoding scheme in the header. The mailer program should process
and translate the email message body accordingly...in theory anyway.
Most email handling programs don't need
Most mail servers sending inbound messages to the list include the encoding
scheme in the header. The mailer program should process and translate the
email message body accordingly...in theory anyway. The set up and testing
of a sampling of encoding variations would reveal which interpreters were
Very old mail programs indeed have no understanding whatsoever of character
sets or encoding. They simply display data from the e-mail file on stdout or
equivalent. If you are lucky, the character set and encoding in the e-mail
match the character set and encoding used by your terminal.
The e
