On Wed, Jan 14, 2009 at 10:26:03PM -0800, Russ Allbery wrote:
> I'm leaning that way as well. I also don't want to require people to use
> RFC 2047 encoding if they have a name that doesn't fit into ASCII.
>
> Anyone have any suggestions on a good subset and description of it that
> isn't too complex?
While I think it would be fine to have a comprehensive and accurate
specification, something like this could be an easy improvement.
By omitting mention of RFC 822, the mandate for UTF-8 in the control
file should obviate RFC 2047 encoding.
Despite underspecifying things, I doubt there will be anyone trying
to use email addresses of the wrong form.
diff --git a/policy.sgml b/policy.sgml
index 7de382d..080229c 100644
--- a/policy.sgml
+++ b/policy.sgml
@@ -2582,17 +2582,14 @@ Package: libc6
<p>
The package maintainer's name and email address. The name
should come first, then the email address inside angle
- brackets <tt><></tt> (in RFC822 format).
+ brackets <tt><></tt>.
</p>
<p>
- If the maintainer's name contains a full stop then the
- whole field will not work directly as an email address due
- to a misfeature in the syntax specified in RFC822; a
- program using this field as an address must check for this
- and correct the problem if necessary (for example by
- putting the name in round brackets and moving it to the
- end, and bringing the email address forward).
+ If the maintainer's name contains a full stop or a comma,
+ the entire name must either be surrounded by quotation marks
+ or put within round brackets and moved it to the end
+ (thus bringing the email address forward).
</p>
</sect1>
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
