Hello Karel.

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

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

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

 KK> Just did, but no improvement. Would it be possible that old messages
 KK> 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.

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

 KK> I am not sure that is just my XLAT setup or BASH env. Interesting is,
 KK> that it is only subject (message is OK). What is difference for XLAT
 KK> in Subj and in Message? Why one UTF-8 is OK a different is not (UTF-8
 KK> 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.

 KK> And there was another collegue who has same issue (assume different
 KK> 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