----------------------------------------------------------------------------------
@MSGID: 1:129/215 83b2be58
@REPLY:
<86a1b7d3-fd55-4e99-953d-9ac831488815n@googlegroups.com> 28fe98fb
@TID: Mystic BBS 1.12 A49
@TZUTC: -0400
gk> Sound like sending UTF8 TO the BBS is not working
gk> or still expected CP437. As when I switch my UTF8 session to
gk> to CP437 the chars working instantly (but as well well the rest is ugly
gk> 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)
SEEN-BY: 1/120 18/0 50/109 116/116 120/616 123/0
10 25 115 170 180 200 525
SEEN-BY: 123/755 3001 129/215 135/300 153/757 7715
154/10 30 40 50 700 220/90
SEEN-BY: 222/2 226/18 70 227/201 229/310 240/1120
250/1 275/1000 292/854
SEEN-BY: 299/6 301/1 467/888 712/1321 2320/105
3634/0 12 27 56 57 119
SEEN-BY: 5000/111 5001/100 5005/49 5019/40 5020/329
715 830 848 1042 4441
SEEN-BY: 5020/12000 5030/49 1081 5053/51 5054/8
5064/56 5075/128 5080/102
SEEN-BY: 5083/1 444 5090/958
@PATH: 129/215 154/10 3634/12 5020/1042 4441