Subj : Re: unicode/cp437 door
To   : NuSkooler
From : fusion
Date : Mon Apr 05 2021 09:27 am

On 03 Apr 2021, NuSkooler said the following...
 
 Nu> This is used successfully in a lot of setups, so I'd have to have more
 Nu> details as to why it's not working for you I guess -- assuming the work
 Nu> around isn't too much of of a PITA/you want to muck with it more :)

tbh i'd love it if most bbses just defaulted to utf-8 and auto-translated
art/doors/message bases/etc to utf-8. the target bbs of echomail for example..
make it their responsibility to force their bases to cp437 should they wish to
do so. i don't think that'd fly though considering what we saw here with ONE
non-English-language message but.. ;)

mystic (a46 at least) SEEMS to have utf-8 detection but doing just 'ssh bbs'
from a linux command prompt doesn't seem to figure it out. seems to work with
ZOC. i'm assuming Netrunner also works right. but tbh the target all along
for me feels like it should be "nothing installed, user has ssh already" ..
just like how windows used to always come with 'telnet'.

in windows 10 only but.. openssh even automatically sets the command prompt to
utf-8, the command prompt's ansi emulation is better than most (no more
ansi.sys monkey business) AND it's harware accelerated. without installing
anything.

i duno, i'm probably preaching to the crowd ;)

--- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
 * Origin: cold fusion - cfbbs.net - grand rapids, mi (21:1/616)

.