diff options
| author | John MacFarlane <jgm@berkeley.edu> | 2017-11-04 10:30:32 -0700 |
|---|---|---|
| committer | John MacFarlane <jgm@berkeley.edu> | 2017-11-04 10:30:32 -0700 |
| commit | 8a216b00ef3207dba1438387c6064a97719c8fb3 (patch) | |
| tree | 979a959dd3f208eb8f476ee7772f393b8585b60b | |
| parent | e9c9bf10e26d62046f30a07f364ae06b44deb830 (diff) | |
| download | pandoc-8a216b00ef3207dba1438387c6064a97719c8fb3.tar.gz | |
Revise clarification on fenced_divs.
(#4039)
| -rw-r--r-- | MANUAL.txt | 13 |
1 files changed, 5 insertions, 8 deletions
diff --git a/MANUAL.txt b/MANUAL.txt index 085a34234..7edc6b063 100644 --- a/MANUAL.txt +++ b/MANUAL.txt @@ -3119,14 +3119,11 @@ because they *must* have attributes: ::: :::::::::::::::::: -Unlike fenced code blocks, here the exact number of colons in the opening and -closing fences is irrelevant, even when nesting divs: the telltale sign -between opening and closing fences is the presence of attributes, or the lack -thereof. Hence, the number of colons in a closing fence doesn't have to -match that of its opening counterpart, and there is no need to use different -fences lenghts to distinguish a nested div from its parent (except for visual -clarity). - +Fences without attributes are always closing fences. Unlike +with fenced code blocks, the number of colons in the closing +fence need not match the number in the opening fence. However, +it can be helpful for visual clarity to use fences of different +lengths to distinguish nested divs from their parents. #### Extension: `raw_tex` #### |