• Russian encodings KOI8-RU and KOI8-R

    From Anton Shepelev@anton.txt@gmail.moc to news.software.readers on Thu Sep 19 17:07:38 2024
    From Newsgroup: news.software.readers

    The MM_NETWORK_CHARSET parameter in the interactive menu of Tin 2.6.3
    contains the following entries, in this order:

    1. KOI8-RU
    2. KOI8-R

    The standard and widely supported KOI8-R encoding is listed after
    its much rare derivative, which may confuse the user as did me,
    because even we Russians are hardly unaware of KOI8-RU. When I first
    saw it in tin, I thought it was a sort of prettified name for KOI8-R,
    intended to emphasize its relation to the RUssian language. But I
    learned better when the NNPT server rejected my article on the
    ground of an invalid charset.

    May I propose that the order of these entries in the interactive
    menu be reversed, and the standard KOI8-R encoding placed first?
    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From Urs =?UTF-8?Q?Jan=C3=9Fen?=@urs@buil.tin.org to news.software.readers on Thu Sep 19 18:22:35 2024
    From Newsgroup: news.software.readers

    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. but it's more likely that
    other charsets than US-ASCII and UTF-8 will be dropped. so: no.
    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From Anton Shepelev@anton.txt@gmail.moc to news.software.readers on Thu Sep 19 18:33:41 2024
    From Newsgroup: news.software.readers

    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.
    --- Synchronet 3.21a-Linux NewsLink 1.2