diff options
| author | Fabien Schurter <8007715+fabschurt@users.noreply.github.com> | 2020-03-21 01:15:00 +0100 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2020-03-20 17:15:00 -0700 |
| commit | 5d88396dd45bf8668d2066693a6891aa275c16f3 (patch) | |
| tree | c2505ca48a74712c27d5c7a45d41b13a3f35d0b3 | |
| parent | 7601953205a233a72acceec780ff7a0e8160f1a0 (diff) | |
| download | pandoc-5d88396dd45bf8668d2066693a6891aa275c16f3.tar.gz | |
Make MANUAL more explicit about NBSP handling by all_symbols_escapable (#6201)
Fixes #6154.
| -rw-r--r-- | MANUAL.txt | 9 |
1 files changed, 6 insertions, 3 deletions
diff --git a/MANUAL.txt b/MANUAL.txt index 639c925b7..da70096d3 100644 --- a/MANUAL.txt +++ b/MANUAL.txt @@ -4019,9 +4019,12 @@ which allows only the following characters to be backslash-escaped: (However, if the `markdown_strict` format is used, the standard Markdown rule will be used.) -A backslash-escaped space is parsed as a nonbreaking space. It will -appear in TeX output as `~` and in HTML and XML as `\ ` or -`\ `. +A backslash-escaped space is parsed as a nonbreaking space. In TeX output, +it will appear as `~`. In HTML and XML output, it will appear as a +literal unicode nonbreaking space character (note that it will thus +actually look "invisible" in the generated HTML source; you can still +use the `--ascii` command-line option to make it appear as an explicit +entity). 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 |