diff --git a/man/pandoc-lua.1 b/man/pandoc-lua.1 --- a/man/pandoc-lua.1 +++ b/man/pandoc-lua.1 @@ -1,6 +1,6 @@ -.\" Automatically generated by Pandoc 3.12.1 +.\" Automatically generated by Pandoc 3.13 .\" -.TH "pandoc-lua" "1" "September 22, 2022" "pandoc 3.12.1" "Pandoc User\[cq]s Guide" +.TH "pandoc-lua" "1" "September 22, 2022" "pandoc 3.13" "Pandoc User\[cq]s Guide" .SH NAME pandoc\-lua \- Lua interface to pandoc API .SH SYNOPSIS diff --git a/man/pandoc-server.1 b/man/pandoc-server.1 --- a/man/pandoc-server.1 +++ b/man/pandoc-server.1 @@ -1,6 +1,6 @@ -.\" Automatically generated by Pandoc 3.12.1 +.\" Automatically generated by Pandoc 3.13 .\" -.TH "pandoc-server" "1" "August 15, 2022" "pandoc 3.12.1" "Pandoc User\[cq]s Guide" +.TH "pandoc-server" "1" "August 15, 2022" "pandoc 3.13" "Pandoc User\[cq]s Guide" .SH NAME pandoc\-server \- web server exposing pandoc API .SH SYNOPSIS diff --git a/man/pandoc.1 b/man/pandoc.1 --- a/man/pandoc.1 +++ b/man/pandoc.1 @@ -1,6 +1,6 @@ -.\" Automatically generated by Pandoc 3.12.1 +.\" Automatically generated by Pandoc 3.13 .\" -.TH "pandoc" "1" "2026\-10\-07" "pandoc 3.12.1" "Pandoc User\[cq]s Guide" +.TH "pandoc" "1" "2026\-10\-25" "pandoc 3.13" "Pandoc User\[cq]s Guide" .SH NAME pandoc - general markup converter .SH SYNOPSIS @@ -163,7 +163,7 @@ \f[CR]xelatex\f[R] is used, else \f[CR]luatexja\f[R] is needed if \f[CR]lualatex\f[R] is used. \f[CR]framed\f[R] is required if code is highlighted in a scheme that -use a colored background. +uses a colored background. The use of \f[CR]xelatex\f[R] or \f[CR]lualatex\f[R] as the PDF engine requires \f[CR]fontspec\f[R]. \f[CR]lualatex\f[R] uses \f[CR]selnolig\f[R] and \f[CR]lua\-ul\f[R]. @@ -802,7 +802,7 @@ in spans with \f[CR]insertion\f[R], \f[CR]deletion\f[R], \f[CR]comment\-start\f[R], and \f[CR]comment\-end\f[R] classes, respectively. -The author and time of change is included. +The author and time of change are included. \f[CR]all\f[R] is useful for scripting: only accepting changes from a certain reviewer, say, or before a certain date. If a paragraph is inserted or deleted, \f[CR]track\-changes=all\f[R] @@ -814,7 +814,7 @@ \f[CR]\-\-extract\-media=\f[R]\f[I]DIR\f[R]|\f[I]FILE\f[R]\f[CR].zip\f[R] Extract images and other media contained in or linked from the source document to the path \f[I]DIR\f[R], creating it if necessary, and adjust -the images references in the document so they point to the extracted +the image references in the document so they point to the extracted files. Media are downloaded, read from the file system, or extracted from a binary container (e.g.\ docx), as needed. @@ -1293,8 +1293,8 @@ Currently this feature only affects HTML and Docx output. .TP \f[CR]\-\-listings[=true|false]\f[R] -*Deprecated, use \f[CR]\-\-syntax\-highlighting=idiomatic\f[R] or -\f[CR]\-\-syntax\-highlighting=default\f[R] instead. +\f[I]Deprecated, use \f[CI]\-\-syntax\-highlighting=idiomatic\f[I] or +\f[CI]\-\-syntax\-highlighting=default\f[I] instead.\f[R] .RS .PP Use the \f[CR]listings\f[R] package for LaTeX code blocks. @@ -1599,8 +1599,8 @@ \f[CR]\f[R] (from the document title), \f[CR]\f[R] (from the document authors), \f[CR]\f[R] (from the document date, which should be in ISO 8601 format), \f[CR]\f[R] -(from the \f[CR]lang\f[R] variable, or, if is not set, the locale), and -\f[CR]\f[R] (a randomly generated +(from the \f[CR]lang\f[R] variable, or, if it is not set, the locale), +and \f[CR]\f[R] (a randomly generated UUID). Any of these may be overridden by elements in the metadata file. .PP @@ -1741,7 +1741,7 @@ Set the \f[CR]bibliography\f[R] field in the document\(cqs metadata to \f[I]FILE\f[R], overriding any value set in the metadata. If you supply this argument multiple times, each \f[I]FILE\f[R] will be -added to bibliography. +added to the bibliography. If \f[I]FILE\f[R] is a URL, it will be fetched via HTTP. If \f[I]FILE\f[R] is not found relative to the working directory, it will be sought in the resource path (see \f[CR]\-\-resource\-path\f[R]). @@ -1794,7 +1794,7 @@ When this is not possible, fall back to plain TeX. .TP \f[CR]mathjax\f[R][\f[CR]:\f[R]\f[I]URL\f[R]] -Render math using MathJaX. +Render math using MathJax. TeX math will be put between \f[CR]\(rs(...\(rs)\f[R] (for inline math) or \f[CR]\(rs[...\(rs]\f[R] (for display math) and wrapped in \f[CR]\f[R] tags with class \f[CR]math\f[R]. @@ -2322,7 +2322,7 @@ .EE .RE .PP -If the command line option accepts a URL argument, an \f[CR]url:\f[R] +If the command line option accepts a URL argument, a \f[CR]url:\f[R] field can be added to \f[CR]math\-method:\f[R]. .SS Options for wrapper scripts .RS -14n @@ -2747,7 +2747,7 @@ .IP \(bu 2 \f[CR]roman\f[R]: Converts textual values that can be read as an integer into lowercase roman numerals. -This can be used to get lettered enumeration from array indices. +This can be used to get roman\-numeral enumeration from array indices. To get uppercase roman, chain with \f[CR]uppercase\f[R]. .IP \(bu 2 \f[CR]left n \(dqleftborder\(dq \(dqrightborder\(dq\f[R]: Renders a @@ -2914,9 +2914,7 @@ .TP \f[CR]quotebordercolor\f[R], \f[CR]quotebordercolordark\f[R] sets the CSS \f[CR]border\-color\f[R] property for the left\-border of -.RS \f[CR]blockquote\f[R] elements. -.RE .TP \f[CR]quotecolor\f[R], \f[CR]quotecolordark\f[R] sets the CSS \f[CR]color\f[R] property for \f[CR]blockquote\f[R] @@ -3498,8 +3496,8 @@ \f[CR]pdfaintent\f[R] when used in conjunction with \f[CR]pdfa\f[R], specifies the output intent for the colors, -e.g.\ \f[CR]ISO coated v2 300\(rsletterpercent\(rsspace (ECI)\f[R] If -left unspecified, \f[CR]sRGB IEC61966\-2.1\f[R] is used as default. +e.g.\ \f[CR]ISO coated v2 300\(rsletterpercent\(rsspace (ECI)\f[R]. +If left unspecified, \f[CR]sRGB IEC61966\-2.1\f[R] is used as default. .TP \f[CR]toc\f[R] include table of contents (can also be set using @@ -3609,7 +3607,7 @@ .SS Variables for ms .TP \f[CR]fontfamily\f[R] -\f[CR]A\f[R] (Avant Garde), \f[CR]B\f[R] (Bookman), \f[CR]C\f[R] +\f[CR]A\f[R] (Avant Garde), \f[CR]B\f[R] (Bookman), \f[CR]H\f[R] (Helvetica), \f[CR]HN\f[R] (Helvetica Narrow), \f[CR]P\f[R] (Palatino), or \f[CR]T\f[R] (Times New Roman). This setting does not affect source code, which is always displayed @@ -3647,9 +3645,9 @@ \f[CR]mm/dd/yy\f[R], \f[CR]yyyy\-mm\-dd\f[R] (ISO 8601), \f[CR]dd MM yyyy\f[R] (e.g.\ either \f[CR]02 Apr 2018\f[R] or \f[CR]02 April 2018\f[R]), \f[CR]MM dd, yyyy\f[R] -(e.g.\ \f[CR]Apr. 02, 2018\f[R] or -\f[CR]April 02, 2018),\f[R]yyyy[mm[dd]]\f[CR](e.g.\f[R]20180402, -\f[CR]201804\f[R] or \f[CR]2018\f[R]). +(e.g.\ \f[CR]Apr. 02, 2018\f[R] or \f[CR]April 02, 2018\f[R]), +\f[CR]yyyy[mm[dd]]\f[R] (e.g.\ \f[CR]20180402\f[R], \f[CR]201804\f[R] or +\f[CR]2018\f[R]). .TP \f[CR]header\-includes\f[R] contents specified by \f[CR]\-H/\-\-include\-in\-header\f[R] (may have @@ -3767,7 +3765,7 @@ these characters literally. In writing LaTeX, enabling \f[CR]smart\f[R] tells pandoc to use the ligatures when possible; if \f[CR]smart\f[R] is disabled pandoc will use -unicode quotation mark and dash characters. +Unicode quotation mark and dash characters. .SS Headings and sections .SS Extension: \f[CR]auto_identifiers\f[R] A heading without an explicitly specified identifier will be @@ -4027,11 +4025,12 @@ referenced item. The original link text is discarded. This extension can be combined with \f[CR]xrefs_name\f[R] in which case -the name or caption numbers will appear after the number. +the name or caption will appear after the number. .PP -For the \f[CR]xrefs_number\f[R] to be useful heading numbers must be -enabled in the generated document, also table and figure captions must -be enabled using for example the \f[CR]native_numbering\f[R] extension. +For the \f[CR]xrefs_number\f[R] extension to be useful, heading numbers +must be enabled in the generated document, also table and figure +captions must be enabled using for example the +\f[CR]native_numbering\f[R] extension. .PP Numbers in cross\-references are only visible in the final document once it has been refreshed. @@ -4432,7 +4431,7 @@ Same as \f[CR]fenced_code_blocks\f[R], but uses backticks (\f[CR]\(ga\f[R]) instead of tildes (\f[CR]\(ti\f[R]). .SS Extension: \f[CR]fenced_code_attributes\f[R] -Optionally, you may attach attributes to fenced or backtick code block +Optionally, you may attach attributes to a fenced or backtick code block using this syntax: .IP .EX @@ -5171,8 +5170,8 @@ header from the table body. (For example \f[CR]\-\-\-|\-\f[R] would make the first column 3/4 and the second column 1/4 of the full text width.) -On the other hand, if no lines are wider than column width, then cell -contents will not be wrapped, and the cells will be sized to their +On the other hand, if no lines are wider than the column width, then +cell contents will not be wrapped, and the cells will be sized to their contents. .PP Note: pandoc also recognizes pipe tables of the following form, as can @@ -5738,7 +5737,7 @@ .TP FictionBook2 If \f[CR]\-\-math\-method=webtex\f[R] is used, formulas are rendered as -images using CodeCogs or other compatible web service, downloaded and +images using CodeCogs or another compatible web service, downloaded and embedded in the e\-book. Otherwise, they will appear verbatim. .TP @@ -5762,12 +5761,13 @@ For a more explicit way of including raw HTML in a Markdown document, see the \f[CR]raw_attribute\f[R] extension. .PP -In the CommonMark format, if \f[CR]raw_html\f[R] is enabled, -superscripts, subscripts, strikeouts and small capitals will be -represented as HTML. +In commonmark output, if \f[CR]raw_html\f[R] is enabled, superscripts, +subscripts, strikeouts and small capitals will be represented as HTML. Otherwise, plain\-text fallbacks will be used. -Note that even if \f[CR]raw_html\f[R] is disabled, tables will be -rendered with HTML syntax if they cannot use pipe syntax. +.PP +Disabling the \f[CR]raw_html\f[R] extension has no effect on +\f[CR]commonmark\f[R] (or \f[CR]gfm\f[R] or \f[CR]commonmark_x\f[R]) +\f[I]input\f[R]. .SS Extension: \f[CR]markdown_in_html_blocks\f[R] Original Markdown allows you to include HTML \(lqblocks\(rq: blocks of HTML between balanced tags that are separated from the surrounding text @@ -5818,7 +5818,7 @@ \f[CR]markdown_in_html_blocks\f[R], but it makes it easier to write pandoc filters to manipulate groups of blocks. .SS Extension: \f[CR]native_spans\f[R] -Use native pandoc \f[CR]Span\f[R] blocks for content inside +Use native pandoc \f[CR]Span\f[R] elements for content inside \f[CR]\f[R] tags. For the most part this should give the same output as \f[CR]raw_html\f[R], but it makes it easier to write pandoc filters to @@ -5968,9 +5968,9 @@ in square brackets. (There cannot be space between the two unless the \f[CR]spaced_reference_links\f[R] extension is enabled.) -If the label is empty (\f[CR][]\f[R]), then it will be implicitly be -taken to be the same as the link text; thus \f[CR][foo][]\f[R] is -equivalent to \f[CR][foo][foo]\f[R]. +If the label is empty (\f[CR][]\f[R]), then it will implicitly be taken +to be the same as the link text; thus \f[CR][foo][]\f[R] is equivalent +to \f[CR][foo][foo]\f[R]. (If the \f[CR]shortcut_reference_links\f[R] extension is enabled, the empty \f[CR][]\f[R] may be omitted.) .PP @@ -5981,7 +5981,7 @@ \f[CR]citations\f[R] extension is enabled): citations take precedence over link labels. .PP -Here are some examples of reference links and link definitions; +Here are some examples of reference links and link definitions: .IP .EX See [the website *I* built][my website]. @@ -6157,7 +6157,7 @@ For example the above example will render to the following. .RS 2 .IP \(bu 2 -HTML: \f[CR]\f[R] +HTML: \f[CR]\f[R] .IP \(bu 2 LaTeX: \f[CR]\(rsincludegraphics[width=0.5\(rstextwidth,height=\(rstextheight]{file.jpg}\f[R] @@ -6365,8 +6365,8 @@ If no locator term is used, \(lqpage\(rq is assumed. .PP In complex cases, you can force something to be treated as a locator by -enclosing it in curly braces or prevent parsing the suffix as locator by -prepending curly braces: +enclosing it in curly braces or prevent parsing the suffix as a locator +by prepending curly braces: .IP .EX [\(atsmith{ii, A, D\-Z}, with a suffix] @@ -6459,8 +6459,7 @@ relative to the file containing the link reference definition, not the file containing the reference link or image itself, if these differ. .SS Extension: \f[CR]mark\f[R] -To highlight out a section of text, begin and end it with with -\f[CR]==\f[R]. +To highlight a section of text, begin and end it with \f[CR]==\f[R]. Thus, for example, .IP .EX @@ -6687,7 +6686,7 @@ where \f[CR]FORMAT\f[R] is replaced with the name of the format. .PP Note that the list of extensions for \f[CR]commonmark\f[R], -\f[CR]gfm\f[R], and \f[CR]commonmark_x\f[R] are defined relative to +\f[CR]gfm\f[R], and \f[CR]commonmark_x\f[R] is defined relative to default commonmark. So, for example, \f[CR]backtick_code_blocks\f[R] does not appear as an extension, since it is enabled by default and cannot be disabled. @@ -6714,8 +6713,8 @@ \f[CR]bibliography\f[R] metadata field in a YAML metadata section or the \f[CR]\-\-bibliography\f[R] command line argument. If you want to use multiple bibliography files, you can supply multiple -\f[CR]\-\-bibliography\f[R] arguments or set \f[CR]bibliography\f[R] -metadata field to YAML array. +\f[CR]\-\-bibliography\f[R] arguments or set the \f[CR]bibliography\f[R] +metadata field to a YAML array. A bibliography may have any of these formats: .RS -14n .IP @@ -7029,8 +7028,8 @@ For LaTeX output, you can also use \f[CR]natbib\f[R] or \f[CR]biblatex\f[R] to render the bibliography. In order to do so, specify bibliography files as outlined above, and add -\f[CR]\-\-natbib\f[R] or \f[CR]\-\-biblatex\f[R] argument to pandoc -invocation. +the \f[CR]\-\-natbib\f[R] or \f[CR]\-\-biblatex\f[R] argument to the +pandoc invocation. Bear in mind that bibliography files have to be in either BibTeX (for \f[CR]\-\-natbib\f[R]) or BibLaTeX (for \f[CR]\-\-biblatex\f[R]) format. .SS Other relevant metadata fields @@ -7042,8 +7041,8 @@ Defaults to false. .TP \f[CR]link\-bibliography\f[R] -If true, DOIs, PMCIDs, PMID, and URLs in bibliographies will be rendered -as hyperlinks. +If true, DOIs, PMCIDs, PMIDs, and URLs in bibliographies will be +rendered as hyperlinks. (If an entry contains a DOI, PMCID, PMID, or URL, but none of these fields are rendered by the style, then the title, or in the absence of a title the whole entry, will be hyperlinked.) @@ -7985,8 +7984,8 @@ Setext\-style headings to be used; and \f[CR]\-\-preserve\-tabs\f[R] will prevent tabs from being turned to spaces. .SH VIMDOC -Vimdoc writer generates Vim help files and makes use of the following -metadata variables: +The Vimdoc writer generates Vim help files and makes use of the +following metadata variables: .IP .EX abstract\f[B]:\f[R] \(dqA short description\(dq @@ -7998,9 +7997,9 @@ vimdoc\-prefix\f[B]:\f[R] pandoc .EE .PP -Complete header requires \f[CR]abstract\f[R], \f[CR]author\f[R], +A complete header requires \f[CR]abstract\f[R], \f[CR]author\f[R], \f[CR]title\f[R] and \f[CR]filename\f[R] to be set. -Compiling file with such metadata produces the following file (assumes +Compiling a file with such metadata produces the following file (assumes \f[CR]\-\-standalone\f[R], see Templates): .IP .EX @@ -8017,8 +8016,8 @@ .EE .PP If \f[CR]vimdoc\-prefix\f[R] is set, all non\-command tags are prefixed -with its value, it is used to prevent tag collision: all headers have a -tag (either inferred or explicit) and multiple help pages can have the +with its value; this is used to prevent tag collision: all headers have +a tag (either inferred or explicit) and multiple help pages can have the same header names, therefore collision is to be expected. Let our input be the following markdown file: .IP @@ -8055,7 +8054,7 @@ inherently represent anything. .EE .PP -Convert it to vimdoc with metadata variable set (e.g.\ with +Convert it to vimdoc with the metadata variable set (e.g.\ with \f[CR]\-M vimdoc\-prefix=pandoc\f[R]) .IP .EX @@ -8391,11 +8390,11 @@ .EE .PP A recent \f[CR]context\f[R] version should be used, as older versions -contained a bug that lead to invalid PDF metadata. +contained a bug that led to invalid PDF metadata. .SS WeasyPrint The HTML\-based engine WeasyPrint includes experimental support for PDF/A and PDF/UA since version 57. -Tagged PDFs can created with +Tagged PDFs can be created with .IP .EX pandoc \-\-pdf\-engine=weasyprint \(rs @@ -8458,7 +8457,7 @@ .SH A NOTE ON SECURITY .IP "1." 3 Although pandoc itself will not create or modify any files other than -those you explicitly ask it create (with the exception of temporary +those you explicitly ask it to create (with the exception of temporary files used in producing PDFs), a filter or custom writer could in principle do anything on your file system. Please audit filters and custom writers very carefully before using @@ -8503,12 +8502,12 @@ \f[CR]header\-html\f[R] metadata fields will be passed directly to \f[CR]wkhtmltopdf\f[R] as \f[CR]\-\-footer\-html\f[R] and \f[CR]\-\-header\-html\f[R] arguments, and by using a \f[CR]file:\f[R] -URIs with these, one could exfiltrate local files. +URI with these, one could exfiltrate local files. In addition, using \f[CR]\-\-pdf\-engine=wkhtmltopdf\f[R] with \f[CR]\-f html+raw_html\f[R] enables an SSRF vulnerability in wkhtmltopdf (CVE\-2022\-35583). -Note that [\f[CR]wkhtmltopdf\f[R]) is deprecated and its authors -recommend not to use it with any untrusted input. +Note that \f[CR]wkhtmltopdf\f[R] is deprecated and its authors recommend +not to use it with any untrusted input. However, there may be similar issues with other pdf\-engines. Anyone including a pdf\-engine in a pandoc command run on untrusted input should audit the engine carefully and carefully control the use of diff --git a/pandoc-cli.cabal b/pandoc-cli.cabal --- a/pandoc-cli.cabal +++ b/pandoc-cli.cabal @@ -1,6 +1,6 @@ cabal-version: 2.4 name: pandoc-cli -version: 3.12.1 +version: 3.13 build-type: Simple license: GPL-2.0-or-later license-file: COPYING.md @@ -69,7 +69,7 @@ buildable: True -- Note: we always link to an exact version of pandoc, with the -- same version as this package: - build-depends: pandoc == 3.12.1, text + build-depends: pandoc == 3.13, text other-modules: PandocCLI.Lua , PandocCLI.Server