Subj : UTF-8 nodelist report
To   : Nicholas Boel
From : Sergey Dorofeev
Date : Sat Mar 15 2025 04:27 am

Hello Nicholas,

orig.message to echo UTF-8 on 14 Mar 25  18:52:22
NB> This is true, however.. that's the fault of those sysops. I've found the
NB> best working method has been to 'assume' any message with *no* chrs kludge
NB> is CP437, since it probably comes from a BBS package with ANSI support.

Not so easy for me. At first, I must distinguish CP866 and CP437.
At second, there is a little fraction of messages with latin-1 encoding - not so serious, but some symbols got trashed if wrong charset choosed.
There was messages in encoding that I call "fido-relics" - with 8D byte used as soft-CR.
And some amount of messages with encodings such as CP1125 - if decoded as CP866 some letters are displayed wrong.
Using that fact that each echo area has own language - I use per-echo default encodings.

Sergey

... vim
--- PyFTN
* Origin: fluid.fidoman.ru (2:5020/12000)

You are viewing proxied material from cvs.synchro.net. The copyright of proxied material belongs to its original authors. Any comments or complaints in relation to proxied material should be directed to the original authors of the content concerned. Please see the disclaimer for more details.