1. Forum
  2. FidoNet Int
  3. fidotest

  • it's UTF-8 without proper CHRS kludge..

    From August Abolins@1:153/757.21 to Tommi Koivula on Sun Jan 18 13:15:00 2026
    Hello Tommi!

    ** On Saturday 17.01.26 - 11:36, Tommi Koivula wrote to Ivan Zelenyi:

    ¿Qué cigüeña voló aún más ahí?

    Nothing readable.

    It's UTF-8 charset

    ...which should never be used without a proper CHRS kludge. ;)


    Hopefully he'll add that when he can.

    As for me, I don't think UTF-8 can ever be a thing inside OpenXP, although I see many references to UTF-8 in the .PAS code. And..I "think" UTF-8 gets used for messages going out via the NNTP system here.

    --
    ../|ug

    --- OpenXP 5.0.64
    * Origin: The ONLY point that matters --> . <-- (1:153/757.21)
  • From Matthew Asham@1:153/149.42 to August Abolins on Tue Jan 20 01:35:17 2026
    Hopefully he'll add that when he can.
    As for me, I don't think UTF-8 can ever be a thing inside OpenXP, although I
    see many references to UTF-8 in the .PAS code. And..I "think" UTF-8 gets
    used for messages going out via the NNTP system here.

    This message should have the CHRS UTF-8 kludge. Not sure this is the right approach though, maybe just plain old ASCII?

    "What could possibly go wrong!"

    Matthew

    --- BinktermPHP v1.6.4
    * Origin: myPoint System - https://mypoint.lovelybits.org (1:153/149.42)
  • From Carlos Navarro@1:153/149.42 to Matthew Asham on Tue Jan 20 02:50:20 2026
    --- Original Message ---
    From: Matthew Asham
    Date: 2026-01-20 09:35:17.835038
    Subject: Re: it's UTF-8 without proper CHRS kludge..

    This message should have the CHRS UTF-8 kludge. Not sure this is the right approach though, maybe just plain old ASCII?
    "What could possibly go wrong!"

    Yes, it's there.

    So this message should have it too and this dummy text should be readable for UTF-8 capable editors:

    ¿Qué cigüeña voló aún más ahí?


    --- BinktermPHP v1.6.4
    * Origin: myPoint System - https://mypoint.lovelybits.org (1:153/149.42)
  • From Tommi Koivula@2:221/0 to Carlos Navarro on Tue Jan 20 22:00:04 2026
    On 20/01/2026 10.50, Carlos Navarro wrote:
    --- Original Message ---
    From: Matthew Asham
    Date: 2026-01-20 09:35:17.835038
    Subject: Re: it's UTF-8 without proper CHRS kludge..

    This message should have the CHRS UTF-8 kludge. Not sure this is
    the right approach though, maybe just plain old ASCII?
    "What could possibly go wrong!"

    Yes, it's there.

    So this message should have it too and this dummy text should be
    readable for UTF-8 capable editors:

    Yes.


    ¿Qué cigüeña voló aún más ahí?

    Looks fine. :)


    --- BinktermPHP v1.6.4
    * Origin: myPoint System - https://mypoint.lovelybits.org (1:153/149.42)

    ---
    * Origin: smapinntpd/lnx (2:221/0.0)
  • From Nick Boel@1:154/700 to Matthew Asham on Tue Jan 20 16:21:47 2026
    Hey Matthew!

    On Tue, Jan 20 2026 03:35:17 -0600, you wrote:

    This message should have the CHRS UTF-8 kludge. Not sure this is
    the right approach though, maybe just plain old ASCII?

    Yep, it has the CHRS kludge.

    However, if you want to get technical, you should send the CHRS kludge that coincides with the message written. If the message includes UTF-8, then send the CHRS: UTF-8 kludge. If it contains CP437 characters, then it should be sent with the CHRS: CP437 kludge, etc.

    UTF-8 also works for, and completely covers ASCII.. so it is still valid in this case.

    In most of my setups outside of my BBS itself, I just convert everything to UTF-8, and always send that kludge. YMMV, though.

    Regards,
    Nick

    ... Sarcasm, because beating people up is illegal.
    --- SBBSecho 3.34-Linux
    * Origin: _thePharcyde telnet://bbs.pharcyde.org (Wisconsin) (1:154/700)