1. Forum
  2. Fidonet
  3. ALT.BBS.MYSTIC

  • =?UTF-8?Q?UTF8_special_chars_=28=C3=BC=2C=C3=A4=2C=C3=B6=29_broken_when

    From gierig kitty@3:633/280.2 to All on Thu May 4 00:16:59 2023
    Subject: =?UTF-8?Q?UTF8_special_chars_=28=C3=BC=2C=C3=A4=2C=C3=B6=29_broken_when_sending_to?=
    =?UTF-8?Q?_BBS_in_1=2E12_A48?=

    Hey,=20

    new guy here (run a maximus bbs 25 years ago and return as im old :-)

    Setting up Mystic on Linux (Debian 11) and running some test if
    that BBS system meets my expectations (beautiful pice of software=20
    so far). So I run it atm out the box.

    First in CP437 Mode ("Default Code Page" and "Ask Code page" to =E2=80=9ECP= 437=E2=80=9C) and access with CP437 Settings (via syncterm, putty, iterm2)=
    everything is working fine and look nice.

    Switch to UTF8 (settings on Mystic and in terminal as well)
    Still ALL is working fine, looks nice and feels good.

    Till I try to type in special Character like =C3=BC,=C3=A4,=C3=B6,=C2=A7. T= hat Display
    on screen as =E2=94=9C=E2=95=9D=E2=94=9C=C3=B1=E2=94=9C=E2=95=A2

    that happen everywhere. So in Login Screen for name,=20
    in config Mode (path settings), when writing a Massages.
    even in texteditor (./mystic -text). even in local Mode

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

    Bug Future ? Only affect me ?=20

    greets from Germany.
    marc

    =20



    --- MBSE BBS v1.0.8 (Linux-x86_64)
    * Origin: ---:- FTN<->UseNet Gate -:--- (3:633/280.2@fidonet)
  • From g00r00@1:129/215 to gierig kitty on Wed May 3 20:21:48 2023
    Subject: Re: =?UTF-8?Q?UTF8_special_chars_=28=C3=BC=2C=C3=A4=2C=C3=B6=29_broken

    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


    --- MBSE BBS v1.0.8 (Linux-x86_64)
    * Origin: Agency HUB, Dunedin - New Zealand (1:129/215@fidonet)
  • From Robert Wolfe@1:116/17 to g00r00 on Tue May 9 14:07:51 2023
    Subject: Re: =?UTF-8?Q?UTF8_special_chars_=28=C3=BC=2C=C3=A4=2C=C3=B6=29_broken

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

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

    just snagged this.


    --- MBSE BBS v1.0.8 (Linux-x86_64)
    * Origin: Agency HUB, Dunedin - New Zealand (1:116/17@fidonet)
  • From gierig kitty@3:633/280.2 to All on Fri May 12 20:24:06 2023
    Subject: Re: =?UTF-8?Q?UTF8_special_chars_=28=C3=BC=2C=C3=A4=2C=C3=B6=29_broken

    just snagged this.

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

    Also a further test.. it=E2=80=99s only affect higer Ascii. All =E2=80=9E7 = bit=E2=80=9C ascii work fine as UFT Coding,=20
    bit anything above get back crappy..

    so even =E2=80=9E=C2=A7" =E2=80=9E=C2=B5=E2=80=9C =E2=80=9E=C3=9F=E2=80=9C

    --- MBSE BBS v1.0.8 (Linux-x86_64)
    * Origin: ---:- FTN<->UseNet Gate -:--- (3:633/280.2@fidonet)
  • From Marc Diring@3:633/280.2 to All on Fri May 12 22:32:33 2023
    Subject: Re:
    =?UTF-8?Q?UTF8_special_chars_=28=C3=BC=2C=C3=A4=2C=C3=B6=29_broken

    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



    --- MBSE BBS v1.0.8 (Linux-x86_64)
    * Origin: ---:- FTN<->UseNet Gate -:--- (3:633/280.2@fidonet)