Hello Michiel,

On Sun Jul 12 2020 13:22:18, Michiel van der Vlist wrote to BjÔrn Wiberg:

 MV> Hello BjÔrn,

 MV> On Sunday July 12 2020 12:35, you wrote to All:

 BW>> @MSGID: 2:201/137 544774fd
 BW>> @TID: Mystic BBS 1.12 A46
 BW>> @TZUTC: 0200

 MV> No CHRS kludge..,

 BW>> BjÔrn
 MV>        ^
 MV> Without a CHRS kludge to indicate what encoding is used, one can not
 MV> expect non-ASCII characters to be displayed correctly...

While one can not expect it, you can definitely assume it. Almost 100% of the
time when a CHRS kludge is not used the original sender is using a BBS software
that doesn't support the CHRS kludge. Mystic may be one that can be fixed, but
there are a lot of other programs being used today that aren't supported by a
developer any more and you won't be able to convince the user of said software
to change.

xlatimport cp437

Should fix this for you. This way you can spend more time with grandkids, or
taking walks, or fishing, or whatever you enjoy doing outside of Fidonet,
rather than contstantly nit-picking miniscule things in a dying hobby.

And since I imported it as cp437, I should have now converted it to UTF-8, just
for you. ;)

Regards,
Nick

... "Take my advice, I don't use it anyway."
--- GoldED+/LNX 1.1.5-b20181215