Hello, All!

Is it possible to make synchronet be compartible with CP866 charset that is common for Cyrillic part of Fidonet?


* Originally in SYNC_PROGRAMMING
* Crossposted in SYNCHRONET

--
... It's full of stars!
--- GoldED+/LNX 1.1.5--b20180707 (Linux 4.19.97-v7+ CPU UNKNOWN)
* Origin: FireFox Station (2:5075/35)
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

Re: CP866 codepage support
By: Eugene Subbotin to All on Wed Mar 11 2020 03:18 am

Hello, All!

Is it possible to make synchronet be compartible with CP866 charset that is common for Cyrillic part of Fidonet?

It's possible, but not already support/recognized. What is your interest, just that the tosser (SBBSecho) exports messages with the appropriate CHRS kludge or that the user could use a CP866-terminal program and have other charsets (UTF-8 or CP437) converted to CP866 on the fly before sending to the user?

digital man

Synchronet/BBS Terminology Definition #72:
Sysop = System Operator
Norco, CA WX: 63.2øF, 81.0% humidity, 1 mph SW wind, 0.41 inches rain/24hrs

---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

Hello, Digital!

10 Mar 20 17:25, you wrote to me:

Is it possible to make synchronet be compartible with CP866 charset
that is common for Cyrillic part of Fidonet?

It's possible, but not already support/recognized. What is your
interest, just that the tosser (SBBSecho) exports messages with the appropriate CHRS kludge or that the user could use a CP866-terminal program and have other charsets (UTF-8 or CP437) converted to CP866 on
the fly before sending to the user?

The main goal is to read and send messages in CP866 Echo from UTF-8 terminal and web, with the appropriate CHARS kludge of course. Converting on the fly also will be nice. So that any user who logged in can read russian fidonet echos.

--
... It's full of stars!
--- GoldED+/LNX 1.1.5--b20180707 (Linux 4.19.97-v7+ CPU UNKNOWN)
* Origin: FireFox Station (2:5075/35)
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

Re: Re: CP866 codepage support
By: Eugene Subbotin to Digital Man on Wed Mar 11 2020 06:32 am

Hello, Digital!

10 Mar 20 17:25, you wrote to me:

Is it possible to make synchronet be compartible with CP866 charset
that is common for Cyrillic part of Fidonet?

It's possible, but not already support/recognized. What is your interest, just that the tosser (SBBSecho) exports messages with the appropriate CHRS kludge or that the user could use a CP866-terminal program and have other charsets (UTF-8 or CP437) converted to CP866 on the fly before sending to the user?

The main goal is to read and send messages in CP866 Echo from UTF-8 terminal and web, with the appropriate CHARS kludge of course. Converting on the fly also will be nice. So that any user who logged in can read russian fidonet echos.

Interesting. So if you're using a UTF-8 terminal, which is capable of all the CP866 charactesr (and a lot more), why would you want to send CP866? That seems... weird. You can't send UTF-8 encoded messages in Cyrillic echoes?

digital man

Synchronet/BBS Terminology Definition #50:
NUL = ASCII 0
Norco, CA WX: 58.1øF, 85.0% humidity, 2 mph SW wind, 0.42 inches rain/24hrs

---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

Hello, Digital!

10 Mar 20 20:56, you wrote to me:

The main goal is to read and send messages in CP866 Echo from UTF-8
terminal and web, with the appropriate CHARS kludge of course.
Converting on the fly also will be nice. So that any user who
logged in can read russian fidonet echos.

Interesting. So if you're using a UTF-8 terminal, which is capable of
all the CP866 charactesr (and a lot more), why would you want to send CP866? That seems... weird. You can't send UTF-8 encoded messages in Cyrillic echoes?

