MV> All I can say is that I have never seen a message encoded in CP1251 in MV> Fidonet. What I see is CP437, CP850, Latin-1, and CP866.
A decade ago KOI8-R/KOI8-U messages were pretty common in some areas. Today many non-windows users still setups their golded for KOI8-R<->CP866 recoding despite the fact that most of them also use luit/screen/terminal translator for UTF-8.
MV> While it is true that most of the World Wide Web has migrated to UTF-8, MV> we should keep in mind that Fidonet is not the Internet. As you have MV> pointed out, the vast majority of Fidonet messages still use 8 bit MV> encoding. The UTF-8 evangelists in here may wish it different, but the MV> reality is that we still have a long way to go before UTF-8 will be the MV> dominant encoding for Fidonet and it is quit likely that will never happen.
If we want for widespread UTF-8 usage in fidonet then we must fix the lack of unicode-capable editors first. Especially console ones. Currently there are basically only msged which after golded is too limited and ugly. After that enforce UTF-8 usage on echoes distributed through backbones. Don't accept echoes with rules restricting writing to specific 8bit codepages. Treat complains about not being able to read UTF-8 messages as 1.3.5. If there are enough UTF-8 traffic users will switch to unicode-capable software and the problem will be solved.
But in reality it is not much easier than adopt new fidonet policy.
KK>> If you don't care that you messages could not be read correctly then KK>> you can continue to write with bogus or missing codepage information. KK>> But if it was in my power I would have restricted such traffic and KK>> treat it as a case of 1.3.5 with all its consequences. MV> See the new area rules published earier today.
He-he... Nice one. ^_^
But I talked about more higher level restriction. Like treat it as technical violation in any echoarea and if writers of such messages doesn't want to fix that problem than just excommunicate them.
P.S. What's written there? MV> * Origin: Blóf Tønón
There are some strange 0x7F character: 0620 20 4F 72 69 67 69 6E 3A 20 42 6C 7F C3 B3 66 20 0630 54 C3 B8 6E 7F C3 B3 6E 20 28 32 3A 32 38 30 2F
--- Claws Mail 3.14.0 (GTK+ 2.24.30; x86_64-pc-linux-gnu) * Origin: Via 2:5019/40 NNTP (GaNJaNET STaTi0N, Smolensk) (2:5019/40.1)
