Bug#593909: Names of Fields in Control Files
Charles Plessy <plessy@debian.org> writes:
> Here is an updated patch, that contains the following:
> 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. It ends at
> - the end of the (logical) line. Horizontal whitespace
> + then the data/value associated with that field. The field
> + name is composed of printable ASCII characters (i.e.,
> + characters that have values between 33 and 126, inclusive)
> + except colon and must not with a begin with #. The
> + field ends at the end of the line or at the end of the
> + last continuation line (see below). Horizontal whitespace
> (spaces and tabs) may occur immediately before or after the
> value and is ignored there; it is conventional to put a
> Apart from adding that fields names may not begin with #, I also changed
> ‘US-ASCII’ for ‘ASCII’, since this is the vocabulary used by the Policy.
And, for the record, seconding this combined patch. Thank you for all
your work on this!
--
Russ Allbery (rra@debian.org) <http://www.eyrie.org/~eagle/>
Reply to: