(I will return to the boiler issue once I get my detailed quote!!)
Curious, the encoding for your posts is setup, and presumably amendable, when you created your Usenet a/c in Thunderbird. What is it set to? Might be worth changing and testing on the post you know creates a problem?
At the moment, it's set to ISO-8859-1, which it seems to ignore and use utf-8 instead.
I did try other encodings when it was pointed out to me, I've just changed it to utf-8 and will try replying back to the original message that triggered it ...
Nothing to add, just checking it it triggers base64 again?
Yes, my original post contained the phrase "supply. Dad"
In Harry's reply, that has become "supply. Dad"
And when I reply to Harry's reply, thunderbird sees the  = C3 82 = U+00C2, and switches my reply to base64
Interestingly alan_m's reply has the same, but Andrew's doesn't, even though all everyone up to that point is using thunderbird
Using a hex editor I can't see anything odd in my message?
"Suffice to say it's all relics from time immemorial; the irony being that there's a "feature" of automagically creating non-breakable spaces from regular spaces which later creates the need for that other "feature" of eliminating them again, due to another "feature" of automatically downgrading messages from HTML to plaintext..."
Hammering the space key, apparently causes NBSP to appear. There is a PlainTextSerializer, with lengthy code present in one of the modules.
A philisophy of "vashy-vashy", endless playing with the users typed input, and it seems to come from the Netscape era. Yet, the above thread, Wayne indicates there is no one to work on editor issues.
In TB115, I've lost how Content Encoding works. It's disappeared from the preferences. I just don't know what to type in my simple search thing, to try to pick up where the encoding detection is now done. Sure, maybe it is in the Configuration Editor. The documentation I can find on the web, still refers to TB 1.5 or so.
Paul
It's possible multiple spaces in a row, are playing a part. But, what feature has to be turned on, to make that feature "live". If I hammer the space bar here nothing bad happens.
Paul
The about:config setting mail.strictly_mime is implicated, I do have that set to true, I wonder if Harry and alan_m don't and Andrew does?
Have something to add? Share your thoughts — no account required.
Ask the community — no account required