Make MANUAL more explicit about NBSP handling by all_symbols_escapable (#6201)
Fixes #6154.
This commit is contained in:
parent
7601953205
commit
5d88396dd4
1 changed files with 6 additions and 3 deletions
|
@ -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
|
||||
|
|
Loading…
Reference in a new issue