updated spec to reflect that escaped colons inside of field

names are now allowed; added history entry

git-svn-id: http://svn.code.sf.net/p/docutils/code/trunk/docutils@4092 929543f6-e4f2-0310-98a6-ba3bd3dd1d04

1 files changed, 10 insertions, 9 deletions

diff --git a/docs/ref/rst/restructuredtext.txt b/docs/ref/rst/restructuredtext.txt
index d503d9054..e0cee6031 100644
--- a/docs/ref/rst/restructuredtext.txt
+++ b/docs/ref/rst/restructuredtext.txt
@@ -813,15 +813,16 @@ see `Bibliographic Fields`_ below, or the "image_" and "meta_"
 directives in `reStructuredText Directives`_.
 
 Field lists are mappings from field names to field bodies, modeled on
-RFC822_ headers.  A field name is made up of one or more letters,
-numbers, whitespace, and punctuation, except colons (":").  Inline
-markup is parsed in field names.  Field names are case-insensitive
-when further processed or transformed.  The field name, along with a
-single colon prefix and suffix, together form the field marker.  The
-field marker is followed by whitespace and the field body.  The field
-body may contain multiple body elements, indented relative to the
-field marker.  The first line after the field name marker determines
-the indentation of the field body.  For example::
+RFC822_ headers.  A field name may consist of any characters, but
+colons (":") inside of field names must be escaped with a backslash.
+Inline markup is parsed in field names.  Field names are
+case-insensitive when further processed or transformed.  The field
+name, along with a single colon prefix and suffix, together form the
+field marker.  The field marker is followed by whitespace and the
+field body.  The field body may contain multiple body elements,
+indented relative to the field marker.  The first line after the field
+name marker determines the indentation of the field body.  For
+example::
 
     :Date: 2001-08-16
     :Version: 1