summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorwiemann <wiemann@929543f6-e4f2-0310-98a6-ba3bd3dd1d04>2005-11-21 19:50:32 +0000
committerwiemann <wiemann@929543f6-e4f2-0310-98a6-ba3bd3dd1d04>2005-11-21 19:50:32 +0000
commitccac3b33bd345ea21e0cbbda824f99ddcf11adb1 (patch)
tree9a14f4788a71db511fa58f6c2efc6ca119550b98
parent656b4fab28abdf9a2d3361c385fd20b313fd114d (diff)
downloaddocutils-ccac3b33bd345ea21e0cbbda824f99ddcf11adb1.tar.gz
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
-rw-r--r--HISTORY.txt1
-rw-r--r--docs/ref/rst/restructuredtext.txt19
2 files changed, 11 insertions, 9 deletions
diff --git a/HISTORY.txt b/HISTORY.txt
index f6bcc741b..dbe1920ac 100644
--- a/HISTORY.txt
+++ b/HISTORY.txt
@@ -61,6 +61,7 @@ Changes Since 0.3.9
- Fixed bug with escaped colons indicating a literal block.
- Fixed bug with enumerated lists (SF#1254145).
+ - Backslash-escaped colons inside of field names are now allowed.
- Targets (implicit and explicit), anonymous hyperlink references
and auto-numbered footnote references inside of substitution
definitions are now disallowed.
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