From Newsgroup: news.software.readers

[Please do not remove quotation level indicators. Fixed below.]

Adam H. Kerman wrote:

Thomas 'PointedEars' Lahn <usenet@PointedEars.de> wrote:

Adam H. Kerman wrote:

Also, in followup, I parse for all that crap added to articles that make >>> them other than plain text, like nonbreaking spaces.

No(n)-break(ing) spaces *are* part of plain text, have been since ISO-8859-1 >> and Windows-1252 (arguably the first 8-bit character encodings for PCs).
And they can be very useful.

I am well aware. I understand what it's used for.

No, I do not think so:

When trn users who care about this send an article, it is genuine plain
text, devoid of all nontext characters.

No(n)-break(ing) spaces are not "nontext characters" (which is an oxymoron).

It serves a function in typography.

Yes. It has happened to me that I wanted to write something in a Usenet article, I hit the (I think) 76 characters per line limit of my newsreader,
and I really did not want the text to be wrapped in-between, like the figure and the unit of a quantity being on separate lines because of this, and
manual line-wrapping was not an option. Inserting a non-breaking space
solved this. Your replacing it with an ordinary space character would re-introduce the problem when my text would be quoted and wrapped (at some point in a longer discussion a quotation needs to be rewrapped).
--
PointedEars

Twitter: @PointedEars2
Please do not cc me. / Bitte keine Kopien per E-Mail.
--- Synchronet 3.21f-Linux NewsLink 1.2