git.iko.soy/typeable/pandoc
on master help sign in
MANUAL.txt move fenced_divs down to bracketed_spans
commit579e32408c34ffaf17fd57a76a6b84b11f763ec1 authormb21 <mb21@users.noreply.github.com> dateFri 29 Dec 2017, 15:55 (9 years ago) parent9cba3d2
1 file changed+49−42
MANUAL.txt+49−42
MANUAL.txt+49−42
@@ -3312,45 +3312,6 @@ For the most part this should give the same output as `raw_html`,
33123312but it makes it easier to write pandoc filters to manipulate groups
33133313of inlines.
33143314
3315−#### Extension: `fenced_divs` ####
3316−
3317−Allow special fenced syntax for native `Div` blocks. A Div
3318−starts with a fence containing at least three consecutive
3319−colons plus some attributes. The attributes may optionally
3320−be followed by another string of consecutive colons.
3321−The attribute syntax is exactly as in fenced code blocks (see
3322−[Extension: `fenced_code_attributes`]). As with fenced
3323−code blocks, one can use either attributes in curly braces
3324−or a single unbraced word, which will be treated as a class
3325−name. The Div ends with another line containing a string of at
3326−least three consecutive colons. The fenced Div should be
3327−separated by blank lines from preceding and following blocks.
3328−
3329−Example:
3330−
3331− ::::: {#special .sidebar}
3332− Here is a paragraph.
3333−
3334− And another.
3335− :::::
3336−
3337−Fenced divs can be nested. Opening fences are distinguished
3338−because they *must* have attributes:
3339−
3340− ::: Warning ::::::
3341− This is a warning.
3342−
3343− ::: Danger
3344− This is a warning within a warning.
3345− :::
3346− ::::::::::::::::::
3347−
3348−Fences without attributes are always closing fences. Unlike
3349−with fenced code blocks, the number of colons in the closing
3350−fence need not match the number in the opening fence. However,
3351−it can be helpful for visual clarity to use fences of different
3352−lengths to distinguish nested divs from their parents.
3353−
33543315#### Extension: `raw_tex` ####
33553316
33563317In addition to raw HTML, pandoc allows raw LaTeX, TeX, and ConTeXt to be
@@ -3612,13 +3573,59 @@ For example:
36123573 is to look at the image resolution and the dpi metadata embedded in
36133574 the image file.
36143575
3615−Spans
3616−-----
3576+Divs and Spans
3577+--------------
3578+
3579+Using the `native_divs` and `native_spans` extensions
3580+(see [above][Extension: `native_divs`]), HTML syntax can
3581+be used as part of markdown to create native `Div` and `Span`
3582+elements in the pandoc AST (as opposed to raw HTML).
3583+However, there is also nicer syntax available:
3584+
3585+#### Extension: `fenced_divs` ####
3586+
3587+Allow special fenced syntax for native `Div` blocks. A Div
3588+starts with a fence containing at least three consecutive
3589+colons plus some attributes. The attributes may optionally
3590+be followed by another string of consecutive colons.
3591+The attribute syntax is exactly as in fenced code blocks (see
3592+[Extension: `fenced_code_attributes`]). As with fenced
3593+code blocks, one can use either attributes in curly braces
3594+or a single unbraced word, which will be treated as a class
3595+name. The Div ends with another line containing a string of at
3596+least three consecutive colons. The fenced Div should be
3597+separated by blank lines from preceding and following blocks.
3598+
3599+Example:
3600+
3601+ ::::: {#special .sidebar}
3602+ Here is a paragraph.
3603+
3604+ And another.
3605+ :::::
3606+
3607+Fenced divs can be nested. Opening fences are distinguished
3608+because they *must* have attributes:
3609+
3610+ ::: Warning ::::::
3611+ This is a warning.
3612+
3613+ ::: Danger
3614+ This is a warning within a warning.
3615+ :::
3616+ ::::::::::::::::::
3617+
3618+Fences without attributes are always closing fences. Unlike
3619+with fenced code blocks, the number of colons in the closing
3620+fence need not match the number in the opening fence. However,
3621+it can be helpful for visual clarity to use fences of different
3622+lengths to distinguish nested divs from their parents.
3623+
36173624
36183625#### Extension: `bracketed_spans` ####
36193626
36203627A bracketed sequence of inlines, as one would use to begin
3621−a link, will be treated as a span with attributes if it is
3628+a link, will be treated as a `Span` with attributes if it is
36223629followed immediately by attributes:
36233630
36243631 [This is *some text*]{.class key="val"}