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.
Yet your posting here was not in HTML, it was plain/text, transfer-encoding 8bit, contained only 7bit chars.
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.
I thought by now everyone could handle Unicode. Turns out not to be the case.
What have you found that doesn't handle unicode? -- Per Jessen, Zürich (13.1°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org