Hello Bj”rn,

On Monday May 27 2019 10:58, you wrote to me:

 MvdV>> I noticed that as well. Our estimed Fidonews editor has patched
 MvdV>> the software to accept non-ASCII characters but he has
 MvdV>> neglected to specify the encoding for submitted articles, From
 MvdV>> what I gleen the article was submitted using CP1252 Aka
 MvdV>> Centraal-Europees Windows. The articles are published with a
 MvdV>> "CHRS 850 2" kludge.

 MvdV>> That's where it goes wrong.

 BF>    Oh, BTW, your analysis is totally wrong.

"Totally"? As in EVERYTHING I mentioned is wrong?

 BF>    There are two programs involved here.

I mentioned "software". That can mean more than one program.

 BF> The first is MAKENEWS.EXE that I indeed patched even before I became
 BF> editor -- in October 2001 to be exact.

So the part of my analysis that mentioned you patched software is correct.

 BF> This is the program that produces the actual Fidonews. For obvious
 BF> reasons there are no kludges involved here, and neither are there any
 BF> in the pure text files of the submitted articles.

Of course. That does not alter the fact that you neglected to specify in which
encoding these "pure text files" should be submitted. Neither artspec.doc not
the trailer in the snooze itself makes any mention of it. So that part of my
analysis is also correct.

 BF>    The second program is the NEWSPREP program that posts the Fidonews
 BF> in this and another related echo. I don't have to patch it, because I
 BF> have the source code.

So you may claim that part of my analysis is incomplete.

 BF> And I did make a change in it a decade or so ago, to go for "CHRS 850
 BF> 2".

And so the part of my analysis that stated the message in the echo displayed a
"CHRS CP850 2" kludge is aldso correct.

Are you disputing my part of the analysis that Ward's article was encoded in
CP1252?

Your claim that my analysis is "totally wrong" is wrong. The most you can say
it that it is incomplete on one point.

 BF> It was on your request, so that your copyright symbol would show
 BF> properly...

Be that as it may be, that does not make my analysis incorrect. I may indeed
have made a request to that effect in the distant past. I am still not too old
to adapt and gain new insight. If I made such a request I hereby withdraw it
and make a plea for UTF-8.


Cheers, Michiel

--- GoldED+/W32-MSVC 1.1.5-b20170303