From: Charles Lindsey (chl@clw.cs.man.ac.uk)
Date: Wed Jul 24 2002 - 09:41:56 CDT
On Wed, 24 Jul 2002 10:10:24 +0200
Frank.Ellermann@t-online.de (Frank Ellermann) said...
>
> Charles Lindsey wrote in <200207041524.QAA08572@clw.cs.man.ac.uk>:
>
> > 2. Each octet in the name in the range 0x80-ff is replaced by a "%"
> > character, followed by two characters representing that octet in
> > hexadecimal, in which the hexadecimal digits "a" through "f" MUST
> > be in lowercase.
> >
> > 3. Each octet in the name in the range 0x00-7f remains unaltered (and
> > thus MUST NOT be replaced by its hexadecimal equivalent).
>
> Silly, because it's implicitly impossible, but you might want
> to move "%" (%25) from set 3 to set 2.
The question does not arise because "%" is not allowed as a character in
a newsgroup-name. And if one should inadvertently appear, it is probably
left alone so that it remains looking like an obvious error.
> I tried to understand
> why you didn't use UTF-7 for this problem, and found some old
> messages from 1999 about it in your archive... ;-)
There is general agreement that UTF-7 is an interesting experiment that
is best forgitten about.
BTW, you seeme to be sending your replies durect to me, but not to the List.
>
> BTW, my good old netscape 3 allows me to send a mail copy (CC:)
> of any news message, and the mail then includes both Newsgroups:
> and Followup-To: headers.
>
> So Followup-To: has to be encoded too, if necessary. That's
> of course also true for mails sent to moderatored newsgroups
> including a Followup-To: header.
Yes, I have covered that in the Duties of an Injecting agent, but it
needs to be mentioned in 5.5.2 as well. So it now says:
Where it is required to transport an article across some medium that
cannot reliably convey the full 8 bits of each octet, such as when
gatewaying it into Email (8.8.1), or when emailing it to a moderator
or constructing the submission address of the moderator (8.2.2), it
may be necessary to encode any newsgroup-name within a Newsgroups- or
Followup-To-header that contains any non-ASCII character. For that
purpose, the following algorithm is provided:
Actually, it can also occur in a newgroup control message, but I have
not bothered to mention that because you aren't supposed to pass those
through gateways anyway.
Charles H. Lindsey ---------At Home, doing my own thing------------------------
Tel: +44 161 436 6131 Fax: +44 161 436 6133 Web: http://www.cs.man.ac.uk/~chl
Email: chl@clw.cs.man.ac.uk Snail: 5 Clerewood Ave, CHEADLE, SK8 3JU, U.K.
PGP: 2C15F1A9 Fingerprint: 73 6D C2 51 93 A0 01 E7 65 E8 64 7E 14 A4 AB A5