Hi Maurice,

On 2020-12-02 16:44:14, you wrote to me:

 WvV>> That's a broken MSGID implementation, because it could be
 WvV>> possible your system generates 2 (or more) messages in the same
 WvV>> second (maybe automated ones).

 MK> Understood.  I noticed that way back in the 1990's and brought it up back
 MK> then.  However for a single user application such as what I am doing this
 MK> is not an issue.  Basically all I've done is to write an offline
 MK> application using a slightly modified FTN MSG format that generates it's
 MK> own MSGID so that when tossed by a regular automated tosser such as hpt
 MK> (not abandonware ... yet) there shouldn't be an issue with dupes since
 MK> there are none.  Right?

Unless your application can crosspost a single written message to multiple
other areas? They all need different MSGID's...

 MK>>> ... A Møøse once bit my sister ...

 WvV>> Illegal characters without a CHRS: kludge!

 MK> Again it appears to be working without a useless CHRS kludge, especially
in
 MK> the case of UTF-8 as the above quote clearly demonstrates.  Also with
older
 MK> 16-bit DOS editors quoting UTF-8 characters works 100% which cannot be
said
 MK> about most (all?) FTN compliant editors.

If I were using a message editor that could and was configured to display
different charactersets. It wouldn't know how to display this one, because of
the missing CHRS kludge.


Bye, Wilfred.

--- FMail-lnx64 2.1.0.18-B20170815