diff --git a/AUTHORS.md b/AUTHORS.md --- a/AUTHORS.md +++ b/AUTHORS.md @@ -6,6 +6,7 @@ - Akash Patel - Akos Marton - Albert Krewinkel +- Albert Lei - Alex Ivkin - Alex Toldaiev - Alex Vong @@ -33,6 +34,7 @@ - Anti-Distinctlyminty - Antoine Latter - Anton Antich +- Anton Melnikov - Antonio Terceiro - Arata Mizuki - Arata Mizuki @@ -74,6 +76,7 @@ - Charles Tapley Hoyt - Charlotte Koch - Chris Black +- Chris Callison-Burch - Christian Conkle - Christian Christiansen - Christian Despres @@ -176,6 +179,7 @@ - Ivar de Bruin - Ivo Clarysse - Jaap de Jong +- Jacob Larkin - James J Balamuta - J. B. Rainsberger - J. Lewis Muir @@ -441,15 +445,18 @@ - Wout Gevaert - Xavier Olive - Yan Pashkovsky +- Yann Trividic - Yehuda Katz - YI - Yoan Blanc +- You Jiangbin - Yuchen Pei - Zihang Chen - 3w36zj6 - arcnmx - a-vrma - andrebauer +- benniekiss - black-desk - blmage - bucklereed @@ -466,6 +473,7 @@ - etclub - favonia - guqicun +- har7an - harabat - hseg - infinity0x diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -215,9 +215,9 @@ external C libraries should especially be avoided. 10. We aim for compatibility with at least the last three - released ghc versions, and sometimes more. Currently pandoc - can be compiled on ghc 8.6 an higher. All pull requests and - commits are tested automatically on GitHub Actions. + released ghc versions, and sometimes more. Currently we + support ghc versions 9.6 and higher. All pull requests + and commits are tested automatically on GitHub Actions. Tests ----- @@ -448,7 +448,7 @@ Lua filters ----------- -If you've written a useful pandoc [lua filter](lua-filters.html), +If you've written a useful pandoc [lua filter](./doc/lua-filters.md), you may want to consider submitting a pull request to the [lua-filters repository](https://github.com/pandoc/lua-filters). diff --git a/COPYRIGHT b/COPYRIGHT --- a/COPYRIGHT +++ b/COPYRIGHT @@ -196,3 +196,30 @@ LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. + +------------------------------------------------------------------------ +Some of the code in wasm/pandoc.js and the patches in wasm/patches is +from https://github.com/haskell-wasm/pandoc-wasm. It is released under +this license: + +MIT License + +Copyright (c) Tweag I/O Limited. + +Permission is hereby granted, free of charge, to any person obtaining a copy +of this software and associated documentation files (the "Software"), to deal +in the Software without restriction, including without limitation the rights +to use, copy, modify, merge, publish, distribute, sublicense, and/or sell +copies of the Software, and to permit persons to whom the Software is +furnished to do so, subject to the following conditions: + +The above copyright notice and this permission notice shall be included in all +copies or substantial portions of the Software. + +THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR +IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, +FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE +AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER +LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, +OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE +SOFTWARE. diff --git a/MANUAL.txt b/MANUAL.txt --- a/MANUAL.txt +++ b/MANUAL.txt @@ -1,7 +1,7 @@ --- title: Pandoc User's Guide author: John MacFarlane -date: 2025-12-01 +date: 2025-02-02 --- # Synopsis @@ -307,7 +307,7 @@ - `bbcode` [BBCode] - `bbcode_fluxbb` [BBCode (FluxBB)] - `bbcode_phpbb` [BBCode (phpBB)] - - `bbcode_steam` [BBCode (Hubzilla)] + - `bbcode_steam` [BBCode (Steam)] - `bbcode_hubzilla` [BBCode (Hubzilla)] - `bbcode_xenforo` [BBCode (xenForo)] - `beamer` ([LaTeX beamer][`beamer`] slide show) @@ -416,17 +416,17 @@ `-d` *FILE*, `--defaults=`*FILE* -: Specify a set of default option settings. *FILE* is a YAML +: Specify a set of default option settings. *FILE* is a YAML or JSON file whose fields correspond to command-line option settings. All options for document conversion, including input and output files, can be set using a defaults file. The file will be searched for first in the working directory, and then in the `defaults` subdirectory of the user data directory - (see `--data-dir`). The `.yaml` extension may be omitted. - See the section [Defaults files] for more information on the - file format. Settings from the defaults file may be - overridden or extended by subsequent options on the command - line. + (see `--data-dir`). The `.yaml` extension will be added if + *FILE* lacs an extension. See the section [Defaults files] + for more information on the file format. Settings from the + defaults file may be overridden or extended by subsequent + options on the command line. `--bash-completion` @@ -736,7 +736,7 @@ affected paragraph break. This option only affects the docx reader. -`--extract-media=`*DIR* +`--extract-media=`*DIR*|*FILE*`.zip` : Extract images and other media contained in or linked from the source document to the path *DIR*, creating it if @@ -748,6 +748,10 @@ Otherwise filenames are constructed from the SHA1 hash of the contents. + If the path given ends in `.zip`, then instead of creating + a directory, pandoc will create a zip archive containing the + media files. + `--abbreviations=`*FILE* : Specifies a custom abbreviations file, with abbreviations @@ -945,27 +949,20 @@ inside raw HTML blocks when the `markdown_in_html_blocks` extension is not set. -`--syntax-highlighting="default"|"none"|"idiomatic"|`*STYLE*`|`*FILE* +`--syntax-highlighting=default|none|idiomatic|`*STYLE*`|`*FILE* : The method to use for code syntax highlighting. Setting a specific *STYLE* causes highlighting to be performed with the internal highlighting engine, using KDE syntax definitions and - styles. The `"idiomatic"` method uses a format-specific + styles. The `idiomatic` method uses a format-specific highlighter if one is available, or the default style if the target format has no idiomatic highlighting method. Setting this option to `none` disables all syntax highlighting. The - `"default"` method uses a format-specific default. + `default` method uses a format-specific default. The default for HTML, EPUB, Docx, Ms, Man, and LaTeX output is - to use the internal highlighter with the default style; Typst - output relies on Typst's own syntax highlighting system by - default. - - The [`listings`][] LaTeX package is used for idiomatic - highlighting in LaTeX. The package does not support multi-byte - encoding for source code. To handle UTF-8 you would need to - use a custom template. This issue is fully documented here: - [Encoding issue with the listings package][]. + to use the internal highlighter with the default style; for Typst + it is to use Typst's own syntax highlighting system. Style options are `pygments` (the default), `kate`, `monochrome`, `breezeDark`, `espresso`, `zenburn`, `haddock`, @@ -1431,7 +1428,7 @@ In the template, `%n` will be replaced by the chunk number (padded with leading 0s to 3 digits), `%s` with the section number of the chunk, `%h` with the heading text (with formatting removed), `%i` with - the section identifier. For example, `%section-%s-%i.html` might + the section identifier. For example, `section-%s-%i.html` might be resolved to `section-1.1-introduction.html`. The characters `/` and `\` are not allowed in chunk templates and will be ignored. The default is `%s-%i.html`. @@ -1762,7 +1759,9 @@ # Defaults files The `--defaults` option may be used to specify a package -of options, in the form of a YAML file. +of options, in the form of a YAML or JSON file. Examples in +this section will be given in YAML, but the equivalent forms in +JSON will also work. Fields that are omitted will just have their regular default values. So a defaults file can be as simple as @@ -1772,6 +1771,12 @@ verbosity: INFO ``` +or in JSON: + +``` json +{ "verbosity": "INFO" } +``` + In fields that expect a file path (or list of file paths), the following syntax may be used to interpolate environment variables: @@ -2005,7 +2010,7 @@ | ``` | ``` | +----------------------------------+-----------------------------------+ | ``` | ``` yaml | -| --wrap 60 | wrap: 60 | +| --wrap preserve | wrap: "preserve" | | ``` | ``` | +----------------------------------+-----------------------------------+ | ``` | ``` yaml | @@ -2964,6 +2969,13 @@ : additional attributes for the title slide of reveal.js slide shows. See [background in reveal.js, beamer, and pptx] for an example. +`highlightjs-theme` +: highlight.js theme for code highlighting when using + `--syntax-highlighting=idiomatic` with reveal.js (defaults to + `monokai`). See the [highlight.js demo page] for available themes. + +[highlight.js demo page]: https://highlightjs.org/demo + All [reveal.js configuration options] are available as variables. To turn off boolean flags that default to true in reveal.js, use `0`. @@ -3276,6 +3288,17 @@ See the section on [reproducible builds]. +`pdfstandard` +: PDF standard(s) for the document, e.g. `ua-2`, `a-4f`. + Supports PDF/A, PDF/X, and PDF/UA variants. + Requires LuaLaTeX and LaTeX 2023+. Repeat for multiple standards: + + --- + pdfstandard: + - ua-2 + - a-4f + ... + [KOMA-Script]: https://ctan.org/pkg/koma-script [LaTeX Font Catalogue]: https://tug.org/FontCatalogue/ [LaTeX font encodings guide]: https://ctan.org/pkg/encguide @@ -5992,6 +6015,17 @@ this reason, it is sometimes preferable to use the author-in-text style inside notes when using a note style. +Many CSL styles will format citations differently when the +same source has been cited earlier. In documents with chapters, +it is usually desirable to reset this position information +at the beginning of every chapter. To do this, add the class +`reset-citation-positions` to the heading for each chapter: + + # The Beginning {.reset-citation-positions} + +Note that this class only has an effect when placed on +top-level headings; it is ignored in nested blocks. + [CSL user documentation]: https://citationstyles.org/authors/ [CSL]: https://docs.citationstyles.org/en/stable/specification.html [CSL markup specs]: https://citeproc-js.readthedocs.io/en/latest/csl-json/markup.html#html-like-formatting-tags @@ -6199,9 +6233,6 @@ [GitHub-style Markdown alerts]: https://docs.github.com/en/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax#alerts -Note: This extension currently only works with commonmark: -`commonmark`, `gfm`, `commonmark_x`. - ### Extension: `autolink_bare_uris` ### Makes all absolute URIs into links, even when not surrounded by @@ -6927,6 +6958,23 @@ Notes are not yet supported for other slide formats, but the notes will not appear on the slides themselves. +### Speaker notes on the title slide (PowerPoint) + +For PowerPoint output, the title slide is generated from the document's +YAML metadata block. To add speaker notes to this slide, use a `notes` +field in the metadata: + + --- + title: My Presentation + author: Jane Doe + notes: | + Welcome everyone to this presentation. + + Remember to introduce yourself and mention the key topics. + --- + +The `notes` field can contain multiple paragraphs and Markdown formatting. + ## Columns To put material in side by side columns, you can use a native @@ -7594,6 +7642,24 @@ To disable highlighting, use `--syntax-highlighting=none`. +To use a format's idiomatic syntax highlighting instead of +pandoc's built-in highlighting, use `--syntax-highlighting=idiomatic`. +Currently, `idiomatic` only affects the following formats: + +- In reveal.js, it causes reveal.js's highlighting plugin to be + used for source code highlighting. The style may be customized + by setting the `highlightjs-theme` variable. + +- In Typst, it causes Typst's built-in highlighting to be used. + (This is also the default for Typst.) + +- In LaTeX, it causes the [`listings`][] package to be used. Note that + `listings` does not support multi-byte encoding for source code. To handle + UTF-8 you would need to use a custom template. This issue is fully + documented here: [Encoding issue with the listings package][]. + +- In other formats, `idiomatic` will have the same result as `default`. + [skylighting]: https://github.com/jgm/skylighting # Custom Styles @@ -7769,10 +7835,10 @@ However, it is possible to generate accessible PDFs, which use tagging to add semantic information to the document. -Pandoc defaults to LaTeX to generate PDF. Tagging support in LaTeX -is in development and not readily available, so PDFs generated in -this way will always be untagged and not accessible. This means -that alternative engines must be used to generate accessible PDFs. +Pandoc defaults to LaTeX to generate PDF. LaTeX's `\DocumentMetadata` +interface supports PDF standards and tagging when using LuaLaTeX; +set the `pdfstandard` variable to enable this (see below). For older +LaTeX installations, alternative engines must be used. The PDF standards PDF/A and PDF/UA define further restrictions intended to optimize PDFs for archiving and accessibility. Tagging @@ -7783,6 +7849,25 @@ including the colorspace of embedded images. Pandoc cannot check this, and external programs must be used to ensure that generated PDFs are in compliance. + +## LaTeX + +Set the `pdfstandard` variable to produce tagged PDFs conforming +to PDF/A, PDF/X, or PDF/UA standards. For example: + + pandoc -V pdfstandard=ua-2 --pdf-engine=lualatex doc.md -o doc.pdf + +Multiple standards can be combined: + + --- + pdfstandard: + - ua-2 + - a-4f + --- + +The required PDF version is inferred automatically. This feature +requires LuaLaTeX in TeX Live 2025 with LaTeX kernel 2025-06-01 +or newer. ## ConTeXt diff --git a/README.md b/README.md --- a/README.md +++ b/README.md @@ -135,7 +135,7 @@ - `bbcode_phpbb` [BBCode (phpBB)](https://www.phpbb.com/community/help/bbcode) - `bbcode_steam` [BBCode - (Hubzilla)](https://hubzilla.org/help/member/bbcode) + (Steam)](https://steamcommunity.com/comment/ForumTopic/formattinghelp) - `bbcode_hubzilla` [BBCode (Hubzilla)](https://hubzilla.org/help/member/bbcode) - `bbcode_xenforo` [BBCode diff --git a/changelog.md b/changelog.md --- a/changelog.md +++ b/changelog.md @@ -1,5 +1,336 @@ # Revision history for pandoc +## pandoc 3.9 (2026-02-03) + + * Add support for compiling pandoc to WASM. (To build, `make + pandoc.wasm`.) A stanza in `cabal.project` contains the + necessary build modifications. We owe this almost entirely to + TerrorJack, who created the original proof of context and + came up with the necessary build flags and patches to some + dependencies. + + `pandoc.wasm` has almost all the power of regular pandoc. The + main limitations is that it operates in a WASM sandbox and thus + cannot use HTTP to fetch resources and cannot run system commands. + As a result, JSON filters cannot be used, `--embed-resources` + works only with resources that have been explicitly provided in + the WASM sandbox, and PDFs cannot be produced (since that requires + running external commands). However, Lua filters can be used, + as long as they do not run system commands. + + A JavaScript bridge module, `wasm/pandoc.js`, is provided; this + handles the setup necessary to run `pandoc.wasm` in a browser. + + In addition, a full-featured GUI interface is provided in the + `wasm` subdirectory. `make serve` from that directory and it + will run locally, or visit . Note that + once the relevant code has been downloaded by the browser, it runs + entirely in the browser, and the conversions never touch a server. + The GUI was developed in interaction with Claude Code. This app + includes a WASM version of Typst and can produce PDF output via + Typst. + + * Defaults files may now be either JSON or YAML (though a `.yaml` + extension will still be assumed if the file has no extension). + The structure of a JSON defaults file is isomorphic to that of + a YAML defaults file. + + * Variable expansion now works even for the `defaults` field of + defaults files (#8024, Jacob Larkin). + + * `--extract-media` will now create a zip archive containing the media + (instead of a directory) if the path provided has a `.zip` extension. + + * Processing with `--citeproc` is now affected by a + `reset-citation-positions` class on headings. When the + `reset-citation-positions` class is added to a top-level + heading, `--citeproc` will reset position information at that + point in the document. This is needed in order to ensure that + the first citation in a chapter to a work that has been cited + in a previous chapter will not be in abbreviated form. + + * RST reader: + + + Fix definition lists where term ends with `-` (#11323). + This reverts some old code giving special treatment to + lines ending in hyphens; I don't understand why it was + there, because rst2html does not seem to do this. + + * HTML reader: + + + Revert an earlier change that caused style tags in the body + to be ignored (#10643, #11246). + + Parse inline style elements as RawInline (#10643, #11246). + + * Markdown reader: + + + Fix parsing of inline math (`$...$`) (#11311, benniekiss). + Do not allow blank lines before closing `$` delimiter. This brings the + parser in line with the documentation. + + Allow superscripted spans (#11409). These were being parsed as inline + notes. Now we disallow an inline note followed by + attributes, as this is almost certainly meant to be a span. + + Support `alerts` extension for pandoc markdown (#9716). It is not + enabled by default. + + * MediaWiki reader: + + + Add behavior switches support (#11354, Anton Melnikov). + They add a field to metadata without producing any text. + + Handle non-recognized tags as plain text (#11299). + + Better handling of inline tags (#11299). ``, ``, + ``, and `` now produce Code or Span elements with + classes, which can be handled by multiple output formats, + instead of simply being parsed as raw HTML tags. + + * RTF reader: + + + Ensure a new paragraph on `\pard` (#11361, Tuong Nguyen Manh). New + paragraphs may start with `\pard` alone without an explicit paragraph + break with `\par` preceding it. + + Improve hyperlink parsing more (#10942, Tuong Nguyen Manh). + Both the field instruction and its result may be ungrouped. + + Fix bug where list items were incorporated into a following table + (#11364). + + * ODT reader: + + + Add table row and column spans (#11366, Tuong Nguyen Manh). + Parse the number-rows-spanned and number-columns-spanned attributes to + create Cells for the Table. + + * DocBook reader: + + + Support "role" attribute (#11255, Yann Trividic). The `role` + attribute is parsed and added to Pandoc AST elements, using a + wrapper Div if needed. + + Omit empty title when not required (#11422). + This affects example and sidebar elements. + + Fix adding wrong metadata (#11300, Tuong Nguyen Manh). Now + keep track of the current element stack to only add metadata + if inside an appropriate parent element. + + * DocBook/JATS reader: + + + Don't export surrounding space from inline elements (#11398). Previously + we would export leading and trailing space inside elements like + emphasis or ulink so they appeared outside the resulting pandoc Inline + (Emph or Link). This is not really motivated; DocBook and XML in general + treats leading and trailing whitespace in this context as significant. + + * Docx reader: + + + Handle tables without `tblGrid` (#11380). + + Look inside v:rect as well as v:shape (#11412). + + * LaTeX reader: + + + Handle more quote macros from fontspec and ngerman babel (#6120). + + * Org reader: + + + Don't include 'example' class when parsing org example blocks (#11339). + These are just unmarked code blocks. + + * Texinfo writer: + + + Improve handling of certain code blocks (#11312). + MediaWiki, for example, will parse a code block containing + formatting as a sequence of Code elements separated by + LineBreaks. For this we now use a texinfo example block. + + * Typst writer: + + + Escape hyphens when needed (#11334). + + * HTML writer: + + + Include all classes on highlighted code elements (#11423). Previously, + only the language class was included, and the others were dropped. + + Slide formats: Make `. . .` pause work in nested blocks (#7201, #7582). + + For revealjs, add idiomatic highlight.js support (#11420, Claude Opus 4.5). + When using `--syntax-highlighting=idiomatic` with reveal.js output, pandoc + now generates HTML compatible with reveal.js's built-in highlight.js plugin: + Code blocks use `
` format.
+      The template loads highlight.js CSS, JS, and RevealHighlight plugin.
+
+  * Markdown writer:
+
+    + Ensure that `\ ` line breaks are used for commonmark.
+    + Use setext for headers containing line breaks for commonmark (#11341).
+    + Allow display math to start/end with space (#11384).
+      This reverts to earlier < 3.7 behavior.
+    + Properly handle tables with footers (#11416).
+
+  * JATS writer:
+
+    + Fix XML output for nested figures (#11362, Albert Krewinkel).
+      Subfigures are now wrapped inside a `` element. Furthermore,
+      figure content that isn't allowed as children of `` elements, such as
+      raw text, gets wrapped in `
` elements to ensure schema-conforming XML.
+
+  * AsciiDoc writer:
+
+    + Use doubled delims in more contexts (#11362). Also escape the `#` character.
+    + Use a span with role for SmallCaps (#11374).
+    + Export spaces inside delimited constructs like emph.
+
+  * Docx writer:
+
+    + Skip directory entries when building media overrides (#11379, You Jiangbin).
+      Pandoc's docx writer was previously adding an `` for
+      `/word/media/` in `[Content_Types].xml` when the reference doc contains
+      media, which violates OPC rules and causes Word to report corruption.
+    + Refactor the monolithic `writeDocx` into a number of smaller functions
+      (Claude Opus 4.5).
+    + Replace generic XML traversal with direct path navigation (Claude
+      Opus 4.5). Instead of using Data.Generics `everywhere` to traverse the
+      entire XML tree when setting language attributes, navigate directly to
+      the known path `w:docDefaults/w:rPr/w:lang`. This is more efficient and
+      removes the dependency on `Data.Generics`.
+
+  * EPUB writer:
+
+    + Don't use footnote backlinks for EPUBv3. Here we use aside elements,
+      which are popups, and the backlinks are not needed; in some readers
+      they cause a redundant number to appear, since the reader adds a note number.
+
+  * MediaWiki writer:
+
+    + Use Doc Text instead of Text for document construction (with Claude Open 4.5).
+      This refactors the writer to use Text.DocLayout combinators (vcat, hcat,
+      literal, blankline, cr, chomp) for building output, following the pattern
+      used by other text format writers (RST, Markdown, Man). This enables
+      better control over line spacing and paragraph separation.
+    + Improve blank space around div elements (#11417). This is merely cosmetic.
+
+  * PPTX writer:
+
+    + Support notes field in metadata for title slide (#5844, Chris Callison-Burch).
+      This adds support for a `notes` field in the YAML metadata block that will
+      be used as speaker notes for the title slide in PowerPoint output.
+      Previously, there was no way to add speaker notes to the title slide since
+      it is generated from metadata rather than from content blocks.
+
+  * LaTeX writer:
+
+    + Add PDF standard support via DocumentMetadata (#11407, Gordon Woodhull
+      with Claude Opus 4.5). The `pdfstandard` variable can be
+      used to specify PDF standards (PDF/A, PDF/X, PDF/UA) in
+      LaTeX output. This uses LaTeX's `\DocumentMetadata`
+      command, which requires LuaLaTeX. PDF version requirements
+      are automatically inferred, but can be explicitly overridden.
+      Automatic tagging is added for standards that require it.
+
+  * Typst template:
+
+    + Fix keywords usage. (#11317, har7an).
+    + Disable hyphenation for title, subtitle (#11375).
+    + Improve accessibility of definition lists (#11436). Before this
+      change, our show rule produced an error when typst was run with
+      `--pdf-standard=ua1`.
+
+  * HTML5 template:
+
+    + Conditionally include lang attribute, instead of providing
+      it with an empty value.
+
+  * JATS template:
+
+    + Fix author prefix placeholder (#11381, Christophe Dervieux).
+
+  * Text.Pandoc.Citeproc:
+
+    + Fix biblatex parsing of `@commentary` entries (#11322).
+    + Fix typo affecting `jurisdiction` biblatex type (#11321).
+    + Avoid adding an extra space at the beginning of a Cite.
+
+  * Text.Pandoc.Shared:
+
+    + Export `hasLineBreaks` [API change]. This was formerly
+      defined in the DocBook writer but more generally useful.
+
+  * Text.Pandoc.PDF:
+
+    + Add `SOURCE_DATE_EPOCH` to verbose environment variable info.
+
+  * Text.Pandoc.Class:
+
+    + Factor out `openURL` into Text.Pandoc.Class.IO.HTTP (unexported module).
+
+  * Lua subsystem (Albert Krewinkel):
+
+    + Mark readers and writers with their types (#11367). The
+      `pandoc.readers` and `pandoc.writers` maps now have string values
+      instead of boolean values. The string signals the type of the
+      reader/writer, `"text"` for TextReader/TextWriter and `"bytestring"`
+      for ByteStringReader/ByteStringWriter.
+    + Support equallity checks of LogMessage objects.
+    + Add function `pandoc.with_state` (#10859). The function allows
+      to run a callback with a modified pandoc state. This provides
+      the ability to temporarily modify the resource path, the user
+      data directory, and the HTTP request headers.
+    + Let `pandoc.with_state` error on unknown options (#11376).
+    + Add function `pandoc.utils.documentation` (#10999).
+      This is now used to generate much of the Lua API documentation.
+
+  * Text.Pandoc.App:
+
+    + Remove redundant check for asciidoc in UnknownReader.
+
+  * Text.Pandoc.Logging:
+
+    + Add `pretty` field to ToJSON instance for LogMessage.
+      This just reproduces the output of `logMessage`, for convenience for those
+      who are using the JSON output outside of Haskell.
+
+  * Text.Pandoc.Error:
+
+    + Change PandocHttpError constructor to take a Text instead of an
+      HttpException as the second argument (see #10980) [API change]
+      Motivation: exposing HttpException in the public API makes it
+      difficult to provide a version of pandoc that can be compiled
+      to wasm, which currently can't handle the network libraries.
+    + Define `displayException` for PandocError. This is a behavior change,
+      not an API change, since there was already a definition that defaulted
+      to using Show. The change here is that we use `renderError` for
+      a more human-readable version.
+
+  * Drop support for compilation with GHC versions < 9.6.
+
+  * Use released citeproc 0.13, djot 0.1.3, skylighting-format-blaze-html
+    0.1.2 (see #11423), texmath 0.13.1, asciidoc 0.1.0.1, typst-0.9,
+    hslua 2.5.
+
+  * Add `-Wno-deriving-typeble` to cabal ghc-options for ghc >= 9.12.
+
+  * Add `http` cabal flag (#10980). This allows pandoc to be
+    compiled without support for making HTTP requests, which is
+    useful when WASM is the target.
+
+  * pandoc-lua-engine has a new build flag `repl`, allowing support
+    for the Lua repl to be disabled for the wasm build.
+
+  * We now sign Windows artifacts with a code signing
+    certificate provided by SignPath.
+
+  * Mention Excel in cabal description.
+
+  * Makefile: remove some obsolete targets.
+
+  * MANUAL.txt:
+
+    + Fix typo about `--chunk-template` (#11358, Albert Lei).
+    + Fix link for bbcode_steam (#11389).
+    + Small rewrite of syntax-highlighting info.
+    + Fix defaults.yaml example for `wrap`.
+
+  * Fix a few mistakes in the contributing docs. (#11318, har7an).
+
+  * Fix a couple small errors in `doc/lua-filters.md`,
+    `doc/custom-writers.md`, and `doc/custom-readers.md`
+    (#11408, #11388).
+
 ## pandoc 3.8.3 (2025-12-01)
 
   * Add `asciidoc` as an input format (#1456).
diff --git a/data/templates/default.html5 b/data/templates/default.html5
--- a/data/templates/default.html5
+++ b/data/templates/default.html5
@@ -1,5 +1,5 @@
 
-
+
 
   
   
diff --git a/data/templates/default.jats_articleauthoring b/data/templates/default.jats_articleauthoring
--- a/data/templates/default.jats_articleauthoring
+++ b/data/templates/default.jats_articleauthoring
@@ -31,7 +31,7 @@
 $if(author.non-dropping-particle)$${author.non-dropping-particle} $endif$${author.surname}
 ${author.given-names}$if(author.dropping-particle)$ ${author.dropping-particle}$endif$
 $if(author.prefix)$
-${author.suffix}
+${author.prefix}
 $endif$
 $if(author.suffix)$
 ${author.suffix}
diff --git a/data/templates/default.latex b/data/templates/default.latex
--- a/data/templates/default.latex
+++ b/data/templates/default.latex
@@ -1,3 +1,4 @@
+$document-metadata.latex()$
 $passoptions.latex()$
 \documentclass[
 $for(babel-otherlangs)$
diff --git a/data/templates/default.revealjs b/data/templates/default.revealjs
--- a/data/templates/default.revealjs
+++ b/data/templates/default.revealjs
@@ -29,6 +29,9 @@
 $else$
   
 $endif$
+$if(highlight-js)$
+  
+$endif$
 $for(css)$
   
 $endfor$
@@ -87,6 +90,9 @@
 $if(mathjax)$
   
 $endif$
+$if(highlight-js)$
+  
+$endif$