In "MSGID: 2:203/2 52d36718" the kludge he deployed was "CHRS: UTF-8 2" which at his end produced a 0xf6 character rather than a proper UTF-8 character. Some editors will correct this as they remap ISO-8859-1 characters to the corresponding UTF-8 character. They happen to 'match' ... sort of. They do remap nicely.
It was your software that remapped it to CP437 and not Björn's although sending it with a "CHRS: UTF-8 2" kludge is kind of asking for trouble methinks. Despite this flaw your software still got it wrong as there is nothing in that message that assumes that CP437 is indeed a valid remap and frankly latin-1 with a "CHRS: UTF-8 2" kludge would have been to safest remap and indeed would have been correct in this case.
ml> see above...
Exactly. Your software is at fault although Björn isn't helping matters any. I don't think mixing UTF-8 with 8-bit characters is ever a good idea, especially when sysops such as yourself get them wrong and then falsely argue that your codepage is what EVERYONE uses, especially an obsoleted one such as IBMPC. That is total BS and always has been.
Life is good, Maurice
... A Møøse once bit my sister ... --- GNU bash, version 4.2.45(2)-release (x86_64-unknown-linux-gnu) * Origin: Pointy Stick Society - Ladysmith BC, Canada (1:153/7001.0)
