Subj : Re: codepage
To : Michiel van der Vlist
From : Chris Jacobs
Date : Tue Feb 28 2023 01:54 am
-=> Michiel van der Vlist wrote to Rob Swindell <=-
MvV> Hello Rob,
MvV> On Sunday February 26 2023 22:11, you wrote to me:
>> > But oddly enough Synchronat BBS anwers in CP437 when quote replying
>> to an UTF-8 encoded > message... And this reply is being written using
>> a UTF-8 terminal.
RS> And this reply is being written using a UTF-8 terminal with some
RS> actual non-ASCII characters:
MvV> All three of your messages have non-ASCCI charcters. They all have the
MvV> degree character '°' in the sign off, or whatver you call it. In the
MvV> last message it is also present in the message test before the "--"
MvV> (two dashes).
RS> Norco, CA WX: 42.0°F, 79.0% humidity, 0 mph NE wind, 0.15 inches
RS> rain/24hrs
MvV> Considering that the CHRS kludge applies to the entire message, I think
MvV> it is more logical to look at the entire message including header,
MvV> footer en origin lines to determine the encoding.
MvV> Other than that: my comment was on Chris' message that was a
MvV> quote-reply to my message. He quoted the UTF-8 encoded text but the
MvV> reply was in CP437 thereby messing up the quote.
Your message was not entirely UTF-8. It contained a legacy ö
That caused Notepad Kladblok to interpret all of it as legacy.
MvV> Chris seems to have a preference for doing away with "legacy"
MvV> encodings, so I was a bit surprised that his reply was encoded in CP437
MvV> instead of UTF-8.
