On 18/05/2019 04.48, Jeffrey Taylor wrote:
On 5/17/19 3:48 PM, Carlos E. R. wrote:
On 17/05/2019 22.36, Jeffrey Taylor wrote:
Below is the reply, composed in Thunderbird, that has been queued up to send thru a Gmail app server (smtp.gmail.com) for two days now. I've re-routed it thru my Old School mail route: emacs, Mutt, Postfix, a local Web/Email hosting company (noise.org). How much of the original charset, Content-* headers, and Email headers will survive I won't known until the Bcc reaches me. When it> left emacs, there was a UTF-8 hard space after "... mailing lists." It displays perfectly here, both in Thunderbird and Alpine. When I save to file, I just see 0x73 0x20 0x20.
I edited the first 0x20 to 0xA0 to see the effect in the file. I believe it is not Thunderbird who generates that character, it is some other application you use. Th simply leaves it there.
For this usecase, unchecking "Compose in HTML Format" stops the insertion of the hard space. For this e-mail, it's checked. There should be a hard space after each period ending a sentence. I did not find a way to force Thunderbird to use 7bit ASCII. That wasn't the real issue, just a work around.
Yes, in this email I see it, but only when saving to file and looking with a hex editor: hexdump -C p 6b0 68 20 76 69 73 69 62 6c 65 20 67 6c 79 70 68 73 |h visible glyphs 6c0 20 66 6f 72 20 74 68 65 20 63 6f 6e 74 72 6f 6c | for the control 6d0 20 63 6f 64 65 73 20 66 72 6f 6d 20 30 78 38 30 | codes from 0x80 6e0 20 74 6f 20 30 78 39 46 20 0a 72 61 6e 67 65 2e | to 0x9F .range. 6f0 c2 a0 20 57 68 61 74 20 49 27 6d 20 67 6f 69 6e |.. What I'm goin ***** 700 67 20 74 6f 20 64 6f 20 77 69 74 68 20 61 6c 6c |g to do with all In Thunderbird or Alpine, your mail displays perfectly. I have never encountered this problem you say, but then, I have never written using two spaces in my life. I'll try now. Here. Using Thunderbird in plain text mode.
All this reply text was typed directly into Thunderbird.
It has been educational, but time consuming. I now know how to control HTML/plain text and charset encoding: globally, by account, and by individual e-mail. Also that Western, AKA Windows-1252, is a superset of Latin-1 with visible glyphs for the control codes from 0x80 to 0x9F range. What I'm going to do with all that, I haven't figured out. I thought by now everyone could handle Unicode. Turns out not to be the case.
No, they don't. Windows uses a different solution than Linux. But email doesn't have problems if done correctly, because the headers say what exact charset is used. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)