aboutsummaryrefslogtreecommitdiff
path: root/README
diff options
context:
space:
mode:
authorfiddlosopher <fiddlosopher@788f1e2b-df1e-0410-8736-df70ead52e1b>2006-12-30 23:19:14 +0000
committerfiddlosopher <fiddlosopher@788f1e2b-df1e-0410-8736-df70ead52e1b>2006-12-30 23:19:14 +0000
commitcf53a18bc1cc1017fef5525d8c96acc12bda6ce0 (patch)
treeb5bb347313a939791728a29000b6f8dae18a1521 /README
parentc3bad6e89efd20b4882581ad69107e213062ccf8 (diff)
downloadpandoc-cf53a18bc1cc1017fef5525d8c96acc12bda6ce0.tar.gz
Documented the "blank line before header and block quote" discrepancy
between standard markdown and pandoc. git-svn-id: https://pandoc.googlecode.com/svn/trunk@350 788f1e2b-df1e-0410-8736-df70ead52e1b
Diffstat (limited to 'README')
-rw-r--r--README13
1 files changed, 13 insertions, 0 deletions
diff --git a/README b/README
index d7e696bd6..af06a7e86 100644
--- a/README
+++ b/README
@@ -484,6 +484,19 @@ standard markdown (email-style) boxquotes:
| They look like this.
`----
+Blank lines before headers and blockquotes
+------------------------------------------
+
+Standard markdown syntax does not require a blank line before a header
+or blockquote. Pandoc does require this (except, of course, at the
+beginning of the document). The reason for the requirement is that
+it is all too easy for a `>` or `#` to end up at the beginning of a
+line by accident (perhaps through line wrapping). Consider, for
+example:
+
+ I like several of their flavors of ice cream: #22, for example, and
+ #5.
+
Inline LaTeX
------------