1. Forum
  2. FSXNet
  3. FSX MYS

  • Ansi Issue

    From metalhead@21:1/113 to All on Thu Jan 23 12:59:10 2020
    I'm having an ansi display issue with the latest version of Mystic on my 64
    Bit Ubuntu pc. It's displaying about 75% good, with certain characters coming out wrong.

    I tried changing the Mystic setting for UTF-8 or CP437, but that had no noticeable effect; the ansi is still messed up with either setting.

    I consulted the wiki doku.php, but it looks like it only has solutions for Windows &/or Mac sysops.

    My guess is that I need to customize my terminal, but google searches aren't turning up anything yet.

    --- Mystic BBS v1.12 A43 2019/03/03 (Raspberry Pi/32)
    * Origin: Alcoholiday / Est. 1995 / alco.bbs.io (21:1/113)
  • From Beery@21:4/109 to metalhead on Thu Jan 23 13:25:18 2020
    I'm having an ansi display issue with the latest version of Mystic on my 64 Bit Ubuntu pc. It's displaying about 75% good, with certain
    characters coming out wrong.



    Are you sure it is not a terminal issue on the client? What happens if you
    are on another computer running a different telnet client? Do you get the
    same display?

    There are times especially with Telnet clients previously written for RS232
    use that may not have fast enough code to capture all the incoming data as it processes various ANSI sequences. Some ANSI sequences are more complex and take more time, and a poorly written client or one with a slow CPU, could
    drop data depending upon how things are interfaced.

    What happens if you login locally on your computer? If it works there, then
    it is likely what I described above. If it doesn't work with the local login from Mystic's interface, then it is definitely something with your ANSI
    coding.

    Beery

    --Beery Miller -- 9640 News BBS -- 9640news.ddns.net:9640 --

    --- Mystic BBS v1.12 A42 2019/02/01 (Windows/64)
    * Origin: 9640 News BBS (21:4/109)
  • From Al@21:4/106.1 to metalhead on Thu Jan 23 10:25:34 2020
    I'm having an ansi display issue with the latest version of Mystic on my 64 Bit Ubuntu pc. It's displaying about 75% good, with certain characters coming out wrong.

    I tried changing the Mystic setting for UTF-8 or CP437, but that had no noticeable effect; the ansi is still messed up with either setting.

    It could be that the code page isn't being detected properly.

    You can change the ask codepage setting in your login/matrix settings to ask then you can choose what you want to use at each login.

    There are times when you might want to use CP437 instead of UTF-8 also, when using Syncterm from the desktop using one of the SDL modes.

    --- BBBS/Li6 v4.10 Toy-4
    * Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106.1)
  • From metalhead@21:1/113 to Beery on Thu Jan 23 13:45:49 2020
    What happens if you login locally on your computer? If it works there,

    My ansi display problem is just on my local login with mystic (and it's also
    a problem when I use mystic -cfg.)

    I've never used a linux BBS client before, I've always used Netrunner with Wine, but now that everyone has shown me how to install Mystic on Linux, I
    bet I could install Netrunner (for Linux) too. I'll try that & see how it looks.. but most likely will be bad like the way Mystic currently looks

    --- Mystic BBS v1.12 A43 2019/03/03 (Raspberry Pi/32)
    * Origin: Alcoholiday / Est. 1995 / alco.bbs.io (21:1/113)
  • From metalhead@21:1/113 to Al on Thu Jan 23 13:47:03 2020
    You can change the ask codepage setting in your login/matrix settings to ask then you can choose what you want to use at each login.

    Thanks for help with this issue BEERY & Al. I'll try this too..

    --- Mystic BBS v1.12 A43 2019/03/03 (Raspberry Pi/32)
    * Origin: Alcoholiday / Est. 1995 / alco.bbs.io (21:1/113)
  • From metalhead@21:1/113 to metalhead on Thu Jan 23 17:23:38 2020
    You can change the ask codepage setting in your login/matrix settings ask then you can choose what you want to use at each login.

    For anyone else arriving here (you never know!) Al was right - I set the login/matrix setting to ANSI and everything is displaying good now without
    any further issue.

    --- Mystic BBS v1.12 A43 2019/03/03 (Raspberry Pi/32)
    * Origin: Alcoholiday / Est. 1995 / alco.bbs.io (21:1/113)
  • From Analog@21:2/123 to metalhead on Thu Jan 23 21:19:06 2020
    Metal,

    First, if you're in terminal, you're most likely using UTF-8. Second most terminals will not render colors correctly without changing the defaults in terminal dircolors. I recommend using Syncterm to telnet to localhost.

    If you have python installed, pip install "telnetlib3". Then you can telnet into your machine from the Linux shell by doing:
    telnetlib3-client --encoding=cp437 localhost
    or skip the --encoding for UTF-8.

    You can also use telnetlib3 to telnet into any bbs and it renders near
    perfect ansis. UTF-8 supports all extended ASCII characters but the terminal must be told to do so properly. For beginners, go with Syncterm/Netrunner.

    Cheers!

    |19|15┌─|16|07┤ |08De|07ad|15be|07a|08tz b|07b|15s
    |07└─┘├─┐ |08:>.|12F|04sx |1221|08:|122|08/|12123|08.
    |11■ |07└|19|15─|16|07┘ |08:>.|10A|02gn |1046|08:|101|08/|10123|08.
    |12≡|15A|07n|08al|07o|15g|12≡ |08:>.|13F|05dn |131|08:|13305|08/|132|08.
    |08:>.|15S|08ci |1577|08:|151|08/|15131|08.
    |08:>.|11T|03qw |111337|08:|113|08/|1113|08.

    --- Mystic BBS v1.12 A44 2020/01/16 (Linux/64)
    * Origin: deadbeatz.org (21:2/123)
  • From g00r00@21:1/163 to metalhead on Fri Jan 24 12:14:26 2020
    What happens if you login locally on your computer? If it works ther

    My ansi display problem is just on my local login with mystic (and it's also a problem when I use mystic -cfg.)

    Go into Sys Config -> General Settings and play with the "Local Code Page" option at the bottom. Try both CP437 and UTF8.

    It could be that your Linux Distro uses a weird terminal too.

    --- Mystic BBS v1.12 A43 2019/03/03 (Windows/32)
    * Origin: |08--[|15!|07dreamland BBS bbs.dreamlandbbs.org (21:1/163)