• codepage

    From Chris Jacobs@1:103/705 to All on Sat Feb 25 12:52:34 2023
    Is codepage 437 a Vertrauen BBS thing or a multimail thing? Can I use utf-8 if I don't use multimail like now?

    Chris
    --- SBBSecho 3.20-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Alan Ianson@1:153/757 to Chris Jacobs on Sat Feb 25 13:09:52 2023
    Is codepage 437 a Vertrauen BBS thing or a multimail thing? Can I use utf-8 if I don't use multimail like now?

    CP437 is a codepage, it was used a lot by BBSs of yesterday and even today. It's not really a BBS or Synchronet thing although if you type in any CP437 characters (line drawing characters, perhaps) synchronet will set the CHRS kludge to CP437. If you type in any utf8 characters Synchronet will set the CHRS kludge to "UTF-8 4".

    The message I am replying to has a CHRS kludge of "ASCII 1".

    The reply I am writting now will likely have a kludge like LATIN-1.

    It's nothing to worry about. It is there so the person reading your mail can read it as expected.

    --- BBBS/Li6 v4.10 Toy-6
    * Origin: The Rusty MailBox - Penticton, BC Canada (1:153/757)
  • From Michiel van der Vlist@2:280/5555 to Alan Ianson on Sat Feb 25 23:01:12 2023
    Hello Alan,

    On Saturday February 25 2023 13:09, you wrote to Chris Jacobs:

    The reply I am writting now will likely have a kludge like LATIN-1.

    It does.

    It's nothing to worry about. It is there so the person reading your
    mail can read it as expected.

    But oddly enough Synchronat BBS anwers in CP437 when quote replying to an UTF-8 encoded message...


    Cheers, Michiel

    --- GoldED+/W32-MSVC 1.1.5-b20170303
    * Origin: http://www.vlist.eu (2:280/5555)
  • From Alan Ianson@1:153/757.2 to Michiel van der Vlist on Sat Feb 25 14:26:38 2023
    Hello Michiel,

    The reply I am writting now will likely have a kludge like
    LATIN-1.

    It does.

    I think this one will too.

    If I remember right I setup golded to use that because by default it uses "UTF-8 2". Not quite correct but closer to the truth.

    All of my terminals here are UTF-8 although I don't see UTF-8 correctly in any of my readers, not on the BBS or when reading with golded.

    I can setup golded to use an external editor and when I hit reply I see the UTF-8 characters correctly.

    It's nothing to worry about. It is there so the person reading
    your mail can read it as expected.

    But oddly enough Synchronat BBS anwers in CP437 when quote replying to
    an UTF-8 encoded message...

    Synchronet is generally good about the CHRS kludge but I guess it doesn't look at the encoding of the reply. Perhaps it needs to be looked at.

    Ttyl :-),
    Al

    ... Conscience gets a lot of credit that belongs to cold feet
    --- GoldED+/LNX 1.1.5-b20230221
    * Origin: The Rusty MailBox - Penticton, BC Canada (1:153/757.2)
  • From Michiel van der Vlist@2:280/5555 to Alan Ianson on Sun Feb 26 09:32:19 2023
    Hello Alan,

    On Saturday February 25 2023 14:26, you wrote to me:

    @MSGID: 1:153/757.2 63fa8cca
    @REPLY: 2:280/5555 63fa857a
    @CHRS: LATIN-1 2
    @TZUTC: -0800
    @TID: hpt/lnx 1.9 2023-02-18
    Hello Michiel,

    I think this one will too.

    See above.

    If I remember right I setup golded to use that because by default it
    uses "UTF-8 2". Not quite correct but closer to the truth.

    There is trick to make it "UTF-8 4". See my message.

    All of my terminals here are UTF-8 although I don't see UTF-8
    correctly in any of my readers, not on the BBS or when reading with golded.

    Golded has its limits and do do many other Fidonet readers when it comes to UTF-8.

    Goated and Gosiped do it right.

    I can setup golded to use an external editor and when I hit reply I
    see the UTF-8 characters correctly.

    So can I. I use Winvi for that. But it has other issues...

    But oddly enough Synchronat BBS anwers in CP437 when quote
    replying to an UTF-8 encoded message...

    Synchronet is generally good about the CHRS kludge but I guess it
    doesn't look at the encoding of the reply. Perhaps it needs to be
    looked at.

    yeah...


    Cheers, Michiel

    --- GoldED+/W32-MSVC 1.1.5-b20170303
    * Origin: http://www.vlist.eu (2:280/5555)
  • From Alan Ianson@1:153/757.2 to Michiel van der Vlist on Sun Feb 26 01:28:43 2023
    Hello Michiel,

    There is trick to make it "UTF-8 4". See my message.

    What is the trick?

    Golded has its limits and do do many other Fidonet readers when it
    comes to UTF-8.

    Yes, that is the truth. In spite of that I am happy with golded. It must be more than 20 years I have used it now.

    Goated and Gosiped do it right.

    I have read a bit about those but never had a look. Are they open source?

    Ttyl :-),
    Al

    ... As easy as 3.1415926535897932384626433832795028841
    --- GoldED+/LNX 1.1.5-b20230221
    * Origin: The Rusty MailBox - Penticton, BC Canada (1:153/757.2)
  • From Carlos Navarro@2:341/234.1 to Alan Ianson on Sun Feb 26 12:20:51 2023
    26 Feb 23 01:28:43, Alan Ianson wrote to Michiel van der Vlist:

    Goated and Gosiped do it right.

    I have read a bit about those but never had a look. Are they open source?

    Yes, https://github.com/askovpen/gossiped

    Carlos


    --- gossipEd-windows/amd64 .0.25-59c94b9b
    * Origin: cyberiada (2:341/234.1)
  • From Michiel van der Vlist@2:280/5555 to Alan Ianson on Sun Feb 26 14:04:11 2023
    Hello Alan,

    On Sunday February 26 2023 01:28, you wrote to me:

    There is trick to make it "UTF-8 4". See my message.

    What is the trick?

    For the internal Golded editor when translating to and from the local character set to UTF-8, use two parameters in the level line of the translation table. The first parameter being the level of the table, the second parameter is the level to display un the CHRS kludge.

    See 850_utf.chs nd utf_850.chs as example.

    For use with en external editor in golded use UTF_UTF.CHS as a dummy translation table.

    In the golded config used with the external editor add this:

    XLATIMPORT UTF-8
    XLATLOCALSET UTF-8
    XLATEXPORT UTF-8
    XLATCHARSET UTF-8 UTF-8 UTF_UTF.CHS

    Download the *.CHS files from http://www.vlist.eu/downloads/

    or file request the from my system.

    I have read a bit about those but never had a look. Are they open
    source?

    I have never looked at the source myself, just downloaded the .exe, but the grape vine say "yes"


    Cheers, Michiel

    --- GoldED+/W32-MSVC 1.1.5-b20170303
    * Origin: http://www.vlist.eu (2:280/5555)
  • From Rob Swindell@1:103/705 to Michiel van der Vlist on Sun Feb 26 22:06:00 2023
    Re: codepage
    By: Michiel van der Vlist to Alan Ianson on Sat Feb 25 2023 11:01 pm

    Hello Alan,

    On Saturday February 25 2023 13:09, you wrote to Chris Jacobs:

    The reply I am writting now will likely have a kludge like LATIN-1.

    It does.

    It's nothing to worry about. It is there so the person reading your mail can read it as expected.

    But oddly enough Synchronat BBS anwers in CP437 when quote replying to an UTF-8 encoded message...

    It depends on the terminal used to write the reply. This reply is being written using a CP437 terminal.
    --
    digital man (rob)

    Sling Blade quote #19:
    Doyle: I can't so much as drink a damn glass of water around a midget
    Norco, CA WX: 42.0F, 79.0% humidity, 0 mph NE wind, 0.15 inches rain/24hrs
    --- SBBSecho 3.20-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Rob Swindell@1:103/705 to Michiel van der Vlist on Sun Feb 26 22:07:05 2023
    Re: codepage
    By: Michiel van der Vlist to Alan Ianson on Sat Feb 25 2023 11:01 pm

    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.
    --
    digital man (rob)

    Rush quote #54:
    He'd love to spend the night in Zion, he's been a long, long while in Babylon Norco, CA WX: 42.0F, 79.0% humidity, 0 mph NE wind, 0.15 inches rain/24hrs
    --- SBBSecho 3.20-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Rob Swindell@1:103/705 to Michiel van der Vlist on Sun Feb 26 22:11:17 2023
    Re: codepage
    By: Rob Swindell to Michiel van der Vlist on Sun Feb 26 2023 10:07 pm

    Re: codepage
    By: Michiel van der Vlist to Alan Ianson on Sat Feb 25 2023 11:01 pm

    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.

    And this reply is being written using a UTF-8 terminal with some actual non-ASCII characters:

    Norco, CA WX: 42.0°F, 79.0% humidity, 0 mph NE wind, 0.15 inches rain/24hrs
    --
    digital man (rob)

    Breaking Bad quote #17:
    Your breath could knock the buzzard off a shit wagon. - Hank Schrader
    Norco, CA WX: 42.0°F, 79.0% humidity, 0 mph NE wind, 0.15 inches rain/24hrs --- SBBSecho 3.20-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Michiel van der Vlist@2:280/5555.1 to Rob Swindell on Mon Feb 27 15:12:33 2023
    Hello Rob,

    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.

    And this reply is being written using a UTF-8 terminal with some
    actual non-ASCII characters:

    All three of your messages have non-ASCCI charcters. 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).

    Norco, CA WX: 42.0°F, 79.0% humidity, 0 mph NE wind, 0.15 inches rain/24hrs

    Considering that the CHRS kludge applies to the entire message, I think it is more logical to look at the entire message including header, footer en origin lines to determine the encoding.

    Other than that: my comment was on Chris' message that was a quote-reply to my message. He quoted the UTF-8 encoded text but the reply was in CP437 thereby messing up the quote.

    Chris seems to have a preference for doing away with "legacy" encodings, so I was a bit surprised that his reply was encoded in CP437 instead of UTF-8.


    Cheers, Michiel

    --- GoldED+/W32-MSVC 1.1.5-b20130111
    * Origin: Michiel's laptop (2:280/5555.1)
  • From Chris Jacobs@1:103/705 to Michiel van der Vlist on Tue Feb 28 01:54:00 2023
    Michiel van der Vlist wrote to Rob Swindell <=-

    Hello Rob,

    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.

    And this reply is being written using a UTF-8 terminal with some
    actual non-ASCII characters:

    All three of your messages have non-ASCCI charcters. 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).

    Norco, CA WX: 42.0°F, 79.0% humidity, 0 mph NE wind, 0.15 inches rain/24hrs

    Considering that the CHRS kludge applies to the entire message, I think it is more logical to look at the entire message including header,
    footer en origin lines to determine the encoding.

    Other than that: my comment was on Chris' message that was a
    quote-reply to my message. He quoted the UTF-8 encoded text but the
    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.

    Chris seems to have a preference for doing away with "legacy"
    encodings, so I was a bit surprised that his reply was encoded in CP437 instead of UTF-8.


    Cheers, Michiel

    --- GoldED+/W32-MSVC 1.1.5-b20130111
    * Origin: Michiel's laptop (2:280/5555.1)

    ... MultiMail, the new multi-platform, multi-format offline reader!
    --- MultiMail/Win v0.52
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Michiel van der Vlist@2:280/5555 to Chris Jacobs on Wed Mar 1 09:56:30 2023
    Hello Chris,

    On Tuesday February 28 2023 01:54, you wrote to me:

    Other than that: my comment was on Chris' message that was a
    quote-reply to my message. He quoted the UTF-8 encoded text but
    the 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.

    Ah yes.. If there is just ONE byte with bit 7 set that is not part of a well formed UTF-8 string, the entire text is considered legacy encoded. Notepad is very strict in that. And it isn't the only one. Winvi does the same. Fortunately the manual overrride to UTF-8 in Winvi is just one mouse click away.

    Still... when used for Fidonet I say this behaviour is too stricht. The "CHRS UTF-8 ?" in the quoted message should be leading IMNSHO. If the quoted message is in UTF, the respons should also be in UTF whenever possible. Even if the quoted message contains a few bytes legacy encoding.


    Cheers, Michiel

    --- GoldED+/W32-MSVC 1.1.5-b20170303
    * Origin: Nieuw Schnøørd (2:280/5555)
  • From Rob Swindell@1:103/705 to Michiel van der Vlist on Thu Mar 2 17:02:48 2023
    Re: codepage
    By: Michiel van der Vlist to Rob Swindell on Mon Feb 27 2023 03:12 pm

    Hello Rob,

    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.

    And this reply is being written using a UTF-8 terminal with some
    actual non-ASCII characters:

    All three of your messages have non-ASCCI charcters. 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).

    Ah, true. But in the message I posted using a UTF-8 terminal, that would have been a UTF-8 encoded "degree" symbol instead of a CP437-encoded one (as would have been in the other messages, including this one).

    Norco, CA WX: 42.0F, 79.0% humidity, 0 mph NE wind, 0.15 inches rain/24hrs

    Considering that the CHRS kludge applies to the entire message, I think it is more logical to look at the entire message including header, footer en origin lines to determine the encoding.

    Synchronet does exactly that.
    --
    digital man (rob)

    This Is Spinal Tap quote #15:
    Review on "Shark Sandwich", merely a two word review: "Shit Sandwich".
    Norco, CA WX: 56.8F, 59.0% humidity, 7 mph SSE wind, 0.02 inches rain/24hrs --- SBBSecho 3.20-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Michiel van der Vlist@2:280/5555 to Rob Swindell on Sat Mar 4 11:00:48 2023
    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).

    Ah, true. But in the message I posted using a UTF-8 terminal, that
    would have been a UTF-8 encoded "degree" symbol instead of a
    CP437-encoded one (as would have been in the other messages, including 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?

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

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

    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?

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

    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.

    Considering that the CHRS kludge applies to the entire message, I
    think it is more logical to look at the entire message including
    header, footer en origin lines to determine the encoding.

    Synchronet does exactly that.

    OK. :-)


    Cheers, Michiel

    --- GoldED+/W32-MSVC 1.1.5-b20170303
    * Origin: Nieuw Schnøørd (2:280/5555)
  • From Rob Swindell@1:103/705 to Michiel van der Vlist on Sat Mar 4 13:11:48 2023
    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).

    Ah, true. But in the message I posted using a UTF-8 terminal, that would have been a UTF-8 encoded "degree" symbol instead of a CP437-encoded one (as would have been in the other messages, including 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.

    Norco, CA WX: 42.0F, 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.8F, 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)
  • From Michiel van der Vlist@2:280/5555 to Rob Swindell on Sun Mar 5 14:01:12 2023
    Hello Rob,

    On Saturday March 04 2023 13:11, you wrote to me:

    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.

    I see... So it is the terminal - or whatever functions as its equivalent - and only the terminal that determines the encoding of the message at hand.

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

    I think this question is making false assumptions.

    It is making assumtions, but they are not false I would say. Read on.. I will come back to that further down.

    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.

    Hmmm... That leaves out a big part of Fidonet. These days the majority, maybe the vast majority is writen in a language that uses the Cyrillic alfabet and the encoding is CP866.

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

    Yes.

    OK, so far so good...

    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.

    And now I come back to my previous question: what happens if it does not fit into CP437? That can easely happen. A Euro sign '€' can be composed in UTF-8 but it does not fit into CP437.

    My software translates the CP437 encoded degree sign into UTF-8 as
    you can see.

    Yup, most software does the same, when appropriate.

    My Golded does, but the reverse is a bit problematic.


    Cheers, Michiel

    --- GoldED+/W32-MSVC 1.1.5-b20170303
    * Origin: Nieuw Schnøørd (2:280/5555)
  • From Rob Swindell@1:103/705 to Michiel van der Vlist on Sun Mar 5 11:40:06 2023
    Re: codepage
    By: Michiel van der Vlist to Rob Swindell on Sun Mar 05 2023 02:01 pm

    Hello Rob,

    On Saturday March 04 2023 13:11, you wrote to me:

    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.

    I see... So it is the terminal - or whatever functions as its equivalent - and only the terminal that determines the encoding of the message at hand.

    Or rather, the message content created with that terminal. If the content is just plain ASCII, regardless of the terminal that created it, then the message will fly the ASCII charset flag. In Synchronet, a CP437 terminal cannot be used to created UTF-8 content, so messages created by such a terminal will either be ASCII or CP437 encoded.

    It is making assumtions, but they are not false I would say. Read on.. I will come back to that further down.

    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.

    Hmmm... That leaves out a big part of Fidonet. These days the majority, maybe the vast majority is writen in a language that uses the Cyrillic alfabet and the encoding is CP866.

    True, that's the state of things.

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

    Yes.

    OK, so far so good...

    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.

    And now I come back to my previous question: what happens if it does not fit into CP437? That can easely happen. A Euro sign '' can be composed in UTF-8 but it does not fit into CP437.

    When a CP437 terminal user quotes a UTF-8 message that contains untranslatable UNICODE codepoints without a CP437 equivalent, they're translated to character that indiciates it was untranslatable. By default, that character is the upside down question mark.
    --
    digital man (rob)

    Sling Blade quote #14:
    Karl Childers: Some folks call it a sling blade, I call it a kaiser blade. Norco, CA WX: 51.1F, 73.0% humidity, 4 mph E wind, 0.00 inches rain/24hrs
    --- SBBSecho 3.20-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Michiel van der Vlist@2:280/5555 to Rob Swindell on Mon Mar 6 21:41:15 2023
    Hello Rob,

    On Sunday March 05 2023 11:40, you wrote to me:

    I see... So it is the terminal - or whatever functions as its
    equivalent - and only the terminal that determines the encoding of the
    message at hand.

    Or rather, the message content created with that terminal. If the
    content is just plain ASCII, regardless of the terminal that created
    it, then the message will fly the ASCII charset flag. In Synchronet, a CP437 terminal cannot be used to created UTF-8 content, so messages created by such a terminal will either be ASCII or CP437 encoded.

    Understood.

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

    Hmmm... That leaves out a big part of Fidonet. These days the
    majority, maybe the vast majority is writen in a language that uses
    the Cyrillic alfabet and the encoding is CP866.

    True, that's the state of things.

    Well, at least those needing more that CP437 can use UTF-8.

    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.

    And now I come back to my previous question: what happens if it
    does not fit into CP437? That can easely happen. A Euro sign '¿'
    can be composed in UTF-8 but it does not fit into CP437.

    I see that the EURO sign is translated into an inverted question mark.

    When a CP437 terminal user quotes a UTF-8 message that contains untranslatable UNICODE codepoints without a CP437 equivalent, they're translated to character that indiciates it was untranslatable. By
    default, that character is the upside down question mark.

    Check.

    Next question: Can Synchonet deal with a UTF-8 encoded nodelist?

    Here is where to find one: http://www.vlist.eu/downloads/fidolist/z2daily.065



    Cheers, Michiel

    --- GoldED+/W32-MSVC 1.1.5-b20170303
    * Origin: Nieuw Schnøørd (2:280/5555)
  • From Rob Swindell@1:103/705 to Michiel van der Vlist on Mon Mar 6 16:58:55 2023
    Re: codepage
    By: Michiel van der Vlist to Rob Swindell on Mon Mar 06 2023 09:41 pm

    Next question: Can Synchonet deal with a UTF-8 encoded nodelist?

    Synchronet does use an FTN nodelist. There are some optional scripts that can make use of a nodelist (e.g. to look up a particular sysop name/address), but I don't use them personally.
    --
    digital man (rob)

    Synchronet/BBS Terminology Definition #93:
    XPDEV = Cross-platform Development
    Norco, CA WX: 54.0F, 57.0% humidity, 5 mph SSE wind, 0.00 inches rain/24hrs --- SBBSecho 3.20-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Michiel van der Vlist@2:280/5555 to Rob Swindell on Tue Mar 7 10:26:01 2023
    Hello Rob,

    On Monday March 06 2023 16:58, you wrote to me:

    Next question: Can Synchonet deal with a UTF-8 encoded nodelist?

    Synchronet does use an FTN nodelist. There are some optional scripts
    that can make use of a nodelist (e.g. to look up a particular sysop name/address), but I don't use them personally.

    Ok, thanks for the feedback.


    Cheers, Michiel

    --- GoldED+/W32-MSVC 1.1.5-b20170303
    * Origin: Nieuw Schnøørd (2:280/5555)
  • From Rob Swindell@1:103/705 to Michiel van der Vlist on Tue Mar 7 11:13:13 2023
    Re: codepage
    By: Michiel van der Vlist to Rob Swindell on Tue Mar 07 2023 10:26 am

    Hello Rob,

    On Monday March 06 2023 16:58, you wrote to me:

    Next question: Can Synchonet deal with a UTF-8 encoded nodelist?

    Synchronet does use an FTN nodelist. There are some optional scripts that can make use of a nodelist (e.g. to look up a particular sysop name/address), but I don't use them personally.

    Ok, thanks for the feedback.

    I mean to say/write "Synchronet (and SBBSecho) does/do *not* use an FTN nodelist".

    As for the Synchronet related scripts that can make use of an FTN nodelist, I don't presently know how they'd handle UTF-8 content in them.
    --
    digital man (rob)

    Synchronet "Real Fact" #101:
    Avatars were added to Synchronet (backward compatible w/v3.16) in January 2018 Norco, CA WX: 54.6F, 55.0% humidity, 2 mph WNW wind, 0.00 inches rain/24hrs --- SBBSecho 3.20-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)