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

Revise clarification on fenced_divs.

Browse source 
(#4039)
This commit is contained in:
John MacFarlane 2017-11-04 10:30:32 -07:00
parent e9c9bf10e2
commit 8a216b00ef
1 changed files with 5 additions and 8 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

13
MANUAL.txt
View file

@ -3119,14 +3119,11 @@ because they *must* have attributes:
::: :::
:::::::::::::::::: ::::::::::::::::::
Unlike fenced code blocks, here the exact number of colons in the opening and Fences without attributes are always closing fences. Unlike
closing fences is irrelevant, even when nesting divs: the telltale sign with fenced code blocks, the number of colons in the closing
between opening and closing fences is the presence of attributes, or the lack fence need not match the number in the opening fence. However,
thereof. Hence, the number of colons in a closing fence doesn't have to it can be helpful for visual clarity to use fences of different
match that of its opening counterpart, and there is no need to use different lengths to distinguish nested divs from their parents.
fences lenghts to distinguish a nested div from its parent (except for visual
clarity).
#### Extension: `raw_tex` #### #### Extension: `raw_tex` ####