Am 31.08.12 15:57, schrieb Nick Coghlan:
However, also +1 on using "/" as the extension separator to avoid
ambiguity in field names, as well as restoring the explicit
requirement that metadata entries use valid RFC 822 metasyntax.
Unfortunately, this conflicts with the desire to use UTF-8 in attribute
values - RFC 822 (and also 2822) don't support this, but require the
use oF MIME instead (Q or B encoding).
RFC 2822 also has a continuation line semantics which traditionally
conflicts with the metadata; in particular, line breaks cannot be
represented (but are interpreted as continuation lines instead).
OTOH, several of the metadata fields do require line breaks, in
particular those formatted as ReST.
Regards,
Martin
_______________________________________________
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
