Gnus development mailing list
 help / color / mirror / Atom feed
From: Russ Allbery <eagle@eyrie.org>
To: ding@gnus.org
Subject: Re: nntp servers with multibyte group names?
Date: Tue, 27 Nov 2018 16:44:39 -0800	[thread overview]
Message-ID: <878t1eni88.fsf@hope.eyrie.org> (raw)
In-Reply-To: <87in0i5l6h.fsf@tullinup.koldfront.dk> ("Adam =?utf-8?Q?Sj?= =?utf-8?Q?=C3=B8gren=22's?= message of "Tue, 27 Nov 2018 21:18:14 +0100")

Adam Sjøgren <asjo@koldfront.dk> writes:

> According to RFC 3977 (Network News Transfer Protocol (NNTP)):

>   "o  Although this specification allows UTF-8 for newsgroup names, they
>       SHOULD be restricted to US-ASCII until a successor to RFC 1036
>       [RFC1036] standardises another approach. 8-bit encodings SHOULD
>       NOT be used because they are likely to cause interoperability
>       problems."

>      - https://tools.ietf.org/html/rfc3977#section-10

For a bit of background here, non-ASCII newsgroup names mostly work, and
are even used in some areas, but we saw a few instances of strange
behavior in some experiments.  However, putting raw UTF-8 directly into
the Newsgroups header breaks compatibility with RFC 5322 (email), which
prohibits non-ASCII characters in headers.

Email would say that you should MIME-encode those names, but that will
definitely break all Usenet software, which assumes that Newsgroups are
byte strings that don't require any further interpretation.  (And some of
the encoding characters are invalid in newsgroup names, I believe.)

We weren't able to find a good reconciliation of that conflict before the
IETF working group ran out of steam.

So you can probably just use raw UTF-8 directly in newsgroup names with a
local server, but expect some strangeness with some clients, and you are
(for whatever it's worth) breaking compatibility with the email standards
by doing so.

-- 
Russ Allbery (eagle@eyrie.org)              <http://www.eyrie.org/~eagle/>



  parent reply	other threads:[~2018-11-28  0:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-27 19:55 Eric Abrahamsen
2018-11-27 20:18 ` Adam Sjøgren
2018-11-27 20:20   ` Eric Abrahamsen
2018-11-27 20:34     ` Adam Sjøgren
2018-11-27 20:54       ` Eric Abrahamsen
2018-11-27 21:02         ` Adam Sjøgren
2018-11-27 21:07           ` Eric Abrahamsen
2018-11-28  0:44   ` Russ Allbery [this message]
2018-11-28  1:03     ` Eric Abrahamsen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=878t1eni88.fsf@hope.eyrie.org \
    --to=eagle@eyrie.org \
    --cc=ding@gnus.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).