Hello Paul,

On Tuesday June 09 2020 20:13, you wrote to me:

 PQ>>> @CHRS: UTF-8 2
 MV>>               ^

 MV>> JamNNTP has bugs as well in delaing with UTF-8. See above. Also,
 MV>> AFAIK, it assumes that the header is always Latin-1.

 PQ> Yes.  Perfection is difficult with Fidonet; it's an amateur
 PQ> undertaking.

The "UTF-8 2" instead of "UTF8-8 4" isn't really a problem I think. AFAIK all
readers/editor that can do UTF-8 seem to ignore the level field. I have not
heard of a counter example yet.

This is what FTS-5003 has to say on the matter:

  Some implementations do not add the  field and some
  implementations erroneously present "UTF-8 2" instead of "UTF-8 4".
  Well mannered implementations should gracefully handle this situation
  when reading messages. The recommended way of doing this is to
  ignore the level parameter and only use the name of the identifier.
  In future the level parameter may become obsolete.

 PQ> That JamNNTPd is in a UTF-8 Linux environment and has been told not to
 PQ> make any translations.  That Thunderbird is in the /same/ environment.

That it insists the header is always Latin-1 independant of the encoding of the
text body is what I consider am more sreious problem.


Cheers, Michiel

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