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

Update manual date and man page.

Browse source
This commit is contained in:
John MacFarlane 2021-05-13 14:11:15 -07:00
parent b243bf0f44
commit c46482bfc3
2 changed files with 39 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
MANUAL.txt
View file

@ -1,7 +1,7 @@
---
title: Pandoc User's Guide
author: John MacFarlane
date: March 20, 2021
date: May 13, 2021
---
# Synopsis

41
man/pandoc.1
View file

@ -1,7 +1,7 @@
'\" t
.\" Automatically generated by Pandoc 2.12.1
.\" Automatically generated by Pandoc 2.13
.\"
.TH "Pandoc User\[cq]s Guide" "" "March 20, 2021" "pandoc 2.13" ""
.TH "Pandoc User\[cq]s Guide" "" "May 13, 2021" "pandoc 2.14" ""
.hy
.SH NAME
pandoc - general markup converter
@ -4880,6 +4880,21 @@ header-includes:
\[ga]\[ga]\[ga]
\f[R]
.fi
.PP
Note: the \f[C]yaml_metadata_block\f[R] extension works with
\f[C]commonmark\f[R] as well as \f[C]markdown\f[R] (and it is enabled by
default in \f[C]gfm\f[R] and \f[C]commonmark_x\f[R]).
However, in these formats the following restrictions apply:
.IP \[bu] 2
The YAML metadata block must occur at the beginning of the document (and
there can be only one).
If multiple files are given as arguments to pandoc, only the first can
be a YAML metadata block.
.IP \[bu] 2
The leaf nodes of the YAML structure are parsed in isolation from each
other and from the rest of the document.
So, for example, you can\[cq]t use a reference link in these contexts if
the link definition is somewhere else in the document.
.SS Backslash escapes
.SS Extension: \f[C]all_symbols_escapable\f[R]
.PP
@ -6468,9 +6483,29 @@ entries (for author-date and numerical styles only).
.TP
\f[B]\f[CB]lang\f[B]\f[R]
The \f[C]lang\f[R] field will affect how the style is localized, for
example in the translation of labels and the use of quotation marks.
example in the translation of labels, the use of quotation marks, and
the way items are sorted.
(For backwards compatibility, \f[C]locale\f[R] may be used instead of
\f[C]lang\f[R], but this use is deprecated.)
.RS
.PP
A BCP 47 language tag is expected: for example, \f[C]en\f[R],
\f[C]de\f[R], \f[C]en-US\f[R], \f[C]fr-CA\f[R], \f[C]ug-Cyrl\f[R].
The unicode extension syntax (after \f[C]-u-\f[R]) may be used to
specify options for collation (sorting) more precisely.
Here are some examples:
.IP \[bu] 2
\f[C]zh-u-co-pinyin\f[R] \[en] Chinese with the Pinyin collation.
.IP \[bu] 2
\f[C]es-u-co-trad\f[R] \[en] Spanish with the traditional collation
(with \f[C]Ch\f[R] sorting after \f[C]C\f[R]).
.IP \[bu] 2
\f[C]fr-u-kb\f[R] \[en] French with \[lq]backwards\[rq] accent sorting
(with \f[C]cot\['e]\f[R] sorting after \f[C]c\[^o]te\f[R]).
.IP \[bu] 2
\f[C]en-US-u-kf-upper\f[R] \[en] English with uppercase letters sorting
before lower (default is lower before upper).
.RE
.TP
\f[B]\f[CB]notes-after-punctuation\f[B]\f[R]
If true (the default), pandoc will put footnote citations after