Gnus development mailing list
 help / color / mirror / Atom feed
From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: ding@gnus.org
Subject: Re: nntp servers with multibyte group names?
Date: Tue, 27 Nov 2018 12:20:48 -0800	[thread overview]
Message-ID: <87ftvm6zmn.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <87in0i5l6h.fsf@tullinup.koldfront.dk>

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

> Eric writes:
>
>> I'd like to test this with the nntp backend, but I don't actually know
>> if nntp is allowed to have multibyte group names. I've gone browsing
>> through some publicly-accessible nntp servers and haven't found anything
>> but ascii-compatible group names, even for servers at, eg, Taiwanese
>> universities.
>>
>> Are multibyte group names even legal?
>
> 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

Interesting! Thanks for that (I guess I could have looked that up
myself). I will assume for now that group names are coming in as ascii,
but maybe leave a note in the code.

Eric




  reply	other threads:[~2018-11-27 20:20 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 [this message]
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
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=87ftvm6zmn.fsf@ericabrahamsen.net \
    --to=eric@ericabrahamsen.net \
    --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).