Bug#647645: More precise reference to ASCII characters, and few phrasing issues
Charles Plessy wrote:
> Each paragraph consists of a series of data fields; each
> field consists of the field name, followed by a colon and
> then the data/value associated with that field. The field
> name MUST be composed of US-ASCII characters excluding
> control characters, space and colon (i.e., characters in the
> ranges 33–57 and 59–126, inclusive). In addition, they
> MUST NOT begin with a hash character (<tt>#</tt>).
Given that # here would comment out the line, perhaps we could avoid
needing to reveal its true name and just say "MUST NOT begin with the
comment character, <tt>#</tt>".
And just in case it's not 100% clear that tab and newline are control
characters, you might say "control characters, whitespace and colon"
(I would normally use "serial comma" there, but Policy tends not to,
and I don't want to start nitpicking.)
> By the way, is ‘consists of a series of data fields’ gramatically correct ?
Yes, that's fine.
JBR with qualifications in linguistics, experience as a Debian
sysadmin, and probably no clue about this particular package