home bbs files messages ]

Just a sample of the Echomail archive

<< oldest | < older | list | newer > | newest >> ]

 Message 2329 
 Karel Kral to Vitaliy Aksyonov 
 Re: Latest ses..es.. 
 10 Mar 24 14:09:35 
 
REPLY: 1:104/117 65ecbd40
MSGID: 2:423/39 65edb110
CHRS: LATIN-2 2
TZUTC: 0100
TID: CrashMail II/Linux 0.62
Hello Vitaliy!

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

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

 VA> What does it show if you run:
 VA> 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=

 VA> Also try to run:
 VA> locale -a

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


 VA> 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

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

It is working for me in local, czech echomail.

 VA> As for UTF - it's not supported and might "work" if you do some weird
 VA> setup, but I'd not count on it. Better work in one-byte locales like
 VA> 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.

 VA> I totally understand you. I spend several days before my system
 VA> 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)
SEEN-BY: 15/0 18/200 90/1 103/705 105/81 106/201 124/5016 128/260
SEEN-BY: 129/305 135/225 153/757 7715 154/10 30 203/0 218/700 221/1
SEEN-BY: 221/6 360 226/30 227/114 229/110 112 113 206 307 317 400
SEEN-BY: 229/426 428 470 664 700 240/1120 5832 266/512 280/464 5003
SEEN-BY: 280/5555 282/1038 291/111 292/854 8125 301/1 310/31 320/219
SEEN-BY: 322/757 341/66 234 342/200 396/45 420/33 333 421/79 83 423/39
SEEN-BY: 423/81 120 121 460/16 58 256 1124 5858 467/888 633/280 712/848
SEEN-BY: 770/1 5020/400 1042 5054/30
PATH: 423/39 81 221/1 280/464 460/58 229/426


<< oldest | < older | list | newer > | newest >> ]

(c) 1994,  bbs@darkrealms.ca