From d83b70f3a0d72c322b2c0da3c78d4478c20f7f93 Mon Sep 17 00:00:00 2001 From: fiddlosopher Date: Mon, 8 Jan 2007 23:54:15 +0000 Subject: + Changed 'escapedChar' in Markdown reader so that only the characters Markdown escapes are escaped in strict mode. When not in strict mode, Pandoc allows all non-alphanumeric characters to be escaped. + Added documentation of backslash escapes to README. git-svn-id: https://pandoc.googlecode.com/svn/trunk@461 788f1e2b-df1e-0410-8736-df70ead52e1b --- README | 22 ++++++++++++++++++++++ 1 file changed, 22 insertions(+) (limited to 'README') diff --git a/README b/README index f95a93758..23290fadd 100644 --- a/README +++ b/README @@ -342,6 +342,28 @@ using the `hsmarkdown` wrapper. [standard markdown]: http://daringfireball.net/projects/markdown/syntax "Markdown syntax description" +Backslash escapes +----------------- + +Except inside a code block or inline code, any punctuation or space +character preceded by a backslash will be treated literally, even if it +would normally indicate formatting. Thus, for example, if one writes + + *\*hello\** + +one will get + + *hello* + +instead of + + hello + +This rule is easier to remember than standard markdown's rule, +which allows only the following characters to be backslash-escaped: + + \`*_{}[]()>#+-.! + Lists ----- -- cgit v1.2.3