In Thunderbird (at least in v156.0.1; older version may still have a hamburger menu), please go to (Menu bar) Tools -> Settings -> General and scroll all the way down to Config Editor... (I was attempted to write a proper U+2026 horizontal ellipsis C"BB& here but I know that the listserv software will mangle all non-ASCII characters just like it mangled your U+A0 non-breaking space.)
Search for the configuration option mailnews.send_plaintext_flowed and set it to false.
In my copy of Thunderbird, itC"BBs set to true, too, but I don't remember my Thunderbird sending \xA0 to this list for indentation.
But please give it a try. It might deter Thunderbird from well-intended indentation using NBSPs.
Gerrit
On 30.09.2026 17:14, Trevor Nicholls trevor@xxxxxxxxxxxxxxxxxx wrote:
Thanks for the links, I'll have a look now
BTW I am posting in plain text... and when I inspect my message in my sent folder it is plain text.... but when it gets sent back to me by the listserv all leading spaces are folded to \xA0 characters.
It's clearly NOT plain text, it just looks that way.
(I recently switched from Outlook to Thunderbird and this started happening on all listservs I belong to. It must be a problem at my end and I can only keep apologising until I find out how to fix it)
cheers
T
On 1/10/2026 04:08, Imsieke, Gerrit, le-tex gerrit.imsieke@xxxxxxxxx wrote:
Hi Trevor,
I, too, find it difficult to read. But you can try our adaptations of Andrew Welch's method. For CALS tables it's https://github.com/transpect/xslt-util/blob/master/calstable/xsl/normalize.xsl, for HTML tables, it's https://github.com/transpect/htmltables/.
In the latter repo there's html-tables-normalize.xsl that imports http://transpect.io/xslt-util/lengths/xsl/lengths.xsl. This URI doesn't resolve out of the box. In our pipelines, we use a catalog resolver for these URIs. But you can clone https://github.com/transpect/xslt-util, keep only the lengths subdirectory (or even lengths.xsl alone) and import lengths.xsl via relative path.
Gerrit
On 30.09.2026 16:29, Trevor Nicholls trevor@xxxxxxxxxxxxxxxxxx wrote:
Sorry I don't know how that happened, what's below should be easier to read
|
Cart
