diff options
| author | fiddlosopher <fiddlosopher@788f1e2b-df1e-0410-8736-df70ead52e1b> | 2009-12-05 05:33:24 +0000 |
|---|---|---|
| committer | fiddlosopher <fiddlosopher@788f1e2b-df1e-0410-8736-df70ead52e1b> | 2009-12-05 05:33:24 +0000 |
| commit | 8671bc5a1be38f6555e34d7ccc542ebbe91f69fd (patch) | |
| tree | b1dcbf74eb45462d3f6cb0493792fe2a94daf680 /README | |
| parent | 94841b7602f3465cdb7a452989975d08e43fc694 (diff) | |
| download | pandoc-8671bc5a1be38f6555e34d7ccc542ebbe91f69fd.tar.gz | |
Markdown reader: Treat a backslash followed by a newline as hard linebreak.
Resolves Issue #154.
git-svn-id: https://pandoc.googlecode.com/svn/trunk@1646 788f1e2b-df1e-0410-8736-df70ead52e1b
Diffstat (limited to 'README')
| -rw-r--r-- | README | 9 |
1 files changed, 8 insertions, 1 deletions
@@ -463,7 +463,14 @@ which allows only the following characters to be backslash-escaped: \`*_{}[]()>#+-.! A backslash-escaped space is parsed as a nonbreaking space. It will -appear in TeX output as '~' and in HTML and XML as '\ ' or '\ '. +appear in TeX output as '`~`' and in HTML and XML as '`\ `' or +'`\ `'. + +A backslash-escaped newline (i.e. a backslash occurring at the end of +a line) is parsed as a hard line break. It will appear in TeX output as +'`\\`' and in HTML as '`<br />`'. This is a nice alternative to +markdown's "invisible" way of indicating hard line breaks using +two trailing spaces on a line. Subscripts and superscripts --------------------------- |