No, I can't, because fidonet readers mostly don't have UTF-8 support, so CP866 is primary charset for all cyrillic echos :(
Cyrillic UTF-8 in unreadable when using extended-ASCII

--
... It's full of stars!
--- GoldED+/LNX 1.1.5--b20180707 (Linux 4.19.97-v7+ CPU UNKNOWN)
* Origin: FireFox Station (2:5075/35)
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

Re: Re: CP866 codepage support
By: Eugene Subbotin to Digital Man on Wed Mar 11 2020 04:19 pm

Hello, Digital!

10 Mar 20 20:56, you wrote to me:

The main goal is to read and send messages in CP866 Echo from UTF-8
terminal and web, with the appropriate CHARS kludge of course.
Converting on the fly also will be nice. So that any user who
logged in can read russian fidonet echos.

Interesting. So if you're using a UTF-8 terminal, which is capable of all the CP866 charactesr (and a lot more), why would you want to send CP866? That seems... weird. You can't send UTF-8 encoded messages in Cyrillic echoes?

No, I can't, because fidonet readers mostly don't have UTF-8 support, so CP866 is primary charset for all cyrillic echos :(
Cyrillic UTF-8 in unreadable when using extended-ASCII

UTF-8 is the future, I have to imagine that eventually those Cyrillic echoes will switch to it. And Synchronet transcodes UTF-8 -> CP437 on the fly already.

But yes, it's possible that CP866 support could be added to Synchronet. I'm not sure what terminal program one would use to test CP866 support (not SyncTERM).

digital man

Synchronet/BBS Terminology Definition #44:
KD = King Drafus (Allen Christiansen)
Norco, CA WX: 61.9øF, 83.0% humidity, 2 mph WSW wind, 0.14 inches rain/24hrs

---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

Re: Re: CP866 codepage support
By: Digital Man to Eugene Subbotin on Wed Mar 11 2020 10:19:44

But yes, it's possible that CP866 support could be added to
Synchronet. I'm not sure what terminal program one would use
to test CP866 support (not SyncTERM).

putty might be one to start with... but the underlying OS needs to already have conversion support in place...

c-kermit (5a and up) also knows about CP866 via its soft fonts...

zaTelnet (defunct) looks like it was another...

looks like qodem-x11 is another...

https://www.google.com/search?q="CP866"+"telnet"+"terminal"


)\/(ark

---
þ Synchronet þ The SouthEast Star Mail HUB - SESTAR

Hello, Digital!

11 Mar 20 10:19, you wrote to me:

No, I can't, because fidonet readers mostly don't have UTF-8
support, so CP866 is primary charset for all cyrillic echos :(
Cyrillic UTF-8 in unreadable when using extended-ASCII

UTF-8 is the future, I have to imagine that eventually those Cyrillic echoes will switch to it. And Synchronet transcodes UTF-8 -> CP437 on
the fly already.

I know, but this will not happen in nearest future because GoldED (the most popultar fidonet mail editor) doesn't support UTF-8 :(

But yes, it's possible that CP866 support could be added to
Synchronet. I'm not sure what terminal program one would use to test
CP866 support (not SyncTERM).

Putty can. If CP866 support will be added into Synchronet on same conditions as
CP437 I will became the beta-tester of this feature (and can spread wide this in Russia and Ukraine)

--
... It's full of stars!
--- GoldED+/LNX 1.1.5--b20180707 (Linux 4.19.97-v7+ CPU UNKNOWN)
* Origin: FireFox Station (2:5075/35)
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

On 3/12/20 12:52 AM, Eugene Subbotin wrote:

But yes, it's possible that CP866 support could be added to
Synchronet. I'm not sure what terminal program one would use to test CP866 support (not SyncTERM).

Putty can. If CP866 support will be added into Synchronet on same conditions as
CP437 I will became the beta-tester of this feature (and can spread wide this in Russia and Ukraine)

Best bet may be to use UTF-8 locally and on synchronet and have an
option for your mail/tosser for the echo to import/export in CP866 compatibility mode.

Almost everything outside legacy dos and bbs stuff seems to be UTF8,
been dealing with a couple headaches of my own regarding terminal
detection on BBSes as I'd like to be able to use "any" terminal with
minimal issue and resize.

--
Michael J. Ryan
tracker1 +o Roughneck BBS

---
þ Synchronet þ Roughneck BBS - coming back 2/2/20

Re: Re: CP866 codepage support
By: Eugene Subbotin to Digital Man on Thu Mar 12 2020 11:52 am

Hello, Digital!

11 Mar 20 10:19, you wrote to me:

No, I can't, because fidonet readers mostly don't have UTF-8
support, so CP866 is primary charset for all cyrillic echos :(
Cyrillic UTF-8 in unreadable when using extended-ASCII

UTF-8 is the future, I have to imagine that eventually those Cyrillic echoes will switch to it. And Synchronet transcodes UTF-8 -> CP437 on the fly already.

I know, but this will not happen in nearest future because GoldED (the most popultar fidonet mail editor) doesn't support UTF-8 :(

But yes, it's possible that CP866 support could be added to
Synchronet. I'm not sure what terminal program one would use to test CP866 support (not SyncTERM).

Putty can. If CP866 support will be added into Synchronet on same conditions as CP437 I will became the beta-tester of this feature (and can spread wide this in Russia and Ukraine)

I'm interested in doing this and would need an active participant/user (like yourself). But you're writing your messages using GoldEd, which seems to imply that you're not even running Synchronet or not using it for reading/writing messages?

digital man

This Is Spinal Tap quote #46:
"Not an Exit" - we don't want an exit. Well that's true.
Norco, CA WX: 57.8øF, 69.0% humidity, 13 mph NE wind, 0.61 inches rain/24hrs

---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net