ietf-nntp Overview and non-printing characters

Clive D.W. Feather clive at demon.net
Mon Jul 9 01:50:35 PDT 2001


Russ Allbery said:
> In reviewing the draft, I found that we'd not yet resolved the previous
> discussion of overview and we still have the original text in the draft
> regarding how to generate overview information:
> 
>     Any sequence of US-ASCII space or non-printing characters in a field
>     MUST be replaced by a single US-ASCII space.
[...]

I'm generally happy with your suggested changes.

I'd like to specifically point out that Usefor is moving to UTF-8 encoding
for articles. This means that octets 128 to 255 will be part of this data,
and it is important that people do *not* think that "US-ASCII non-printing"
includes such characters. Your changes do this; let's make sure it doesn't
accidentally get undone at a later date.

-- 
Clive D.W. Feather  | Work:  <clive at demon.net>   | Tel:  +44 20 8371 1138
Internet Expert     | Home:  <clive at davros.org>  | Fax:  +44 20 8371 1037
Demon Internet      | WWW: http://www.davros.org | DFax: +44 20 8371 4037
Thus plc            |                            | Mobile: +44 7973 377646



More information about the ietf-nntp mailing list