<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">On 05/05/2023 10:26, Harald
Hanche-Olsen wrote:<br>
</div>
<blockquote type="cite"
cite="mid:etPan.6454cbdb.4a37deb9.21a@runbox.no">Just to get in
one more lash before we bury the poor creature, the original email
was actually not a pure HTML mail. Its content type is
multipart/alternative. The non-breaking spaces are indeed found in
the text/html part, but they are also in the text/plain part. And
for that, I can think of no excuse. (It might be interesting to
see if Thunderbird does the same thing if set to just produce
text/plain.)</blockquote>
<p>What I find interesting is that Seamonkey appears to code around
its own deficiencies — no matter whether I look at the text/plain
or the HTML version as received back here, neither contains any
trace of a U+00A0. Furthermore, TeXworks appears to accept U+00A0
as input, but when that text is copied back from the editor
window, all trace of U+00A0 has disappeared.</p>
<p>I wonder whether I should just add <br>
</p>
<p>
<blockquote type="cite"><tt>\catcode `\ = 10 % <space></tt></blockquote>
at the top of any code that I post here ...<br>
</p>
<p>-- <br>
<i>Philip Taylor</i><br>
</p>
</body>
</html>