• Latest ses..es..

    From Karel Kral@2:423/39 to Vitaliy Aksyonov on Fri Mar 8 07:30:42 2024
    Hello Vitaliy!

    07 Mar 24 17:08, you wrote to me:

    Try to set LANG to cs_CZ.ISO8859-2 and that will solve your issue! No
    need to set it for the whole system. Just for golded session.

    $ LANG=cs_CZ.ISO8859-2 luit -encoding 'ISO-8859-2' ./gedlnx -f

    Just did, but no improvement. Would it be possible that old messages are alreadu scrambled and I have to wait for new examples?

    Your problem is that luit converts symbols from 8859-2 to UTF, but
    ncurses tries to work in UTF-8 mode because you have LANG=cs_CZ.utf8.

    I am not sure that is just my XLAT setup or BASH env. Interesting is, that it is only subject (message is OK). What is difference for XLAT in Subj and in Message? Why one UTF-8 is OK a different is not (UTF-8 4 against UFT-8 2)?

    And there was another collegue who has same issue (assume different setup).

    Karel

    --- GoldED+/LNX 1.1.5-b20240209
    * Origin: Plast DATA (2:423/39)
  • From Vitaliy Aksyonov@1:104/117 to Karel Kral on Sat Mar 9 12:44:28 2024
    Hello Karel.

    08 Mar 24 07:30, you wrote to me:

    Try to set LANG to cs_CZ.ISO8859-2 and that will solve your
    issue! No need to set it for the whole system. Just for golded
    session.

    $ LANG=cs_CZ.ISO8859-2 luit -encoding 'ISO-8859-2' ./gedlnx -f

    Just did, but no improvement. Would it be possible that old messages
    are alreadu scrambled and I have to wait for new examples?

    Could you please make sure that your system actually has such locale?

    What does it show if you run:
    LANG=cs_CZ.ISO8859-2 locale

    Also try to run:
    locale -a

    If it doesn't show that locale - you need to install or generate it. Each linux distro has own way to do it, but that's easy to google.

    Your problem is that luit converts symbols from 8859-2 to UTF,
    but ncurses tries to work in UTF-8 mode because you have
    LANG=cs_CZ.utf8.

    I am not sure that is just my XLAT setup or BASH env. Interesting is,
    that it is only subject (message is OK). What is difference for XLAT
    in Subj and in Message? Why one UTF-8 is OK a different is not (UTF-8
    4 against UFT-8 2)?

    It could be both. Could you please show your xlat setup?

    BTW, luit works for me. Only difference is that my FidoNet charset is KOI8-r.

    As for UTF - it's not supported and might "work" if you do some weird setup, but I'd not count on it. Better work in one-byte locales like cp437 or ISO8859-2 in your case.

    And there was another collegue who has same issue (assume different setup).

    I totally understand you. I spend several days before my system started to work OK. Will try to resolve your issues. :)

    Vitaliy

    ... 640K ought to be enough for anybody
    --- GoldED+/LNX 1.1.5-b20240305-beta
    * Origin: Aurora, Colorado (1:104/117)
  • From Karel Kral@2:423/39 to Vitaliy Aksyonov on Sun Mar 10 14:09:35 2024
    Hello Vitaliy!

    09 Mar 24 12:44, you wrote to me:

    Could you please make sure that your system actually has such locale?

    What does it show if you run:
    LANG=cs_CZ.ISO8859-2 locale

    .. LANG=cs_CZ.ISO8859-2 locale
    LANG=cs_CZ.ISO8859-2
    LC_CTYPE="cs_CZ.ISO8859-2"
    LC_NUMERIC="cs_CZ.ISO8859-2"
    LC_TIME="cs_CZ.ISO8859-2"
    LC_COLLATE="cs_CZ.ISO8859-2"
    LC_MONETARY="cs_CZ.ISO8859-2"
    LC_MESSAGES="cs_CZ.ISO8859-2"
    LC_PAPER="cs_CZ.ISO8859-2"
    LC_NAME="cs_CZ.ISO8859-2"
    LC_ADDRESS="cs_CZ.ISO8859-2"
    LC_TELEPHONE="cs_CZ.ISO8859-2"
    LC_MEASUREMENT="cs_CZ.ISO8859-2"
    LC_IDENTIFICATION="cs_CZ.ISO8859-2"
    LC_ALL=

    Also try to run:
    locale -a

    .. locale -a | grep cs_CZ
    cs_CZ
    cs_CZ.iso88592
    cs_CZ.utf8


    It could be both. Could you please show your xlat setup?

    GOLDED is showed as Group B
    in cfg (this is the latest, changed also based on the latest advice)

    GROUP B
    XLATPATH /home/fido/golded/xlat
    XLATCHARSET CP437 LATIN-2 asc_il2.chs
    XLATCHARSET LATIN-2 CP437 il2_asc.chs
    XLATCHARSET CP437 UTF-8 437_u8.chs
    XLATIMPORT CP437
    XLATIMPORT CP437
    XLATLOCALSET LATIN-2
    MSGLISTWIDESUBJ YES
    ENDGROUP

    BTW, luit works for me. Only difference is that my FidoNet charset is KOI8-r.

    It is working for me in local, czech echomail.

    As for UTF - it's not supported and might "work" if you do some weird setup, but I'd not count on it. Better work in one-byte locales like
    cp437 or ISO8859-2 in your case.

    Where I am reading, usualy they use English. Then pure ASCII should be enough. And I would be OK even for some exceptional scrambled messages. But why some Subject lines are impacted? I see whole message OK, just that line has copied over 4 bytes. Always the same position.

    I totally understand you. I spend several days before my system
    started to work OK. Will try to resolve your issues. :)

    No problem. Have that since years. I just started to wonder if somebody else can see that. Take is as the lowest prio.

    I checked code already, for some "quick win" - but I am not c-guy = nothing found by myself.

    Thank you for any help.

    Karel

    --- GoldED+/LNX 1.1.5-b20240209
    * Origin: Plast DATA (2:423/39)