Subj : UTF-8 nodelist report
To   : Sergey Dorofeev
From : Nicholas Boel
Date : Fri Mar 14 2025 06:52 pm

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)

.