Tissevert/pandoc
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions 1

Make MANUAL more explicit about NBSP handling by all_symbols_escapable (#6201)

Browse source 
Fixes #6154.
This commit is contained in:
Fabien Schurter 2020-03-21 01:15:00 +01:00 committed by GitHub
parent 7601953205
commit 5d88396dd4
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 6 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

9
MANUAL.txt
View file

@ -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 (However, if the `markdown_strict` format is used, the standard Markdown rule
will be used.) will be used.)
A backslash-escaped space is parsed as a nonbreaking space. It will A backslash-escaped space is parsed as a nonbreaking space. In TeX output,
appear in TeX output as `~` and in HTML and XML as `\ ` or 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 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 a line) is parsed as a hard line break. It will appear in TeX output as