On Mon, May 11, 2015 at 08:33:09AM +0000, Debian Bug Tracking System wrote:
> The current Policy (since 3.8.1.0) says "All control files must be encoded > in UTF-8." and the current practice is to use UTF-8 in Maintainer: field > values. Hello, my intention with this bug was to ask to clarify how entries in Uploaders: fields should be split, and I do not see how UTF-8 encoding can help with that. I checked version 3.9.6.1, and the policy still says this for the Uploader: field: > The format is the same as that of the Maintainer tag, and multiple > entries should be comma separated. So according to that definition, a field like: Uploaders: Adam C. Powell, IV <hazel...@debian.org> is a field with a list of two values: "Adam C. Powell" and "IV <hazel...@debian.org>", one of which is illegal becaues it contains no email address inside angle brackets. However, the Maintainer: field has only one value, so it does not mention how commas can be represented in its value without being confused with separators. I would like the Uploaders: field to clarify how one can have a comma in the name without triggering a split. There can be several strategies: - it could say that commas are not allowed at all in an Uploaders: field, except as separators; - it could say that one needs to double quote a name that contains commas; - it could say that the separator is a comma only if it is preceded by a closed angle bracket and optional spaces: this would be the option that is harder to implement, but that keeps Adam's packages policy compliant. I assume this is an effect of this bug having been merged with 160827 and 160827 having been closed. I've unmerged them and reopened this one, as this does not have anything to do with charset encoding. Enrico -- GPG key: 4096R/E7AD5568 2009-05-08 Enrico Zini <enr...@enricozini.org>
signature.asc
Description: Digital signature
