TZUTC: -0800
MSGID: 329.fidoutf8@1:103/705 2868eb5d
REPLY: 2:280/5555 640319a0
PID: Synchronet 3.20a-Linux master/5d1d586fd Mar  3 2023 GCC 12.2.0
TID: SBBSecho 3.20-Linux master/067c40063 Mar  3 2023 GCC 12.2.0
COLS: 80
BBSID: VERT
CHRS: CP437 2
NOTE: FSEditor.js v1.104
  Re: codepage
  By: Michiel van der Vlist to Rob Swindell on Sat Mar 04 2023 11:00 am

 > Hello Rob,
 >
 > On Thursday March 02 2023 17:02, you wrote to me:
 >
 >  >> All three of your messages have non-ASCCI characters. They all have
 >  >> the degree character 'ø' in the sign off, or whatver you call it.
 >  >> In the last message it is also present in the message test before
 >  >> the "--" (two dashes).
 >
 >  RS> Ah, true. But in the message I posted using a UTF-8 terminal, that
 >  RS> would have been a UTF-8 encoded "degree" symbol instead of a
 >  RS> CP437-encoded one (as would have been in the other messages, including
 >  RS> this one).
 >
 > The message I am respondig to, is indeed encoded in CP437.
 >
 > So let me get this straight:
 >
 > 1) If the message that is responded to, is encoded in CP437, Synchronet
 > answers in CP437. Yes?

No. The message response itself determines the encoding and only CP437
terminals can faithfully author CP437 encoded messages. If a UTF-8 terminal
user responds to a CP437 encoded message (with non-ASCII chars), the original
message text is converted to UTF-8 before it is quoted and the response will
be UTF-8. Unless there are no non-ASCII chars in the response, in which case
the response charset witll just be ASCII.

 > So what happens if the response does not fit into CP437?

I think this question is making false assumptions.

 > What happens if the original message is encoded in a one byte encoding other
 > than CP437?

The only encodings Synchronet supports for message text are ASCII, CP437, and
UTF-8.

 > 2) If the message that is responded to is encoded in UTF-8, Synchronet
 > answers in UTF-8 if the terminal theis used supports UTF-8. Yes?

Yes.

 > So what happens in that case if the terminal does not support UTF-8?

The message text would be converted to CP437 before being quoted and the
response would be in CP437.

 >  >>  RS> Norco, CA WX: 42.0øF, 79.0% humidity, 0 mph NE wind, 0.15
 >  >> inches RS> rain/24hrs
 >
 > My software translates the CP437 encoded degree sign into UTF-8 as you can
 > see.

Yup, most software does the same, when appropriate.
-- 
                                            digital man (rob)

Sling Blade quote #18:
Karl Childers: Some folks call it Hell, I call it Hades.
Norco, CA WX: 55.8øF, 64.0% humidity, 5 mph SE wind, 0.01 inches rain/24hrs
--- SBBSecho 3.20-Linux
 * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
SEEN-BY: 10/0 1 103/705 106/201 153/7715 218/0 1 700 860 226/30 227/114
SEEN-BY: 229/111 112 113 307 317 426 428 470 700 317/3 320/219
PATH: 103/705 218/700 229/426