@@ -1346,7 +1346,7 @@ wrapping). Consider, for example:
1346 #22, for example, and #5.
1346 #22, for example, and #5.
1349−### Header identifiers
1349+### Header identifiers ###
1351#### Extension: `header_attributes` ####
1351#### Extension: `header_attributes` ####
@@ -1538,7 +1538,7 @@ of the verbatim text, and is removed in the output.
1538Note: blank lines in the verbatim text need not begin with four spaces.
1538Note: blank lines in the verbatim text need not begin with four spaces.
1541−### Fenced code blocks
1541+### Fenced code blocks ###
1543#### Extension: `fenced_code_blocks` ####
1543#### Extension: `fenced_code_blocks` ####
@@ -1745,7 +1745,7 @@ pandoc interprets it that way.
1745 [markdown syntax guide]:
1745 [markdown syntax guide]:
1746 http://daringfireball.net/projects/markdown/syntax#list
1746 http://daringfireball.net/projects/markdown/syntax#list
1748−### Ordered lists
1748+### Ordered lists ###
1750Ordered lists work just like bulleted lists, except that the items
1750Ordered lists work just like bulleted lists, except that the items
1751begin with enumerators rather than bullets.
1751begin with enumerators rather than bullets.
@@ -1825,7 +1825,7 @@ If default list markers are desired, use `#.`:
1825 #. three
1825 #. three
1828−### Definition lists
1828+### Definition lists ###
1830#### Extension: `definition_lists` ####
1830#### Extension: `definition_lists` ####
@@ -2167,7 +2167,7 @@ you'll need to add colons as above.
2167Metadata blocks
2167Metadata blocks
2168---------------
2168---------------
2170−#### Extension: `pandoc_title_block`
2170+#### Extension: `pandoc_title_block` ####
2172If the file begins with a title block
2172If the file begins with a title block
@@ -2243,7 +2243,7 @@ will also have "Pandoc User Manuals" in the footer.
2244will also have "Version 4.0" in the header.
2244will also have "Version 4.0" in the header.
2246−#### Extension: `yaml_metadata_block`
2246+#### Extension: `yaml_metadata_block` ####
2248A YAML metadata block is a valid YAML object, delimited by a line of three
2248A YAML metadata block is a valid YAML object, delimited by a line of three
2249hyphens (`---`) at the top and a line of three hyphens (`---`) or three dots
2249hyphens (`---`) at the top and a line of three hyphens (`---`) or three dots
@@ -2394,7 +2394,7 @@ just part of a word, use `*`:
2394 feas*ible*, not feas*able*.
2394 feas*ible*, not feas*able*.
2397−### Strikeout
2397+### Strikeout ###
2399#### Extension: `strikeout` ####
2399#### Extension: `strikeout` ####
@@ -2404,7 +2404,7 @@ with `~~`. Thus, for example,
2404 This ~~is deleted text.~~
2404 This ~~is deleted text.~~
2407−### Superscripts and subscripts
2407+### Superscripts and subscripts ###
2409#### Extension: `superscript`, `subscript` ####
2409#### Extension: `superscript`, `subscript` ####
@@ -2579,7 +2579,7 @@ The raw HTML is passed through unchanged in HTML, S5, Slidy, Slideous,
2579DZSlides, EPUB, Markdown, and Textile output, and suppressed in other
2579DZSlides, EPUB, Markdown, and Textile output, and suppressed in other
2582−#### Extension: `markdown_in_html_blocks`
2582+#### Extension: `markdown_in_html_blocks` ####
2584Standard markdown allows you to include HTML "blocks": blocks
2584Standard markdown allows you to include HTML "blocks": blocks
2585of HTML between balanced tags that are separated from the surrounding text
2585of HTML between balanced tags that are separated from the surrounding text
@@ -2901,9 +2901,28 @@ Note that `pandoc-citeproc --bib2json` and `pandoc-citeproc --bib2yaml`
2901can produce `.json` and `.yaml` files from any of the supported formats.
2901can produce `.json` and `.yaml` files from any of the supported formats.
2903In-field markup: In BibTeX and BibLaTeX databases, pandoc-citeproc parses
2903In-field markup: In BibTeX and BibLaTeX databases, pandoc-citeproc parses
2904−a subset of LaTeX markup; in CSL JSON databases, an [HTML-like markup][CSL markup specs];
2904+a subset of LaTeX markup; in CSL YAML databases, pandoc markdown; and in CSL JSON databases, an [HTML-like markup][CSL markup specs]:
2912+`<span style="font-variant:small-caps;">...</span>` or `<sc>...</sc>`
2921+`<span class="nocase">...</span>`
2922+: prevent a phrase from being capitalized as title case
2905−and in CSL YAML databases, pandoc markdown. `pandoc-citeproc -j` and `-y`
2924+`pandoc-citeproc -j` and `-y` interconvert the CSL JSON
2906−interconvert these markup formats as far as possible.
2925+and CSL YAML formats as far as possible.
2908As an alternative to specifying a bibliography file, you can include
2927As an alternative to specifying a bibliography file, you can include
2909the citation data directly in the `references` field of the
2928the citation data directly in the `references` field of the
@@ -2959,13 +2978,15 @@ characters (`:.#$%&-+?<>~/`). Here are some examples:
2959 Blah blah [@smith04; @doe99].
2978 Blah blah [@smith04; @doe99].
2961`pandoc-citeproc` detects locator terms in the [CSL locale files].
2980`pandoc-citeproc` detects locator terms in the [CSL locale files].
2962−Either abbreviated or unabbreviated forms are accepted. In the `en-US` locale,
2981+Either abbreviated or unabbreviated forms are accepted. In the `en-US`
2982+locale, locator terms can be written in either singular or plural forms,
2963−locator terms include `book`, `bk.`; `chapter`, `chap.`; `column`, `col.`;
2983+as `book`, `bk.`/`bks.`; `chapter`, `chap.`/`chaps.`; `column`,
2984+`col.`/`cols.`; `figure`, `fig.`/`figs.`; `folio`, `fol.`/`fols.`;
2964−`figure`, `fig.`; `folio`, `fol.`; `number`, `no.`; `line`, `l.`; `note`, `n.`;
2985+`number`, `no.`/`nos.`; `line`, `l.`/`ll.`; `note`, `n.`/`nn.`; `opus`,
2965−`opus`, `op.`; `page`, `p.`; `paragraph`, `para.`; `part`, `pt.`;
2986+`op.`/`opp.`; `page`, `p.`/`pp.`; `paragraph`, `para.`/`paras.`; `part`,
2966−`section`, `sec.`; `sub verbo`, `s.v.`; `verse`, `v.`; `volume`, `vol.`
2987+`pt.`/`pts.`; `section`, `sec.`/`secs.`; `sub verbo`, `s.v.`/`s.vv.`;
2967−as well as the plural forms of all these. If no locator term is used,
2988+`verse`, `v.`/`vv.`; `volume`, `vol.`/`vols.`; `¶`/`¶¶`; `§`/`§§`. If no
2968−"page" is assumed.
2989+locator term is used, "page" is assumed.
2970A minus sign (`-`) before the `@` will suppress mention of
2991A minus sign (`-`) before the `@` will suppress mention of
2971the author in the citation. This can be useful when the
2992the author in the citation. This can be useful when the