Sound like sending UTF8 TO the BBS is not working
or still expected CP437. As when I switch my UTF8 session to
to CP437 the chars working instantly (but as well well the rest is ugly
as BBS sending in UTF8.

Yes this is currently broken. I am planning to reamp and fix this after the A49 release which will hopefully be soon.

Sorry for the inconvenience

... My reality check just bounced

--- Mystic BBS v1.12 A49 2023/04/30 (Windows/64)
* Origin: Sector 7 * Mystic WHQ (1:129/215)

On 03 May 2023, g00r00 said the following...

--- Mystic BBS v1.12 A49 2023/04/30 (Windows/64)

just snagged this.

--- Mystic BBS v1.12 A48 2022/04/26 (Windows/64)
* Origin: Omicron Theta * Birmingham, AL * 199.231.191.60 (1:116/17)

just snagged this.

Was not easy to find for me bt get it. Same issue.
Setup and Seidig UTF8 will show wrong Chars when echo back.

Also a further test.. it’s only affect higer Ascii. All „7 bit“ ascii work fine as UFT Coding,
bit anything above get back crappy..

so even „§" „µ“ „ß“

--- SoupGate-Win32 v1.05
* Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)

Am 03.05.23 um 12:21 schrieb g00r00:

Yes this is currently broken. I am planning to reamp and fix this

after the

A49 release which will hopefully be soon.

Sorry for the inconvenience

Ok, now via a right News Reader and NNTP Carrier. Google Groups seems to
suck as not seen YOUR Answer.

Thanks for reply and that you will take care.

Marc aka Gierig

--- SoupGate-Win32 v1.05
* Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)