• FTSC

    From Karel Kral@2:423/39 to All on Wednesday, September 30, 2026 19:21:24
    Hello All!

    Just theoretically: is it hard to get FTSC updated? (5003.001)

    Checking process, probably need FSP(?) But maybe review is OK?

    Karel

    --- GoldED+/LNX 1.1.5-b20240209
    * Origin: Plast DATA (2:423/39)
  • From Rob Swindell@1:103/705 to Karel Kral on Wednesday, September 30, 2026 13:16:02
    Re: FTSC
    By: Karel Kral to All on Wed Sep 30 2026 07:21 pm

    Hello All!

    Just theoretically: is it hard to get FTSC updated? (5003.001)

    5003.001 is a document (a FidoNet Technical Standard, or FTS). The FTSC is an "organization" (a very small one)

    Checking process, probably need FSP(?) But maybe review is OK?

    The process is documented here:
    http://ftsc.org/docs/fta-1002.003

    If you still have questions, let us know!
    --
    Rob Swindell
    FTSC Standing Member
    --- SBBSecho 3.38-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Maurice Kinal@2:280/464.113 to Karel Kral on Wednesday, September 30, 2026 20:28:03
    Hej Karel!

    is it hard to get FTSC updated? (5003.001)

    What is there to update? Is there more up-to-date bullshit available?

    Het leven is goed,
    Maurice

    o- -o -o o- o- o- o- o- -o o- -o o- -o o- o- o-
    /) (\ (\ /) /) /) /) /) (\ /) (\ /) (\ /) /) /)
    ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^
    ... Ongiet georne hwæt sy god oþþe yfel, ond toscead simle.
    Keenly perceive what is good or evil, and always distinguish them.
    --- GNU bash, version 5.3.15(1)-release (x86_64-pc-linux-gnu)
    * Origin: Little Mikey's EuroPoint @ (2:280/464.113)
  • From Tim Schattkowsky@2:2/29 to Michiel van der Vlist on Wednesday, October 07, 2026 15:07:55
    //Hello Michiel,//

    on *02.10.26* at *8:00:08* You wrote in Area *FTSC_PUBLIC*
    to *Karel Kral* about *"FTSC"*.

    CP895 Unofficial codepage 895 (DOS KEYBCS2)
    MvdV> One of the requirements for promoting a proposal to a standard is
    MvdV> "widespread use". While this may be a bit vague, you may have some
    MvdV> difficulty convincing the FTSC that CP895 is indeed in "widespread
    MvdV> use".

    Well at least it is fully supported in WinPoint (and tested AFAIR). Still I am not totally sure this counts as widespread use ;)

    Regards,
    Tim

    --- WinPoint 419.0
    * Origin: Original WinPoint Origin! (2:2/29)
  • From Karel Kral@2:423/39 to Rob Swindell on Thursday, October 01, 2026 06:39:08
    Hello Rob!

    30 Sep 26 13:16, you wrote to me:

    The process is documented here:
    http://ftsc.org/docs/fta-1002.003

    Of course, I have read the text. My question was specifically regarding the review process that takes place every two years. Am I correct in understanding that the process is the same as for an initial request?

    Karel

    --- GoldED+/LNX 1.1.5-b20240209
    * Origin: Plast DATA (2:423/39)
  • From Karel Kral@2:423/39 to Maurice Kinal on Thursday, October 01, 2026 06:39:46
    Hello Maurice!

    30 Sep 26 20:28, you wrote to me:

    What is there to update? Is there more up-to-date bullshit available?

    In 2012 we (r42) missed to participate (looks like) on that FTS. Of course, correct is to folow... I just wanted to have all inputs.

    Karel

    --- GoldED+/LNX 1.1.5-b20240209
    * Origin: Plast DATA (2:423/39)
  • From Maurice Kinal@2:280/464.113 to Karel Kral on Thursday, October 01, 2026 11:21:21
    Hej Karel!

    In 2012 we (r42) missed to participate (looks like) on that FTS.

    From my perspective it came out of the blue as well.

    I just wanted to have all inputs.

    Best of luck with that. I have yet to see anyone, responsible or otherwise, defend that particular document.

    Het leven is goed,
    Maurice

    o- -o -o -o -o o- o- -o o- o- o- o- o- -o o- -o
    /) (\ (\ (\ (\ /) /) (\ /) /) /) /) /) (\ /) (\
    ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^
    ... Fus sceal feran, fæge sweltan.
    Those who are ready must go, the doomed die.
    --- GNU bash, version 5.3.15(1)-release (x86_64-pc-linux-gnu)
    * Origin: Little Mikey's EuroPoint @ (2:280/464.113)
  • From Rob Swindell@1:103/705 to Karel Kral on Thursday, October 01, 2026 13:12:59
    Re: Re: FTSC
    By: Karel Kral to Rob Swindell on Thu Oct 01 2026 06:39 am

    Hello Rob!

    30 Sep 26 13:16, you wrote to me:

    The process is documented here:
    http://ftsc.org/docs/fta-1002.003

    Of course, I have read the text. My question was specifically regarding the review process that takes place every two years. Am I correct in understanding that the process is the same as for an initial request?

    Initial request of what? I'm not clear what you're saying. Anyway, if you have revisions to make, post the updated doc here and we'll have a look-see and hopefully publish it... someday. :-)
    --
    Rob Swindell
    FTSC Standing Member
    --- SBBSecho 3.38-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Maurice Kinal@1:153/7001 to Tim Schattkowsky on Thursday, October 08, 2026 01:15:46
    Hey Tim!

    <Esc>:read !trans -b -no-ansi -t Čeština "I\'ve got squirrels in my pants\!" V kalhotách mám veverky!

    It works without adding any additional bullshit and is universal. Also it doesn't screw up the Anglo-Saxon text tagline below which so-called CP895 would ... if it was real that is. DOS-think at it's finest.

    Well at least it is fully supported in WinPoint (and tested AFAIR).

    I for one would like to see the evidence.

    Life is good,
    Maurice

    o- -o o- -o -o -o -o -o -o -o -o o-
    /) (\ /) (\ (\ (\ (\ (\ (\ (\ (\ /)
    ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^
    ... Wræd sceal wunden, wracu heardum men.
    A wound must have a bandage, an unyielding man must have revenge.
    --- GNU bash, version 5.3.15(1)-release (x86_64-pc-linux-gnu)
    * Origin: Little Mikey's Brain - Ladysmith BC, Canada (1:153/7001)
  • From Andrew Leary@1:320/219 to Karel Kral on Thursday, October 08, 2026 00:44:22
    Hello Karel!

    30 Sep 26 19:21, you wrote to all:

    Just theoretically: is it hard to get FTSC updated? (5003.001)

    Checking process, probably need FSP(?) But maybe review is OK?

    You can send a proposal in this echo, or send it to me via NetMail. What is it you're thinking needs to be updated in FTS-5003?

    Andrew

    ---
    * Origin: From the Desk of the FTSC Administrator (1:320/219)
  • From Karel Kral@2:423/39 to Andrew Leary on Thursday, October 08, 2026 11:28:55
    Hello Andrew!

    08 Oct 26 00:44, you wrote to me:

    You can send a proposal in this echo, or send it to me via NetMail.
    What is it you're thinking needs to be updated in FTS-5003?

    I wrote diff there already.

    Basically is about to add one line:

    CP895 Unofficial codepage 895 (DOS KEYBCS2)

    I will send Att via Netmail to you.

    Karel

    --- GoldED+/LNX 1.1.5-b20240209
    * Origin: Plast DATA (2:423/39)
  • From Karel Kral@2:423/39 to Rob Swindell on Friday, October 02, 2026 08:55:07
    Hello Rob!

    01 Oct 26 13:12, you wrote to me:

    you have revisions to make, post the updated doc here and we'll have a look-see and hopefully publish it... someday. :-)

    Is easy:

    [fido]$ diff fts-5003.001 fts-5003.002
    7c7
    < Revision: 1
    -+-
    Revision: 2
    12c12,13
    < Date: 7 April 2012
    -+-
    Karel Kral
    Date: 2 October 2026
    215a217
    CP895 Unofficial codepage 895 (DOS KEYBCS2)
    291a294
    Karel Kral Fidonet: 2:42/0
    310a314
    Rev.2, 20261002: Added support for Region 2:42

    Karel

    --- GoldED+/LNX 1.1.5-b20240209
    * Origin: Plast DATA (2:423/39)
  • From Michiel van der Vlist@2:280/5555 to Karel Kral on Friday, October 02, 2026 10:00:08
    Hello Karel,

    On 02 Oct 26 08:55, you wrote to Rob Swindell:

    Is easy:

    [fido]$ diff fts-5003.001 fts-5003.002
    7c7
    < Revision: 1
    -+-
    Revision: 2
    12c12,13
    < Date: 7 April 2012
    -+-
    Karel Kral
    Date: 2 October 2026
    215a217
    CP895 Unofficial codepage 895 (DOS KEYBCS2)

    One of the requirements for promoting a proposal to a standard is "widespread use". While this may be a bit vague, you may have some difficulty convincing the FTSC that CP895 is indeed in "widespread use".

    But even if you succeed, I doubt it will make any difference in practice. CP895 is indeed "unofficial". It was never recognised by IBM as such, there appear to be at least two versions, the Japanese and the Kamenicky version. None of my versions of Windows that I have in use here accept it as a vaild code page.

    Add to that that in the world outside Fidonet the whole code page circus is a finished race. For all intents and purposes the transition to Unicode is history. Except for a few niches, like Fidonet. No one is going to invest time and energy to update transition tools line iconv to include CP895. Or install such updates.

    Nevertheless, good luck! ;-)


    Cheers, Michiel

    --- GoldED+/W32-MINGW 2.0.0-b20260917
    * Origin: Nieuw Schnøørd (2:280/5555)
  • From Tim Schattkowsky@2:2/29 to Maurice Kinal on Monday, November 09, 2026 16:16:01
    //Hello Maurice,//

    on *08.10.26* at *1:15:46* You wrote in Area *FTSC_PUBLIC*
    to *Tim Schattkowsky* about *"FTSC"*.

    Hey Tim!

    <Esc>:read !trans -b -no-ansi -t Čeština "I\'ve got squirrels in my pants\!"
    V kalhotách mám veverky!

    It works without adding any additional bullshit and is universal. Also
    it doesn't screw up the Anglo-Saxon text tagline below which so-called CP895 would ... if it was real that is. DOS-think at it's finest.

    Well at least it is fully supported in WinPoint (and tested AFAIR).

    I for one would like to see the evidence.

    Life is good,
    Maurice

    o- -o o- -o -o -o -o -o -o -o -o o-
    /) (\ /) (\ (\ (\ (\ (\ (\ (\ (\ /) ^^ ^^ ^^ ^^ ^^ ^^
    ^^ ^^ ^^ ^^ ^^ ^^ ... Wræd sceal wunden, wracu heardum men.
    A wound must have a bandage, an unyielding man must have revenge.
    --- GNU bash, version 5.3.15(1)-release (x86_64-pc-linux-gnu)
    * Origin: Little Mikey's Brain - Ladysmith BC, Canada (1:153/7001)

    Regards,
    Tim

    --- WinPoint 419.0
    * Origin: Original WinPoint Origin! (2:2/29)
  • From Tim Schattkowsky@2:2/29 to Maurice Kinal on Monday, November 09, 2026 16:18:54
    //Hello Maurice,//

    on *08.10.26* at *1:15:46* You wrote in Area *FTSC_PUBLIC*
    to *Tim Schattkowsky* about *"FTSC"*.

    Comes as CP895 ...

    AREA:FTSC_PUBLIC
    @REPLY: 2:2/29 d7f75507
    @MSGID: 1:153/7001 87430585
    @CHRS: UTF-8 4
    Hey Tim!

    <Esc>:read !trans -b -no-ansi -t €e¨tina "I\'ve got squirrels in my pants\!"
    V kalhot ch m m veverky!

    It works without adding any additional bullshit and is universal. Also
    it doesn't screw up the Anglo-Saxon text tagline below which so-called CP895 would ... if it was real that is. DOS-think at it's finest.

    Well at least it is fully supported in WinPoint (and tested AFAIR).

    I for one would like to see the evidence.

    Life is good,
    Maurice

    o- -o o- -o -o -o -o -o -o -o -o o-
    /) (\ /) (\ (\ (\ (\ (\ (\ (\ (\ /) ^^ ^^ ^^ ^^ ^^ ^^
    ^^ ^^ ^^ ^^ ^^ ^^ ... Wr?d sceal wunden, wracu heardum men.
    A wound must have a bandage, an unyielding man must have revenge.
    --- GNU bash, version 5.3.15(1)-release (x86_64-pc-linux-gnu)
    * Origin: Little Mikey's Brain - Ladysmith BC, Canada (1:153/7001) SEEN-BY: 2/29 1000 103/705 104/119 121 114/10 30 124/5016 153/757
    SEEN-BY: 153/7001 154/10 30 50 700 203/0 220/15 90 221/0 1 6 226/18 SEEN-BY: 226/20 44 50 229/310 426 240/1120 5832 263/1 280/464 1043 SEEN-BY: 280/5003 5006 5555 292/789 854 8125 301/1 310/31 320/219
    SEEN-BY: 335/364 341/66 234 396/45 400/2992 410/9 421/79 790 423/120 SEEN-BY: 460/58 463/68 633/280 712/848 770/1 2320/105 3634/12 5020/545 SEEN-BY: 5020/715 1042 5030/1997 5060/900
    @PATH: 153/7001 154/10 280/464 292/854

    Regards,
    Tim

    --- WinPoint 419.0
    * Origin: Original WinPoint Origin! (2:2/29)
  • From Dan Clough@1:135/115 to Tim Schattkowsky on Monday, November 09, 2026 11:18:09
    Tim Schattkowsky wrote to Maurice Kinal <=-

    //Hello Maurice,//

    on *08.10.26* at *1:15:46* You wrote in Area *FTSC_PUBLIC*
    to *Tim Schattkowsky* about *"FTSC"*.

    Comes as CP895 ...

    AREA:FTSC_PUBLIC
    @REPLY: 2:2/29 d7f75507
    @MSGID: 1:153/7001 87430585
    @CHRS: UTF-8 4
    Hey Tim!

    <Esc>:read !trans -b -no-ansi -t €e¨tina "I\'ve got squirrels in my pants\!"
    V kalhot ch m m veverky!

    It works without adding any additional bullshit and is universal. Also
    it doesn't screw up the Anglo-Saxon text tagline below which so-called CP895 would ... if it was real that is. DOS-think at it's finest.

    Well at least it is fully supported in WinPoint (and tested AFAIR).

    I for one would like to see the evidence.

    Life is good,
    Maurice

    o- -o o- -o -o -o -o -o -o -o -o o-
    /) (\ /) (\ (\ (\ (\ (\ (\ (\ (\ /) ^^ ^^ ^^ ^^ ^^ ^^
    ^^ ^^ ^^ ^^ ^^ ^^ ... Wr?d sceal wunden, wracu heardum men.
    A wound must have a bandage, an unyielding man must have revenge.
    --- GNU bash, version 5.3.15(1)-release (x86_64-pc-linux-gnu)
    * Origin: Little Mikey's Brain - Ladysmith BC, Canada (1:153/7001) SEEN-BY: 2/29 1000 103/705 104/119 121 114/10 30 124/5016 153/757
    SEEN-BY: 153/7001 154/10 30 50 700 203/0 220/15 90 221/0 1 6 226/18 SEEN-BY: 226/20 44 50 229/310 426 240/1120 5832 263/1 280/464 1043 SEEN-BY: 280/5003 5006 5555 292/789 854 8125 301/1 310/31 320/219
    SEEN-BY: 335/364 341/66 234 396/45 400/2992 410/9 421/79 790 423/120 SEEN-BY: 460/58 463/68 633/280 712/848 770/1 2320/105 3634/12 5020/545 SEEN-BY: 5020/715 1042 5030/1997 5060/900
    @PATH: 153/7001 154/10 280/464 292/854

    Regards,
    Tim

    --- WinPoint 419.0
    * Origin: Original WinPoint Origin! (2:2/29)

    This is an invalid FidoNet node number. Should be a "Pvt" node.

    Why are you, as an FTSC member, not doing something about that?



    ... He does the work of 3 Men...Moe, Larry & Curly
    === MultiMail/Linux v0.52
    --- SBBSecho 3.38-Linux
    * Origin: Palantir * palantirbbs.ddns.net * Pensacola, FL * (1:135/115)
  • From Maurice Kinal@1:153/7001 to Tim Schattkowsky on Monday, November 09, 2026 16:48:35
    Hey Tim!

    Comes as CP895 ...

    Probably. At this point in time 'iconv -f cp895' claims that cp895 is not supported. I noted that "MSGID: 2:2/29 ee68e987" is flying the utf-8 flag and, other than the screwed up penguin quote, it looks perfect. As for "MSGID: 2:2/29 ee68e98f" I'd require a proper encoding table to check it against. How exactly did you accomplish the conversion from utf-8 to cp895? I noted that you only had issues with the 'æ' character in the Anglo-Saxon part. Looking at the tagline below I am guessing 'ð' would also be a problem for cp895.

    Life is good,
    Maurice

    -o o- o- -o -o -o o- o- o- o- -o -o
    (\ /) /) (\ (\ (\ /) /) /) /) (\ (\
    ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^
    ... Domgeorne dreorigne oft in hyra breostcofan bindað fæste.
    Those eager for glory often bind sorrowful thoughts fast within the heart. --- GNU bash, version 5.3.20(1)-release (x86_64-pc-linux-gnu)
    * Origin: Little Mikey's Brain - Ladysmith BC, Canada (1:153/7001)
  • From Karel Kral@2:423/39 to Maurice Kinal on Monday, November 09, 2026 19:12:08
    Hello Maurice!

    09 Nov 26 16:48, you wrote to Tim Schattkowsky:

    encoding table to check it against. How exactly did you accomplish
    the conversion from utf-8 to cp895? I noted that you only had issues
    with the '??' character in the Anglo-Saxon part. Looking at the
    tagline below I am guessing '??' would also be a problem for cp895.

    Just to complete: I started to write own cp895.h for iconv (nearly finished)

    Idea behind was: to take 852 895 CHS conversion table from Golded (I have) and patch cp852.h from iconv - to get easily created cp895.h ;-)

    Karel

    --- GoldED+/LNX 1.1.5-b20240209
    * Origin: Plast DATA (2:423/39)
  • From Maurice Kinal@1:153/7001 to Karel Kral on Monday, November 09, 2026 20:34:19
    Hey Karel!

    I started to write own cp895.h for iconv (nearly finished)

    Sure but I'd still have reservations as to the legitimacy of such a thing. What does IBM think cp895 is? I believe it is one of their codepages and has nothing to do with Čeština. Also I note that iana, as well as glibc, isn't going out on a limb over that particular codepage no matter what language it supports.

    take 852 895 CHS conversion table from Golded (I have)

    That in itself offers nothing as to credibility.

    Life is good,
    Maurice

    o- o- o- -o -o o- o- o- -o -o o- -o
    /) /) /) (\ (\ /) /) /) (\ (\ /) (\
    ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^
    ... I've got squirrels in my pants!
    --- GNU bash, version 5.3.20(1)-release (x86_64-pc-linux-gnu)
    * Origin: Little Mikey's Brain - Ladysmith BC, Canada (1:153/7001)
  • From Karel Kral@2:423/39 to Maurice Kinal on Tuesday, November 10, 2026 09:53:01
    Hello Maurice!

    09 Nov 26 20:34, you wrote to me:

    Sure but I'd still have reservations as to the legitimacy of such a
    thing. What does IBM think cp895 is? I believe it is one of their codepages and has nothing to do with ??e??tina. Also I note that

    That in itself offers nothing as to credibility.

    As I maybe said, we have 91 conferences in r42 (ok, traffic is debatable). 4x allow only 7bit, 2 allow cp852 or cp895, 72 allow only cp895 and 13 does not say. The only thing I wanted here was to move cp895 from "not allowed" in fidonet - to "is used in named conferences and is tolerated".

    Karel

    --- GoldED+/LNX 1.1.5-b20240209
    * Origin: Plast DATA (2:423/39)
  • From Michiel van der Vlist@2:280/5555 to Karel Kral on Tuesday, November 10, 2026 13:50:06
    Hello Karel,

    On 10 Nov 26 09:53, you wrote to Maurice Kinal:

    As I maybe said, we have 91 conferences in r42 (ok, traffic is
    debatable).

    91 conferences for 11 sysops? Under those conditions the number of conferences is totally meaningless.

    Here in R28 (13 sysops) we dropped all echos except one. Just one echo for all and everything. Works for us.

    4x allow only 7bit, 2 allow cp852 or cp895, 72 allow only
    cp895 and 13 does not say.

    Those numbers are totally meaningless. The only meaningfull number is: "how many of those 11 sysops are stuck with CP895 and are unable to change to something else?". Area rules do not come from God. Just change the CP895 only rule for those 72 echos. Or drop those 72 echos.

    The only thing I wanted here was to move cp895 from "not allowed" in fidonet - to "is used in named conferences and is tolerated".

    In practise it will make no difference. The FTSC does not "forbid" the use of other encodings than the ones listed in the standard. They are just not documented as a standard which neans that if you use it, you are on your own. That CP895 is used in R42 has been tolerated for decades and that will not change. The rest of Fidonet will not use CP895 and that will not change either.

    Cheers, Michiel

    --- GoldED+/W32-MINGW 2.0.0-b20260928
    * Origin: Nieuw Schnøørd (2:280/5555)
  • From Ward Dossche@2:292/854 to Karel Kral on Tuesday, November 10, 2026 14:23:33
    Karel,

    As I maybe said, we have 91 conferences in r42 (ok, traffic is
    debatable).

    I take it that is an understatement?

    \%/@rd

    --- DB4 - 20261031
    * Origin: Many Glacier - Preserve / Protect / Conserve (2:292/854)
  • From Maurice Kinal@1:153/7001 to Karel Kral on Tuesday, November 10, 2026 14:06:46
    Hey Karel!

    The only thing I wanted here was to move cp895 from "not allowed" in
    fidonet - to "is used in named conferences and is tolerated".

    Why? If it is already working for those needing it why rock the compatibilty boat? ... especially considering fts-5003.001 is total bullshit.

    Just curious, are those concerned using the cp895 deploying the kódování Kamenických? I've seen a character map for that. However in the associated documentation it says, "Some ambiguity exists in the official code page assignment for the Kamenický encoding".

    Gotta love controversy. :-)

    Life is good,
    Maurice

    -o -o -o -o o- o- -o -o -o o- o- o-
    (\ (\ (\ (\ /) /) (\ (\ (\ /) /) /)
    ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^
    ... Sceal þegna gehwilc geþylde nimon.
    Every man must acquire patience.
    --- GNU bash, version 5.3.20(1)-release (x86_64-pc-linux-gnu)
    * Origin: Little Mikey's Brain - Ladysmith BC, Canada (1:153/7001)
  • From Karel Kral@2:423/39 to Michiel van der Vlist on Tuesday, November 10, 2026 19:34:37
    Hello Michiel!

    10 Nov 26 13:50, you wrote to me:

    Those numbers are totally meaningless. The only meaningfull number is: "how many of those 11 sysops are stuck with CP895 and are unable to
    change to something else?". Area rules do not come from God. Just

    We tested 3 of us to use UTF. Somebody is thinking about that. And some people simply can not (e.g. OS/2 etc)


    are on your own. That CP895 is used in R42 has been tolerated for
    decades and that will not change. The rest of Fidonet will not use
    CP895 and that will not change either.

    OK then. I will print that message.

    Karel

    --- GoldED+/LNX 1.1.5-b20240209
    * Origin: Plast DATA (2:423/39)
  • From Michiel van der Vlist@2:280/5555 to Karel Kral on Tuesday, November 10, 2026 21:41:42
    Hello Karel,

    On 10 Nov 26 19:34, you wrote to me:

    We tested 3 of us to use UTF. Somebody is thinking about that. And
    some people simply can not (e.g. OS/2 etc)

    Ouch, I didn't realize OS/2 does not support UTF-8. OS/2 was a fantastic OS. "Was", past tense. I have used it with pleasure a couple of decades ago. I dropped it when I could not make it talk with Novell netware. Now it is a dead end street. It is no longer developed. No Ipv6 and no UTF-8. :(

    That CP895 is used in R42 has been tolerated for decades and that
    will not change. The rest of Fidonet will not use CP895 and that will
    not change either.

    OK then. I will print that message.

    OK...


    Cheers, Michiel

    --- GoldED+/W32-MINGW 2.0.0-b20260928
    * Origin: Nieuw Schnøørd (2:280/5555)
  • From Michiel van der Vlist@2:280/5555 to Maurice Kinal on Tuesday, November 10, 2026 21:47:37
    Hello Maurice,

    On 10 Nov 26 14:06, you wrote to Karel Kral:

    The only thing I wanted here was to move cp895 from "not allowed" in
    fidonet - to "is used in named conferences and is tolerated".

    Why? If it is already working for those needing it why rock the compatibilty boat?

    Why indeed. My not so humble opinion is that instead of puting time an effort into more of the same, we should move into the direction of getting away from that codepage shit. Over the years I have put quit some time and effort into making the codepages work. I wrote translation tables for Golded with varying milage. But I am happy to call that history. In fact I already have with the coming of the Unicode version of Golded. I have removed all reference to the translation tabels in the new Golded's config. I no longer need them. UTF-8 it is. :-)

    ... especially considering fts-5003.001 is total bullshit.

    Here I disagree. FTS-5003 has been of use to the Fidonet community. But as I said, I will happily leave all that behind and move on...


    Cheers, Michiel

    --- GoldED+/W32-MINGW 2.0.0-b20260928
    * Origin: Nieuw Schnøørd (2:280/5555)
  • From Maurice Kinal@1:153/7001 to Michiel van der Vlist on Tuesday, November 10, 2026 21:52:09
    Hey Michiel!

    we should move into the direction of getting away from that codepage
    shit.

    If it were only that easy. I am sure there would be much grief from the CP437 crowd. Speaking for myself, it matters not as long as the 8 bit codes are actually what they say they are and not simply some ill advised nonexistent codepage without any reference map/table so that a proper critique could be advanced by someone who actually cares about standards and is prepared to defend them with credible references, such as IANA in the case of codepages.

    FTS-5003 has been of use to the Fidonet community.

    I fail to see how. I believe any usefulness to be found in the Fidonet community is in spite of FTS-5003. :-)

    Life is good,
    Maurice

    o- -o -o o- -o -o o- -o -o o- o- -o
    /) (\ (\ /) (\ (\ /) (\ (\ /) /) (\
    ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^
    ... Gemyne mærþo, mægenellen cyð, waca wið wraþum.
    Think of glory, show great courage, keep watch against the foe.
    --- GNU bash, version 5.3.20(1)-release (x86_64-pc-linux-gnu)
    * Origin: Little Mikey's Brain - Ladysmith BC, Canada (1:153/7001)
  • From Yegor Gluhov@2:382/736 to Maurice Kinal on Wednesday, November 11, 2026 08:43:43
    Hello Maurice!

    10 Nov 26 21:52, you wrote to Michiel van der Vlist:

    we should move into the direction of getting away from that codepage shit.
    If it were only that easy. I am sure there would be much grief from the CP437 crowd.

    There's already some grief from the CP866 crowd claiming that splitting Fidonet into UTF-8 and non-UTF-8 parts will kill (what remains of) the network. Frankly, plenty of sysops won't ever bother to upgrade, no matter what new software gets released or what the FTSC decides.

    Yegor

    --- AmberEdit/linux 0.11.0
    * Origin: to err is human, but to really f.. things up you need AI (2:382/736)
  • From Michiel van der Vlist@2:280/5555 to Maurice Kinal on Wednesday, November 11, 2026 09:30:49
    Hello Maurice,

    On 10 Nov 26 21:52, you wrote to me:

    we should move into the direction of getting away from that codepage
    shit.

    If it were only that easy.

    I never said it would be easy. But with the coming of UTF capable Fidonet readers, it has become less difficult. The new Golded is a breakthrough I say. Not to forget FidoMail which is also 100% UTF compatible.

    I am sure there would be much grief from the CP437 crowd.

    Not my problem. The CP437 is a relatively small minority anyway these days. CP850 has been the default for Windows version distributed in Western Europe. CP866 and some others in many eastern parts of Euope.

    Speaking for myself, it matters not as long as the 8 bit codes are actually what they say they are

    The problem in this part of the world is that there are so many languages in use with different character sets. There is no 8 bit encoding schema that covers all those languages. 256 characters just aren't enough. The rest of the Internet has solved this problem long ago by adopting unicode. 8 bit encoding can still be found in the museum we call Fidonet.

    and not simply some ill advised nonexistent codepage without any
    reference map/table so that a proper critique could be advanced by
    someone who actually cares about standards and is prepared to defend
    them with credible references, such as IANA in the case of codepages.

    FTS-5003 has been of use to the Fidonet community.

    I fail to see how. I believe any usefulness to be found in the
    Fidonet community is in spite of FTS-5003. :-)

    No problem. One can not please everyone all of the time. If FTS-5003 has been usefull to some - and it has - then the effort was no wasted.


    Cheers, Michiel

    --- GoldED+/W32-MINGW 2.0.0-b20260928
    * Origin: Nieuw Schnøørd (2:280/5555)
  • From Michiel van der Vlist@2:280/5555 to Yegor Gluhov on Wednesday, November 11, 2026 09:47:09
    Hello Yegor,

    On 11 Nov 26 08:43, you wrote to Maurice Kinal:

    we should move into the direction of getting away from that
    codepage shit.

    If it were only that easy. I am sure there would be much grief
    from the CP437 crowd.

    There's already some grief from the CP866 crowd claiming that
    splitting Fidonet into UTF-8 and non-UTF-8 parts will kill (what
    remains of) the network.

    The CP866 crowd has always been more or less isolated from those that use latin based alfabets. I don't see how UTF-8 will make much difference. There is always the fall back to pure ASCII. Which was the official Fidonet standard from the very beginning. Introducing ohter eccodings beyond ASCII did not kill Fidonet either.

    Frankly, plenty of sysops won't ever bother to upgrade, no matter what
    new software gets released

    Yes, and some will hang on to dead end streets like OS/2 to the bitter end. That won't stop the rest. And it won't kill Fidonet.

    or what the FTSC decides.

    The FTSC does not "decide". It just documents "current practise". Whatever that means...


    Cheers, Michiel

    --- GoldED+/W32-MINGW 2.0.0-b20260928
    * Origin: Nieuw Schnøørd (2:280/5555)
  • From Ward Dossche@2:292/854 to Yegor Gluhov on Wednesday, November 11, 2026 10:48:26
    There's already some grief from the CP866 crowd claiming that splitting Fidonet into UTF-8 and non-UTF-8 parts will kill (what remains of) the network.

    Nothing is being split.

    There is just an UTF8-type nodelist because it is an interesting project to have one's name being written in one's language. The functionality of the nodelist is not touched.

    \%/@rd

    --- DB4 - 20261031
    * Origin: Many Glacier - Preserve / Protect / Conserve (2:292/854)
  • From Alexey Fayans@2:5030/1997 to Michiel van der Vlist on Wednesday, November 11, 2026 12:53:40
    Hello Michiel!

    On Wed, 11 Nov 2026 09:47 +0100, you wrote to Yegor Gluhov:

    The CP866 crowd has always been more or less isolated from those that
    use latin based alfabets. I don't see how UTF-8 will make much
    difference.

    Most stone age software cannot display UTF-8. For latin text it doesn't matter, but cyrillic text in UTF-8 cannot be displayed on regular terminals and most old school BBSes. Even classic GoldED+ cannot display it, even through its xlat system. Only the recent AI rewrite can handle it.

    If/when people will start writing messages in UTF-8, a lot of software will display it as garbage. That's the difference.


    ... Music Station BBS | https://bbs.bsrealm.net | telnet://bbs.bsrealm.net
    --- GoldED+/W32-MSVC 1.1.5-b20180707
    * Origin: Music Station | https://ms.bsrealm.net (2:5030/1997)
  • From Yegor Gluhov@2:382/736 to Ward Dossche on Wednesday, November 11, 2026 11:59:06
    Hello Ward!

    11 Nov 26 10:48, you wrote to me:

    There's already some grief from the CP866 crowd claiming that splitting
    Fidonet into UTF-8 and non-UTF-8 parts will kill (what remains of) the
    network.
    Nothing is being split.

    There is just an UTF8-type nodelist because it is an interesting project to have one's name being written in one's language. The functionality of the nodelist is not touched.

    It's not about the nodelist, but about message content. If I start posting to RU.* echoes in UTF-8 Cyrillic and tell everyone "it's not my problem if you don't update your software", I'll most likely be cut off by the moderators and that's it. But if a noticeable number of people start doing the same, the subscribers will in practice be split into those who can read such messages and those who can't.

    Yegor

    --- AmberEdit/linux 0.11.0
    * Origin: to err is human, but to really f.. things up you need AI (2:382/736)
  • From Maurice Kinal@1:153/7001 to Yegor Gluhov on Wednesday, November 11, 2026 11:32:06
    Hey Yegor!

    There's already some grief from the CP866 crowd claiming that
    splitting Fidonet into UTF-8 and non-UTF-8 parts will kill (what
    remains of) the network.

    I fail to see why the split over that particular issue. From what I've witnessed over the decades is that most text messaging in Fidonet is done in ascii, including utf8 and non-utf8.

    Life is good,
    Maurice

    -o -o -o o- -o o- -o o- -o o- -o -o
    (\ (\ (\ /) (\ /) (\ /) (\ /) (\ (\
    ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^
    ... Se forholena cræft and forhyded gold ne bið ællunga ungelice.
    Concealed skill and hidden gold are not entirely unalike.
    --- GNU bash, version 5.3.20(1)-release (x86_64-pc-linux-gnu)
    * Origin: Little Mikey's Brain - Ladysmith BC, Canada (1:153/7001)
  • From Maurice Kinal@1:153/7001 to Michiel van der Vlist on Wednesday, November 11, 2026 11:44:43
    Hey Michiel!

    The CP437 is a relatively small minority anyway these days.

    Not really surprising given the lack of support for such encodings on the web. The same can be said for CP850.

    8 bit encoding can still be found in the museum we call Fidonet.

    Personally I have no problem with that. How about you?

    One can not please everyone all of the time.

    That is because you're not trying hard enough.

    Life is good,
    Maurice

    -o -o -o -o o- o- o- o- o- -o -o o-
    (\ (\ (\ (\ /) /) /) /) /) (\ (\ /)
    ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^
    ... Eall þæt mon untidlice onginþ, næfþ hit no æltæþne ende.
    Anything begun at the wrong time will never have a good end.
    --- GNU bash, version 5.3.20(1)-release (x86_64-pc-linux-gnu)
    * Origin: Little Mikey's Brain - Ladysmith BC, Canada (1:153/7001)
  • From Alexey Fayans@2:5030/1997 to Maurice Kinal on Wednesday, November 11, 2026 15:27:26
    Hello Maurice!

    On Wed, 11 Nov 2026 11:32, you wrote to Yegor Gluhov:

    I fail to see why the split over that particular issue. From what
    I've witnessed over the decades is that most text messaging in Fidonet
    is done in ascii, including utf8 and non-utf8.

    Yeah, there are no languages in the world other than English. And no countries other than USA.


    ... Music Station BBS | https://bbs.bsrealm.net | telnet://bbs.bsrealm.net
    --- GoldED+/W32-MSVC 1.1.5-b20180707
    * Origin: Music Station | https://ms.bsrealm.net (2:5030/1997)
  • From Michiel van der Vlist@2:280/5555 to Maurice Kinal on Wednesday, November 11, 2026 13:41:10
    Hello Maurice,

    On 10 Nov 26 21:52, you wrote to me:

    we should move into the direction of getting away from that codepage
    shit.

    If it were only that easy.

    I never said it would be easy. But with the coming of UTF capable Fidonet readers, it has become less difficult. The new Golded is a breakthrough I say. Not to forget FidoMail which is also 100% UTF compatible.

    I am sure there would be much grief from the CP437 crowd.

    Not my problem. The CP437 is a relatively small minority anyway these days. CP850 has been the default for MS-DOS version distributed in Western Europe. CP866 and some others in many eastern parts of Euope. CP125x for Windows and
    Latin-x for Linux. Actually it has always been a mess until the coming of unicode.

    Speaking for myself, it matters not as long as the 8 bit codes are actually what they say they are

    The problem in this part of the world is that there are so many languages in use with different character sets. There is no 8 bit encoding schema that covers all those languages. 256 characters just aren't enough. The rest of the Internet has solved this problem long ago by adopting unicode. 8 bit encoding can still be found in the museum we call Fidonet.

    and not simply some ill advised nonexistent codepage without any
    reference map/table so that a proper critique could be advanced by
    someone who actually cares about standards and is prepared to defend
    them with credible references, such as IANA in the case of codepages.

    FTS-5003 has been of use to the Fidonet community.

    I fail to see how. I believe any usefulness to be found in the
    Fidonet community is in spite of FTS-5003. :-)

    No problem. One can not please everyone all of the time. If FTS-5003 has been usefull to some - and it has - then the effort was not wasted.


    Cheers, Michiel

    --- GoldED+/W32-MINGW 2.0.0-b20260928
    * Origin: Nieuw Schnøørd (2:280/5555)
  • From Michiel van der Vlist@2:280/5555 to Maurice Kinal on Wednesday, November 11, 2026 13:41:33
    Hello Maurice,

    On 11 Nov 26 11:32, you wrote to Yegor Gluhov:

    There's already some grief from the CP866 crowd claiming that
    splitting Fidonet into UTF-8 and non-UTF-8 parts will kill (what
    remains of) the network.

    I fail to see why the split over that particular issue. From what
    I've witnessed over the decades is that most text messaging in Fidonet
    is done in ascii, including utf8 and non-utf8.

    This may come as a surprise to you bit my observation is that for the last decades most mesages in Fidonet are written in Cyrillic.


    Cheers, Michiel

    --- GoldED+/W32-MINGW 2.0.0-b20260928
    * Origin: Nieuw Schnøørd (2:280/5555)
  • From Yegor Gluhov@2:382/736 to Alexey Fayans on Wednesday, November 11, 2026 13:57:11
    Hello Alexey!

    11 Nov 26 15:27, you wrote to Maurice Kinal:

    I fail to see why the split over that particular issue. From what I've
    witnessed over the decades is that most text messaging in Fidonet is
    done in ascii, including utf8 and non-utf8.
    Yeah, there are no languages in the world other than English. And no countries other than USA.

    And, paradoxically, no cities other than Moscow aka Default City.

    Yegor

    --- AmberEdit/linux 0.11.0
    * Origin: to err is human, but to really f.. things up you need AI (2:382/736)
  • From Maurice Kinal@1:153/7001 to Alexey Fayans on Wednesday, November 11, 2026 12:56:14
    Hey Alexey!

    Yeah, there are no languages in the world other than English.

    Для меня это все греческое.

    Life is good,
    Maurice

    o- -o o- -o o- o- o- o- -o -o o- -o
    /) (\ /) (\ /) /) /) /) (\ (\ /) (\
    ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^
    ... Gewurdene wyrda, ðæt beoð ða feowere fæges rapas.
    Things which have happened: those are the four ropes of the doomed.
    --- GNU bash, version 5.3.20(1)-release (x86_64-pc-linux-gnu)
    * Origin: Little Mikey's Brain - Ladysmith BC, Canada (1:153/7001)
  • From Maurice Kinal@1:153/7001 to Michiel van der Vlist on Wednesday, November 11, 2026 13:11:26
    Hey Michiel!

    most mesages in Fidonet are written in Cyrillic.

    Probably. I don't get around that much anymore.

    Life is good,
    Maurice

    -o o- o- -o -o o- -o -o o- -o o- -o
    (\ /) /) (\ (\ /) (\ (\ /) (\ /) (\
    ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^
    ... Forbær oft ðæt þu eaðe wrecan mæge.
    Forbear often where you might easily take vengeance.
    --- GNU bash, version 5.3.20(1)-release (x86_64-pc-linux-gnu)
    * Origin: Little Mikey's Brain - Ladysmith BC, Canada (1:153/7001)
  • From Alexey Fayans@2:5030/1997 to Maurice Kinal on Wednesday, November 11, 2026 16:53:20
    Hello Maurice!

    On Wed, 11 Nov 2026 12:56, you wrote to me:

    Yeah, there are no languages in the world other than English.
    ?F?»?P ?¼?????P ??V?? ?²?B?? ?³?A???Z???B?º????.

    https://postimg.cc/sM1jbDnX

    This is how it looks in most popular Fidonet software - GoldED+. Do you see the problem now?


    ... Music Station BBS | https://bbs.bsrealm.net | telnet://bbs.bsrealm.net
    --- GoldED+/W32-MSVC 1.1.5-b20180707
    * Origin: Music Station | https://ms.bsrealm.net (2:5030/1997)
  • From Michiel van der Vlist@2:280/5555 to Alexey Fayans on Wednesday, November 11, 2026 15:45:12
    Hello Alexey,

    On 11 Nov 26 12:53, you wrote to me:

    The CP866 crowd has always been more or less isolated from those
    that use latin based alfabets. I don't see how UTF-8 will make
    much difference.

    Most stone age software cannot display UTF-8.

    I have worked with stonier software that could not even display lower case letters. MY ASR33 WAS UPPER CASE ASCII ONLY.

    For latin text it doesn't matter, but cyrillic text in UTF-8 cannot be displayed on regular terminals and most old school BBSes. Even classic GoldED+ cannot display it, even through its xlat system. Only the
    recent AI rewrite can handle it.

    That is why I switched to the new Golded unicode.

    If/when people will start writing messages in UTF-8, a lot of software will display it as garbage. That's the difference.

    My Fidonet system could never Properly display Cyrillics, not even CP866. I have been looking at garbage for decades. Now with the new Golded I can see it properly. That's the difference.


    Cheers, Michiel

    --- GoldED+/W32-MINGW 2.0.0-b20260928
    * Origin: Nieuw Schnøørd (2:280/5555)
  • From Alexey Fayans@2:5030/1997 to Michiel van der Vlist on Wednesday, November 11, 2026 18:27:46
    Hello Michiel!

    On Wed, 11 Nov 2026 15:45 +0100, you wrote to me:

    If/when people will start writing messages in UTF-8, a lot of
    software will display it as garbage. That's the difference.
    My Fidonet system could never Properly display Cyrillics, not even
    CP866. I have been looking at garbage for decades. Now with the new
    Golded I can see it properly. That's the difference.

    That's a different difference. You can see cyrillics properly now even when the message is in CP866 because new GoldED uses UTF-8 internally. No one says it's a bad thing. Bad thing would be to post messages in UTF-8 for no reason and break systems that cannot display it properly while having no issues with displaying CP866.


    ... Music Station BBS | https://bbs.bsrealm.net | telnet://bbs.bsrealm.net
    --- GoldED+/W32-MSVC 1.1.5-b20180707
    * Origin: Music Station | https://ms.bsrealm.net (2:5030/1997)
  • From Kurt Weiske@1:218/700 to Yegor Gluhov on Wednesday, November 11, 2026 09:40:07
    Yegor Gluhov wrote to Alexey Fayans <=-

    And, paradoxically, no cities other than Moscow aka Default City.

    "Default City" sounds like a great name for a fictional dystopian
    metropolis.



    ... RAW DATA FOR RAW NERVES
    --- MultiMail/Win v0.52
    * Origin: http://realitycheckbbs.org | tomorrow's retro tech (1:218/700)
  • From Maurice Kinal@1:153/7001 to Alexey Fayans on Wednesday, November 11, 2026 18:49:13
    Hey Alexey!

    Do you see the problem now?

    I've been seeing it for ages now. Too bad you've chosen to cripple yourself with inferior encodings.

    Life is good,
    Maurice

    -o o- -o -o o- o- o- o- -o -o -o -o
    (\ /) (\ (\ /) /) /) /) (\ (\ (\ (\
    ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^
    ... Gomol snoterost, fyrngearum frod, se þe ær feala gebideð.
    An old person is wisest, sage from past years, he who has endured much.
    --- GNU bash, version 5.3.20(1)-release (x86_64-pc-linux-gnu)
    * Origin: Little Mikey's Brain - Ladysmith BC, Canada (1:153/7001)
  • From Yegor Gluhov@2:382/736 to Kurt Weiske on Wednesday, November 11, 2026 20:35:52
    Hello Kurt!

    11 Nov 26 09:40, you wrote to me:

    And, paradoxically, no cities other than Moscow aka Default City.
    "Default City" sounds like a great name for a fictional dystopian
    metropolis.

    It's not fictional, it's a meme on the Russian-speaking internet. People often post ads or messages like "let's grab some beers near [some street or metro station]" without mentioning the city, as if Moscow were the default. Also, some .ru websites actually default to "Your location: Moscow" when visited from abroad or when location detection fails.

    Anti-Offtopic: pretty similar to assuming Fidonet messages are ASCII-only or CP866-only.

    Yegor

    --- AmberEdit/linux 0.11.0
    * Origin: to err is human, but to really f.. things up you need AI (2:382/736)
  • From Alexey Fayans@2:5030/1997 to Maurice Kinal on Wednesday, November 11, 2026 22:44:13
    Hello Maurice!

    On Wed, 11 Nov 2026 18:49, you wrote to me:

    Do you see the problem now?
    I've been seeing it for ages now.

    But earlier you said the opposite. Ok.

    Too bad you've chosen to cripple yourself with inferior encodings.

    I didn't choose anything. I didn't even say that my software cannot handle UTF-8. This conversation is about a different thing. You said you didn't see a problem first, now you are saying that you've been seeing it for ages now. No reason to continue this conversation, I guess.


    ... Music Station BBS | https://bbs.bsrealm.net | telnet://bbs.bsrealm.net
    --- GoldED+/W32-MSVC 1.1.5-b20180707
    * Origin: Music Station | https://ms.bsrealm.net (2:5030/1997)
  • From Maurice Kinal@1:153/7001 to Alexey Fayans on Wednesday, November 11, 2026 20:11:37
    Hey Alexey!

    This conversation is about a different thing.

    For me it started out with what appears to be the kódování Kamenických and has been digressing from there.

    No reason to continue this conversation, I guess.

    Offhand I don't think it can digress much further, but I've been wrong about that before.

    Life is good,
    Maurice

    o- -o o- o- -o -o o- o- -o -o o- o-
    /) (\ /) /) (\ (\ /) /) (\ (\ /) /)
    ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^
    ... Hyge sceal gehealden, hond gewealden.
    The mind must be restrained, the hand trained.
    --- GNU bash, version 5.3.20(1)-release (x86_64-pc-linux-gnu)
    * Origin: Little Mikey's Brain - Ladysmith BC, Canada (1:153/7001)
  • From Michiel van der Vlist@2:280/5555 to Maurice Kinal on Wednesday, November 11, 2026 21:27:59
    Hello Maurice,

    On 11 Nov 26 11:44, you wrote to me:

    The CP437 is a relatively small minority anyway these days.

    Not really surprising given the lack of support for such encodings on
    the web. The same can be said for CP850.

    The web has made the transition to unicode many years ago. There is no need for supporting the old eight bit encodings any more, so it has stopped. Just like there are no places any more where the traveller can get fresh horses.

    8 bit encoding can still be found in the museum we call Fidonet.

    Personally I have no problem with that. How about you?

    I live in a part of the world where one eight bit encoding is not enough. Even if I forget about Cyrillics, one isn't enough to cover all the languages used in Europe. I consider that a problem.

    One can not please everyone all of the time.

    That is because you're not trying hard enough.

    I prefer to erase all traces of having tried...


    Cheers, Michiel

    --- GoldED+/W32-MINGW 2.0.0-b20260928
    * Origin: Nieuw Schnøørd (2:280/5555)
  • From Michiel van der Vlist@2:280/5555 to Alexey Fayans on Wednesday, November 11, 2026 21:44:13
    Hello Alexey,

    On 11 Nov 26 18:27, you wrote to me:

    If/when people will start writing messages in UTF-8, a lot of
    software will display it as garbage. That's the difference.

    My Fidonet system could never Properly display Cyrillics, not
    even CP866. I have been looking at garbage for decades. Now with
    the new Golded I can see it properly. That's the difference.

    That's a different difference. You can see cyrillics properly now
    even when the message is in CP866 because new GoldED uses UTF-8 internally.

    Not so much of a difference with Russian sysops using the old Golded and being unable to properly see the o with umlaut in Björn Felten's name.

    No one says it's a bad thing. Bad thing would be to post messages in
    UTF-8 for no reason and break systems that cannot display it properly while having no issues with displaying CP866.

    A good reason to post in UTF-8 instead of CP866 are Fidowide areas where both cyrillics and extended latin based characters are used.


    Cheers, Michiel

    --- GoldED+/W32-MINGW 2.0.0-b20260928
    * Origin: Nieuw Schnøørd (2:280/5555)
  • From Maurice Kinal@1:153/7001 to Michiel van der Vlist on Wednesday, November 11, 2026 21:21:31
    Hey Michiel!

    I live in a part of the world where one eight bit encoding is not
    enough.

    You're in the thick of it. Dutch, German, French, Spanish, English, ?????

    I prefer to erase all traces of having tried...

    The journey is half the fun.

    Life is good,
    Maurice

    -o o- -o o- o- -o -o -o -o o- o- o-
    (\ /) (\ /) /) (\ (\ (\ (\ /) /) /)
    ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^
    ... Sinc eaðe mæg, gold on grunde, gumcynnes gehwone oferhigian.
    Treasure, gold in earth, may easily overwhelm any of the human race.
    --- GNU bash, version 5.3.20(1)-release (x86_64-pc-linux-gnu)
    * Origin: Little Mikey's Brain - Ladysmith BC, Canada (1:153/7001)
  • From Yegor Gluhov@2:382/736 to Michiel van der Vlist on Wednesday, November 11, 2026 22:38:09
    Hello Michiel!

    11 Nov 26 21:44, you wrote to Alexey Fayans:

    No one says it's a bad thing. Bad thing would be to post messages in
    UTF-8 for no reason and break systems that cannot display it properly
    while having no issues with displaying CP866.
    A good reason to post in UTF-8 instead of CP866 are Fidowide areas where both cyrillics and extended latin based characters are used.

    UTF-8 and UTF8.FTN.MESSAGING echoareas only? All the rest seem to have either Cyrillics or extended Latin script, but not both together.

    Yegor

    --- AmberEdit/linux 0.11.0
    * Origin: to err is human, but to really f.. things up you need AI (2:382/736)
  • From Alexey Fayans@2:5030/1997 to Michiel van der Vlist on Thursday, November 12, 2026 00:25:21
    Hello Michiel!

    On Wed, 11 Nov 2026 21:44 +0100, you wrote to me:

    That's a different difference. You can see cyrillics properly
    now even when the message is in CP866 because new GoldED uses
    UTF-8 internally.
    Not so much of a difference with Russian sysops using the old Golded

    GoldED is just an example and it's not a problem to replace it. Real problem is the lack of UTF-8 support in old BBS software for DOS like Tornado, RA, EleBBS, Maximus, etc. People running it for retro stuff, not for progress. And there are active users who read and post new messages from such systems. Won't be a huge loss for the whole network of corse, but the quesion is why breaking something that works well for no reason?

    and being unable to properly see the o with umlaut in BjÃ?rn Felten's name.

    It's not a problem even for an old GoldED with a proper xlat config.

    No one says it's a bad thing. Bad thing would be to post messages
    in UTF-8 for no reason and break systems that cannot display it
    properly while having no issues with displaying CP866.
    A good reason to post in UTF-8 instead of CP866 are Fidowide areas
    where both cyrillics and extended latin based characters are used.

    I can't think of a single example, but if there is - sure thing. It's also fine for new areas where UTF-8 usage is allowed or even required by rules.


    ... Music Station BBS | https://bbs.bsrealm.net | telnet://bbs.bsrealm.net
    --- GoldED+/W32-MSVC 1.1.5-b20180707
    * Origin: Music Station | https://ms.bsrealm.net (2:5030/1997)
  • From Nick Boel@1:154/10 to Yegor Gluhov on Wednesday, November 11, 2026 17:35:10
    Hey Yegor!

    On Wed, Nov 11 2026 08:43:42 +0100, you wrote:

    There's already some grief from the CP866 crowd claiming that splitting Fidonet into UTF-8 and non-UTF-8 parts will kill (what remains of) the network. Frankly, plenty of sysops won't ever bother to upgrade, no
    matter what new software gets released or what the FTSC decides.

    I can't imagine anyone is "splitting" anything. People that want to continue into the future can do so, and still communicate with people that don't care to. This is probably the major reason for supporting "replying in original sender's charset" in most, if not all of these newer readers/editors. *shrug*

    Regards,
    Nick

    ... Take my advice, I don't use it anyway.
    --- AmberEdit/linux 0.11.0
    * Origin: thePharcyde_ telnet://bbs.pharcyde.org (Wisconsin) (1:154/10)
  • From Nick Boel@1:154/10 to Alexey Fayans on Wednesday, November 11, 2026 17:51:32
    Hey Alexey!

    On Thu, Nov 12 2026 00:25:20 +0300, you wrote:

    GoldED is just an example and it's not a problem to replace it. Real problem is the lack of UTF-8 support in old BBS software for DOS like Tornado, RA, EleBBS, Maximus, etc. People running it for retro stuff, not for progress. And there are active users who read and post new messages from such systems. Won't be a huge loss for the whole network of corse, but the quesion is why breaking something that works well for no reason?

    Golded (the most recent version) is also "just an example" of being able to properly reply in anyone's legitimate charset. While things are moving forward, they are still supporting backwards compatibility.

    I can't think of a single example, but if there is - sure thing. It's
    also fine for new areas where UTF-8 usage is allowed or even required by rules.

    As far as I know, the UTF-8 echo is the main echo for testing/using UTF-8. If RU.* echos want CP866, then these new readers/editors can also do that, as well. I'm not seeing a problem..?

    Regards,
    Nick

    ... Sarcasm, because beating people up is illegal.
    --- AmberEdit/linux 0.11.0
    * Origin: thePharcyde_ telnet://bbs.pharcyde.org (Wisconsin) (1:154/10)
  • From Rob Swindell@1:103/705 to Alexey Fayans on Wednesday, November 11, 2026 19:19:40
    Re: FTSC
    By: Alexey Fayans to Michiel van der Vlist on Wed Nov 11 2026 12:53 pm

    Most stone age software cannot display UTF-8.

    Sure, but they could convert to a charset/encoding that they can display.
    --
    Rob Swindell
    FTSC Standing Member
    --- SBBSecho 3.38-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Alexey Fayans@2:5030/1997 to Rob Swindell on Thursday, November 12, 2026 09:41:45
    Hello Rob!

    On Wed, 11 Nov 2026 19:19 -0800, you wrote to me:

    Most stone age software cannot display UTF-8.
    Sure, but they could convert to a charset/encoding that they can
    display.

    Unfortunately they cannot. Some software is closed source and is not updated, other can only be built with BP7 which doesn't have a library for reading UTF-8, and UTF-8 is not a simple charset that can be converted to a 8-bit charset using classic xlat table.


    ... Music Station BBS | https://bbs.bsrealm.net | telnet://bbs.bsrealm.net
    --- GoldED+/W32-MSVC 1.1.5-b20180707
    * Origin: Music Station | https://ms.bsrealm.net (2:5030/1997)
  • From Tim Schattkowsky@2:2/29 to Maurice Kinal on Wednesday, November 11, 2026 21:44:56
    //Hello Maurice,//

    on *09.11.26* at *16:48:35* You wrote in Area *FTSC_PUBLIC*
    to *Tim Schattkowsky* about *"FTSC"*.

    Probably. At this point in time 'iconv -f cp895' claims that cp895 is
    not supported. I noted that "MSGID: 2:2/29 ee68e987" is flying the utf-8 flag

    Dont get the connection.

    and, other than the screwed up penguin quote, it looks perfect. As
    for "MSGID: 2:2/29 ee68e98f" I'd require a proper encoding table to check it against. How exactly did you accomplish the conversion from utf-8 to cp895?

    Goes directly through the corresponding windows APIs.

    I noted that you only had issues with the 'æ' character in the Anglo-Saxon part.

    I guess its simply not in CP895?

    Regards,
    Tim

    --- WinPoint 419.0
    * Origin: Original WinPoint Origin! (2:2/29)
  • From Tim Schattkowsky@2:2/29 to Maurice Kinal on Thursday, November 12, 2026 14:58:59
    //Hello Maurice,//

    on *09.11.26* at *16:48:35* You wrote in Area *FTSC_PUBLIC*
    to *Tim Schattkowsky* about *"FTSC"*.

    Forgot to quote that one (again that funny CP) ...

    ... Domgeorne dreorigne oft in hyra breostcofan binda? f?ste.
    Those eager for glory often bind sorrowful thoughts fast within the heart.

    Regards,
    Tim

    --- WinPoint 419.0
    * Origin: Original WinPoint Origin! (2:2/29)
  • From Maurice Kinal@1:153/7001 to Alexey Fayans on Friday, November 13, 2026 01:09:49
    Hey Alexey!

    UTF-8 is not a simple charset that can be converted to a 8-bit
    charset

    There should be no trouble converting this msg to cp866. I'd do it myself but I don't want to. I'll probably go back to the Anglo-Saxon taglines. Also I am unsure of the English translations.

    Life is good,
    Maurice

    o- -o o- -o o- -o -o o- -o -o -o -o
    /) (\ /) (\ /) (\ (\ /) (\ (\ (\ (\
    ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^
    ... Дают - бери, а бьют - беги.
    If you are given something, take it; if you are being beaten, run
    --- GNU bash, version 5.3.20(1)-release (x86_64-pc-linux-gnu)
    * Origin: Little Mikey's Brain - Ladysmith BC, Canada (1:153/7001)
  • From Alexey Fayans@2:5030/1997 to Maurice Kinal on Friday, November 13, 2026 10:18:28
    Hello Maurice!

    On Fri, 13 Nov 2026 01:09, you wrote to me:

    UTF-8 is not a simple charset that can be converted to a 8-bit
    charset
    There should be no trouble converting this msg to cp866. I'd do it
    myself but I don't want to.

    Yeah, converting latin from/to any charset is indeed trivial - you just change the charset name and that's it.


    ... Music Station BBS | https://bbs.bsrealm.net | telnet://bbs.bsrealm.net
    --- GoldED+/W32-MSVC 1.1.5-b20180707
    * Origin: Music Station | https://ms.bsrealm.net (2:5030/1997)
  • From Chris Jacobs@2:280/5555.11 to Alexey Fayans on Friday, November 13, 2026 11:16:17
    Hello Alexey!

    13 Nov 26 10:18, you wrote to Maurice Kinal:

    Hello Maurice!

    On Fri, 13 Nov 2026 01:09, you wrote to me:

    UTF-8 is not a simple charset that can be converted to a 8-bit
    charset
    There should be no trouble converting this msg to cp866. I'd do
    it myself but I don't want to.

    Yeah, converting latin from/to any charset is indeed trivial - you
    just change the charset name and that's it.

    There is extended BCD https://en.wikipedia.org/wiki/EBCDIC

    ... Music Station BBS | https://bbs.bsrealm.net |
    telnet://bbs.bsrealm.net
    --- GoldED+/W32-MSVC 1.1.5-b20180707
    * Origin: Music Station | https://ms.bsrealm.net (2:5030/1997)

    Chris


    --- Binkd, FMail, Golded+
    * Origin: https://drschrisjacobs.nl (2:280/5555.11)
  • From Maurice Kinal@1:153/7001 to Alexey Fayans on Friday, November 13, 2026 14:38:36
    Hey Alexey!

    Yeah, converting latin from/to any charset is indeed trivial - you
    just change the charset name and that's it.

    What latin? What happens to the cyrillic?

    Life is good,
    Maurice

    -o -o -o o- -o -o -o o- o- o- -o -o
    (\ (\ (\ /) (\ (\ (\ /) /) /) (\ (\
    ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^
    ... �ࠢ¤  £« §  ª®«¥â.
    Truth pricks eyes
    --- GNU bash, version 5.3.20(1)-release (x86_64-pc-linux-gnu)
    * Origin: Little Mikey's Brain - Ladysmith BC, Canada (1:153/7001)
  • From Rob Swindell@1:103/705 to Alexey Fayans on Friday, November 13, 2026 12:30:52
    Re: FTSC
    By: Alexey Fayans to Rob Swindell on Thu Nov 12 2026 09:41 am

    Hello Rob!

    On Wed, 11 Nov 2026 19:19 -0800, you wrote to me:

    Most stone age software cannot display UTF-8.
    Sure, but they could convert to a charset/encoding that they can display.

    Unfortunately they cannot. Some software is closed source and is not updated, other can only be built with BP7 which doesn't have a library for reading UTF-8, and UTF-8 is not a simple charset that can be converted to a 8-bit charset using classic xlat table.

    FidoNet has a tradition of creating and inserting tools into the import/export message chain. That chain could include a tool that translated UTF-8 encoded messages to the locally-supported encoding/charset without updating or replacing any of the existing legacy software. Very doable.
    --
    Rob Swindell
    FTSC Standing Member
    --- SBBSecho 3.38-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Michiel van der Vlist@2:280/5555 to Alexey Fayans on Friday, November 13, 2026 20:50:11
    Hello Alexey,

    On 12 Nov 26 00:25, you wrote to me:

    GoldED is just an example and it's not a problem to replace it. Real problem is the lack of UTF-8 support in old BBS software for DOS like Tornado, RA, EleBBS, Maximus, etc. People running it for retro stuff,
    not for progress.

    Sure, no problem. If they enjoy running that muweum stuff, no problem. But of course they won't benefit from the new developmenst. Just like sysops that hang on to POTS won't have the benfiys from what came after POTS. Like ISDN and FOIP.

    And there are active users who read and post new messages from such systems. Won't be a huge loss for the whole network of corse,

    I don't think rolling out UTF-8 in Fidonet will lead to a split, let alone that it will kill Fidonet. What I have learned over the deacades is that Fidonet is pretty hard to kill. 30 yeara go I thougt that Fidonet would not survive Y2K. Not because of the technical problems with two figit years but because everyone one would have movef to the greeneer pastures of the Internet. But that didn't happen. A quarter of a a century later, Fidonet is still here. It has survived by adapting. It will survive UF-8.

    but the quesion is why breaking something that works well for no
    reason?

    This codepage shit does NOT work well. It was a compromise from the beginning and it never really worked well. Not for a global network. It is like the ol days of analog television where every country had their own TV standard. A mess it was. There is a reason the Internet has dumped all tose 8 bit ancodings and gone unicode well over a decade ago.

    and being unable to properly see the o with umlaut in Bj├?rn
    Felten's name.

    It's not a problem even for an old GoldED with a proper xlat config.

    My problem with the old Golded is that it could only work with the local set that the Window was started up in. In my case it was actually locked to

    XLATLOCALSET CP850.

    So no matter what I did. I could only display that and nothing alse. Translation tables could ony translate INTO that.

    Do the windows version distributed in Russia not have a similar problem?

    No one says it's a bad thing. Bad thing would be to post
    messages in UTF-8 for no reason and break systems that cannot
    display it properly while having no issues with displaying
    CP866.

    Tjah....

    Ther ais no way you can display Cirillilecs AND accents, umlauts and carot AND Greek in one and the same message with an 8 bit encoding. UTF-8 solves that problem.


    Cheers, Michiel

    --- GoldED+/W32-MINGW 2.0.0-b20260928
    * Origin: Nieuw Schnøørd (2:280/5555)
  • From Alexey Fayans@2:5030/1997 to Rob Swindell on Saturday, November 14, 2026 11:40:13
    Hello Rob!

    On Fri, 13 Nov 2026 12:30 -0800, you wrote to me:

    FidoNet has a tradition of creating and inserting tools into the import/export message chain. That chain could include a tool that translated UTF-8 encoded messages to the locally-supported encoding/charset without updating or replacing any of the existing
    legacy software. Very doable.

    I have such a tool and this is my last resort option in case the UTF-8 madness will actually happen.


    ... Music Station BBS | https://bbs.bsrealm.net | telnet://bbs.bsrealm.net
    --- GoldED+/W32-MSVC 1.1.5-b20180707
    * Origin: Music Station | https://ms.bsrealm.net (2:5030/1997)
  • From Alexey Fayans@2:5030/1997 to Michiel van der Vlist on Saturday, November 14, 2026 11:44:51
    Hello Michiel!

    On Fri, 13 Nov 2026 20:50 +0100, you wrote to me:

    Ther ais no way you can display Cirillilecs AND accents, umlauts and
    carot AND Greek in one and the same message with an 8 bit encoding.

    I know. My point is that it's not needed where CP866 is used.

    UTF-8 solves that problem.

    So it solves nothing at all.


    ... Music Station BBS | https://bbs.bsrealm.net | telnet://bbs.bsrealm.net
    --- GoldED+/W32-MSVC 1.1.5-b20180707
    * Origin: Music Station | https://ms.bsrealm.net (2:5030/1997)
  • From Michiel van der Vlist@2:280/5555 to Alexey Fayans on Saturday, November 14, 2026 11:02:54
    Hello Alexey,

    On 14 Nov 26 11:40, you wrote to Rob Swindell:

    FidoNet has a tradition of creating and inserting tools into the
    import/export message chain. That chain could include a tool that
    translated UTF-8 encoded messages to the locally-supported
    encoding/charset without updating or replacing any of the
    existing legacy software. Very doable.

    I have such a tool and this is my last resort option in case the UTF-8 madness will actually happen.

    "UTF-8 madness"? Oh come on, transition to UTF-8 is a natural path of evolution that started decades ago. That train is not going to stop. If we have to use emotion to describe the process, I'd say that is is the "codepage madness" that will finally come to an end.


    Cheers, Michiel

    --- GoldED+/W32-MINGW 2.0.0-b20260928
    * Origin: Nieuw Schnøørd (2:280/5555)
  • From Michiel van der Vlist@2:280/5555 to Alexey Fayans on Saturday, November 14, 2026 10:45:50
    Hello Alexey,

    On 14 Nov 26 11:44, you wrote to me:

    Ther is no way you can display Cirillilecs AND accents, umlauts
    and carot AND Greek in one and the same message with an 8 bit
    encoding.

    I know. My point is that it's not needed where CP866 is used.

    Look further than your own back yard. UTF-8 is indeed not needed now where CP866 is used. But the world of communication is bigger than just the area where CP866 is used. In the end it is easier to use just one universal encoding for the whole world, than each his own encoding. In the rest of the internet this message was understood and acted upon. Fidonet will eventually follow, like it or not. Join the ride or stay behind...

    UTF-8 solves that problem.

    So it solves nothing at all.

    It solves the "codepage madness". :-)


    Cheers, Michiel

    --- GoldED+/W32-MINGW 2.0.0-b20260928
    * Origin: Nieuw Schnøørd (2:280/5555)
  • From Alexey Fayans@2:5030/1997 to Michiel van der Vlist on Saturday, November 14, 2026 14:37:50
    Hello Michiel!

    On Sat, 14 Nov 2026 11:02 +0100, you wrote to me:

    I have such a tool and this is my last resort option in case the
    UTF-8 madness will actually happen.
    "UTF-8 madness"? Oh come on, transition to UTF-8 is a natural path

    Yes, madness. Like I already said, UTF-8 solves nothing in most cases. It's fine to use it in an international echo, for example, where multiple languages may be used at the same time. But not where only one langage is used and perfectly fits into a 8-bit code page.


    ... Music Station BBS | https://bbs.bsrealm.net | telnet://bbs.bsrealm.net
    --- GoldED+/W32-MSVC 1.1.5-b20180707
    * Origin: Music Station | https://ms.bsrealm.net (2:5030/1997)
  • From Alexey Fayans@2:5030/1997 to Michiel van der Vlist on Saturday, November 14, 2026 14:42:44
    Hello Michiel!

    On Sat, 14 Nov 2026 10:45 +0100, you wrote to me:

    I know. My point is that it's not needed where CP866 is used.
    Look further than your own back yard.

    Maybe you should follow this advice yourself?

    UTF-8 is indeed not needed now where CP866 is used.

    Exactly.

    But the world of communication is bigger than just the area where
    CP866 is used.

    And I already said many times that it's perfectly fine to use UTF-8 there.

    In the end it is easier to use just one universal encoding for the
    whole world

    It would be easier if ther software was as simple as it is for the internet - where users only run a choice of modern *client* software (browser, email client, etc) with all the content served on the server side. But that's not how FTN evolved and so the same rules cannot be applied there.

    Fidonet will eventually follow, like it or not. Join the
    ride or stay behind...

    It will either die completely (becoming an outdated internet-based forums system first and then forgotten), or find its own way to evolve without breaking everything for nothing and attracting people looking for real alternative to internet.


    ... Music Station BBS | https://bbs.bsrealm.net | telnet://bbs.bsrealm.net
    --- GoldED+/W32-MSVC 1.1.5-b20180707
    * Origin: Music Station | https://ms.bsrealm.net (2:5030/1997)
  • From Michiel van der Vlist@2:280/5555 to Alexey Fayans on Saturday, November 14, 2026 19:26:07
    Hello Alexey,

    On 14 Nov 26 14:42, you wrote to me:

    Look further than your own back yard.

    Maybe you should follow this advice yourself?

    Looking beyound my own back yard is exactly what made me become a UTF-8 evangelist. If my vision had been limited to my own back yard, I would have been satisfied with a code page that covered unlauts, accents, carots, the ƒ, the ij and the €.

    FYI: such a code page does not exist.

    25 years ago when it looked like Russia was becoming a normal European country, I got interested in the Russian language and I looked for ways to get Cyrrilic on my screen. I found several ways, but none of them made it possible to have both the unlauts and accents and Cyrillic. Then I found unicode and I became interested....

    UTF-8 is indeed not needed now where CP866 is used.

    Exactly.

    Note the word "now".

    But the world of communication is bigger than just the area where
    CP866 is used.

    And I already said many times that it's perfectly fine to use UTF-8
    there.

    In the end it is easier to use just one universal encoding for
    the whole world

    It would be easier if ther software was as simple as it is for the internet - where users only run a choice of modern *client* software (browser, email client, etc) with all the content served on the server side.

    Bad argument. The "internet" is bigger than http(s).

    But that's not how FTN evolved and so the same rules cannot be applied there.

    Fidonet has gone through several stages of upgrades that were not downwards compatible.

    Fidonet will eventually follow, like it or not. Join the
    ride or stay behind...

    It will either die completely (becoming an outdated internet-based
    forums system first and then forgotten), or find its own way to evolve without breaking everything for nothing and attracting people looking
    for real alternative to internet.

    In the beginning of Fidonet node numbers were one dimensional. Then nodemumbers became 2D. Systems with 1D node numbers could no longer communicate with sysems with 2D node numbers. Fidonet survived.

    Fidonet went from 2D node numbers to 3D node numbers. Fidonet survived.

    Fidonet went from 3D to 4D nodenumbers. Fidonet survived.

    Fidonet went from POTS to ISDN. Fidonet survived.

    Fidonet went from POTS/ISDN to FOIP. Fidonet survived.

    Fidonet went from a strict hyrachical system for echomail distribution to the Fidoweb. Fidonet survived.

    Fidonet will survive UFT-8.


    Cheers, Michiel

    --- GoldED+/W32-MINGW 2.0.0-b20260928
    * Origin: Nieuw Schnøørd (2:280/5555)
  • From Michiel van der Vlist@2:280/5555 to Alexey Fayans on Saturday, November 14, 2026 21:51:01
    Hello Alexey,

    14 Nov 26 19:26, I wrote to you:

    Fidonet will survive UFT-8.

    Having said that, I will now stop this thread. We are far too off topic anyway. This is not really something that needs interaction between the FTSC and the Fidonet community.

    So enjoy the weekend.


    Cheers, Michiel

    --- GoldED+/W32-MINGW 2.0.0-b20260928
    * Origin: Nieuw Schnøørd (2:280/5555)