Path: ...!3.eu.feeder.erje.net!feeder.erje.net!newsfeed.bofh.team!paganini.bofh.team!not-for-mail
From: Anton Shepelev <anton.txt@gmail.moc>
Newsgroups: news.software.readers
Subject: Re: Russian encodings KOI8-RU and KOI8-R
Date: Thu, 19 Sep 2024 18:33:41 -0000 (UTC)
Organization: To protect and to server
Sender: 9dIQLXBM7WM9KzA+yjdR4A
Message-ID: <vchqq5$1bq8p$1@paganini.bofh.team>
References: <vchloq$1bijt$1@paganini.bofh.team> <vchq5b$4sm$1@nntp.de>
Injection-Date: Thu, 19 Sep 2024 18:33:41 -0000 (UTC)
Injection-Info: paganini.bofh.team; logging-data="1435929"; posting-host="RuGtXskjILadxbC+FS6/9w.user.paganini.bofh.team"; mail-complaints-to="usenet@bofh.team"; posting-account="9dIQLXBM7WM9KzA+yjdR4A";
User-Agent: tin/2.6.3-20231224 ("Banff") (FreeBSD/14.1-RELEASE (amd64))
X-Notice: Filtered by postfilter v. 0.9.3
Bytes: 1752
Lines: 20

Urs Janssen <urs@buil.tin.org> wrote:

> Anton Shepelev wrote:
>> May I propose that the order of these entries in the interactive
>> menu be reversed, and the standard KOI8-R encoding placed first?
> 
> The manpage states which charsetrs are available as mm_network_charset.
> If there ever will be a change in the order exotics like KOI8-* would go
> the end and UTF-8 would be moved forward. 

You misunderstood: I meant only to swap the /relative/ positions of
KOI-RU and KOI8-R, so that the standard and widely supported encoding
KOI8-R should go before the less standard and rarely supported
KOI8-RU.  Of course, neither of them should be at the head of the
list.

> but it's more likely that other charsets than US-ASCII and
> UTF-8 will be dropped. so: no.

Then Tin will become useless with Russian FidoNet echoes gated
through NNTP.