MSGID: 2:221/6.0 66e9d890
REPLY: 2:5023/24.4222 66e7c52e
PID: SmapiNNTPd/Linux/IPv6 kco 20240915
NOTE: tin/2.6.2-20221225 ("Pittyvaich") (Linux/6.10.8-100.fc39.x86_64
(x86_64))
CHRS: LATIN-1 2
TZUTC: 0300
TID: hpt/lnx 1.9 2024-03-02
Gale Hlebov <4222@24.5023.2> wrote:
>  wrote:
>
>> I ask this question here simply because on this machine I cannot read
>> or write Russian-language FidoNet articles (yet). What is the default
>> encoding of a Russian FidoNet message, the one assmed in default of a
>> CHRS cludge? Is it koi8-r or 866?
>
> It's set to 866 in its "native" software.
> If you're using an NNTP client under Linux it should be KOI8-R.

How can it be determined by the OS and protocol? I thought the required
encoding depended on the settings of the NNTP gateway...

> For tin, add/edit the line in tinrc as follows:
>
> mm_network_charset=koi8-r

Thank you.  This options lets me read Russian Fidonet echoes on this
server, but I still cannot post.  Although I made sure my editor (Vim)
saves the files in koi8-r (set fenc=koi8-r), Tin warns me that I am
posting in UTF-8 and replaces the Russian characters with question
marks...

--- 
 * Origin: nntp://news.fidonet.fi (2:221/6.0)
SEEN-BY: 1/19 16/0 19/37 90/1 105/81 106/201 123/130 129/305 142/104
SEEN-BY: 153/757 7715 154/10 203/0 218/700 840 221/1 6 360 226/30
SEEN-BY: 227/114 229/110 114 206 300 317 426 428 470 664 700 240/5832
SEEN-BY: 266/512 280/5003 282/1038 291/111 301/1 320/119 219 319 2119
SEEN-BY: 322/757 762 335/364 341/66 234 342/200 396/45 423/81 460/58
SEEN-BY: 712/848 5020/400 1042 5075/35
PATH: 221/6 1 320/219 229/426