1. Forum
  2. fsxNet
  3. Talisman/Magicka Support

  • Control Codes -> UTF8

    From apam@21:1/126 to All on Sun Oct 27 13:06:15 2019
    Hi

    I've just committed a change that will convert some control codes to
    their graphic counterparts in UTF8

    This only works if you have UTF-8 selected as the codepage, if you have
    CP437 you get them as they are.

    Al, this should make your musical note character appear as a musical
    note in UTF-8.

    Andrew

    --- MagickaBBS v0.13alpha (Linux/x86_64)
    * Origin: HappyLand - telnet://magickabbs.com:2023/ (21:1/126)
  • From Al@21:4/106 to apam on Sat Oct 26 20:46:04 2019
    I've just committed a change that will convert some control codes to
    their graphic counterparts in UTF8

    This only works if you have UTF-8 selected as the codepage, if you have CP437 you get them as they are.

    Al, this should make your musical note character appear as a musical
    note in UTF-8.

    It does, I just updated and had a look at that message with no trouble.

    I first encountered this maybe 15 years ago. It happens rarely. At first
    I had no clue what was happening and would reboot to get back to normal
    before I discovered that I could get back to normal by typing reset at
    the prompt. Looks much better now.. :)

    Ttyl :-)
    Al

    --- MagickaBBS v0.13alpha (Linux/x86_64)
    * Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106)
  • From apam@21:1/126 to Al on Sun Oct 27 13:53:35 2019
    It does, I just updated and had a look at that message with no trouble.

    I first encountered this maybe 15 years ago. It happens rarely. At
    first I had no clue what was happening and would reboot to get back to normal before I discovered that I could get back to normal by typing
    reset at the prompt. Looks much better now.. :)

    Yeah, it was new to me too, I had encountered it in the pastt when
    'cat'-ing binary files, and never new how to move back.

    Andrew

    --- MagickaBBS v0.13alpha (Linux/x86_64)
    * Origin: HappyLand - telnet://magickabbs.com:2023/ (21:1/126)
  • From Oli@21:1/151 to apam on Sun Oct 27 13:54:33 2019
    It does, I just updated and had a look at that message with no trouble.

    I first encountered this maybe 15 years ago. It happens rarely. At
    first I had no clue what was happening and would reboot to get back to
    normal before I discovered that I could get back to normal by typing
    reset at the prompt. Looks much better now.. :)

    Yeah, it was new to me too, I had encountered it in the pastt when 'cat'-ing binary files, and never new how to move back.

    Now I know why this sometimes happens :). I always wondered why trying to display some binary data can mess up my terminal.

    ---
    * Origin: (21:1/151)