REPLY: 2:5020/12000 4f53923a
MSGID: 1:154/10 67d4c548
CHRS: UTF-8 4
TZUTC: -0500
TID: hpt/lnx 1.9 2024-03-02
Hey Sergey!

On Fri, 14 Mar 2025 19:54:00 +0300, you wrote:

 > Not all sysops use correct CHRS kludge.

This is true, however.. that's the fault of those sysops. I've found the best
working method has been to 'assume' any message with *no* chrs kludge is
CP437, since it probably comes from a BBS package with ANSI support.

 > Moreover, there is some messages with two different charset (some
 > SYNCHRO users) - message itself in UTF-8, but tearline uses
 > CP437-encoded pseudographics.

Here's a couple links that addressed this issue.

https://gitlab.synchro.net/main/sbbs/-/issues/742
https://gitlab.synchro.net/main/sbbs/-/issues/842

Unfortunately, you can only try to get the hundreds of sysops using older
versions of Synchronet to update. Until then, the issue will remain. ;(

 NB>> Do you still translate all incoming mails to UTF-8 using iconv so
 NB>> they're readable?

 > Yes. But no external iconv, pyhton internal decode/encode.

I see. My best results seem to be with Linux terminal based NNTP clients
(slrn, tin, alpine, neomutt) that use iconv. I believe sometimes even when the
CHRS kludge is wrong, as long as the "Content-Type" field is correct, the
message still displays fine, since NNTP clients don't know what a CHRS kludge
is.

🖕_😁_🖕
   o
 _/ \_

;)

Regards,
Nick

... Sarcasm: because beating people up is illegal.
--- GoldED+/LNX 1.1.5-b20240309
 * Origin: _thePharcyde telnet://bbs.pharcyde.org (Wisconsin) (1:154/10)
SEEN-BY: 1/19 16/0 19/37 104/119 105/81 106/201 123/130 128/187 142/104
SEEN-BY: 153/757 7715 154/10 30 50 110 700 701 201/0 203/0 218/700
SEEN-BY: 218/840 220/20 221/1 6 242 360 226/30 44 50 227/114 229/110
SEEN-BY: 229/114 310 317 426 428 470 700 705 230/0 240/5832 280/464
SEEN-BY: 280/5003 5555 291/111 292/854 301/1 320/119 219 319 2119
SEEN-BY: 322/762 335/364 341/66 234 423/81 902/26 5020/1042
PATH: 154/10 221/6 1 320/219 229/426