fixed the folding/unfolding story for the Description field
This commit is contained in:
parent
ed118482b1
commit
a8af709972
|
@ -127,7 +127,7 @@ field as-is. This means that authors should be conservative in
|
|||
the markup they use.
|
||||
|
||||
To support empty lines and lines with indentation with respect to
|
||||
the RFC 822 format, any new line has to be suffixed by 7 spaces
|
||||
the RFC 822 format, any CRLF character has to be suffixed by 7 spaces
|
||||
followed by a pipe ("|") char. As a result, the Description field is
|
||||
encoded into a folded field that can be interpreted by RFC822
|
||||
parser [2]_.
|
||||
|
@ -143,8 +143,9 @@ Example::
|
|||
| 3
|
||||
|
|
||||
|
||||
This encoding implies that any occurences of "``\n |``" have to be replaced
|
||||
by "``\n``" when the field is unfolded using a RFC822 reader.
|
||||
This encoding implies that any occurences of a CRLF followed by 7 spaces
|
||||
and a pipe char have to be replaced by a single CRLF when the field is unfolded
|
||||
using a RFC822 reader.
|
||||
|
||||
|
||||
Keywords (optional)
|
||||
|
|
Loading…
Reference in New Issue