pdfmd-cli 3.26.20__tar.gz → 3.29.8__tar.gz

{pdfmd_cli-3.26.20/pdfmd_cli.egg-info → pdfmd_cli-3.29.8}/PKG-INFO

@@ -1,9 +1,9 @@
 Metadata-Version: 2.4
 Name: pdfmd-cli
-Version: 3.26.20
+Version: 3.29.8
 Summary: One command from Markdown to a good-looking PDF: a Pandoc wrapper with smart defaults, project-file discovery and a multi-engine fallback chain
 Author: Ali Perdekhan
-License-Expression: MIT
+License-Expression: MIT AND Apache-2.0
 Project-URL: Homepage, https://github.com/aliperdehan/pdfmd
 Project-URL: Changelog, https://github.com/aliperdehan/pdfmd/blob/main/CHANGELOG.md
 Keywords: pandoc,markdown,pdf,latex,cli
@@ -16,6 +16,7 @@ Description-Content-Type: text/markdown
 License-File: LICENSE
 License-File: pdfmd_inkmd/LICENSE
 License-File: pdfmd_inkmd/assets/fonts/DejaVuSans-LICENSE.txt
+License-File: pdfmd_mhchem/LICENSE
 Requires-Dist: pyyaml
 Requires-Dist: pypdf
 Provides-Extra: math
@@ -46,10 +47,20 @@ Word or OpenDocument file that follows its page setup, fonts and LaTeX (see
 
 ```console
 $ pdfmd lecture
-AUTO: READER TITLE MARGIN MONOFONT. Use --verbose to see in full
-OK    lecture.md
+FOUND     metadata: metadata.yaml + preamble.tex
+DEFAULTS  margin 1in, font STIX Two Text, code in JetBrains Mono, title from heading
+AUTO: READER. Use --verbose to see in full
+OK    lecture.md > lecture.pdf  (lualatex)
 ```
 
+`FOUND` is what pdfmd picked up from the folder, `DEFAULTS` what it applied because nothing said otherwise
+(the global metadata of `pdfmd --setup`, the title taken from a leading `# ` heading, a wide table whose columns it
+balanced), and the `AUTO:` line the other decisions it made. Files of one folder are listed under it once
+(`metadata: metadata.yaml + preamble.tex`; `--setup` can list each with its path instead). Each line is cut at the
+width of the terminal (110 characters when the output is piped): `+3 more (--verbose)`. `--verbose` prints every
+decision with its reason. The closing line names the file the build made, `OK    lecture.md > lecture.pdf`; `--setup`
+sets what stands between the two.
+
 In a folder with a single Markdown file you do not even need the name: `cd` into the folder and run `pdfmd`. It finds
 the file, its metadata, preamble and filters, and writes the PDF beside it (with several Markdown files it asks for
 one, or for `-b` to convert all of them or `-r` to join them). `pdfmd --help` is one short page; `pdfmd --help all`
@@ -90,6 +101,7 @@ turns that knowledge into defaults:
   given a Word recipe; what is left (tikz, chemfig, math Pandoc cannot convert) is drawn by LaTeX in the document's
   own preamble and embedded as vector pictures. `pdfmd-options: {office: {latex: auto|images|off}}`, `--no-auto
   officelatex` and `pdfmd --setup` switch it (see [Word and OpenDocument output](#word-and-opendocument-output)).
+  The file's properties hold the document's title and authors, and nothing of the machine that built it.
 - **It handles every script and emoji.** Text the main font cannot draw (Arabic,
   Hebrew, Chinese, Japanese, Korean, Greek, Cyrillic with Kazakh letters, Indic and
   more) is set run by run in an installed font for its script, emoji become colour
@@ -164,6 +176,11 @@ sudo pacman -S python-pipx pandoc-cli typst texlive   # Arch
 
 On any Linux, `pdfmd --install full` (Pandoc and Typst) needs no package manager and no root.
 
+The extras that are Python packages (`pdfmd --install math`, `tui`, `translit`, `batchocr` ...) go into the Python pdfmd runs
+from; when that Python is managed by the system (Homebrew's, Debian's: "externally-managed-environment", PEP 668) pdfmd puts
+them in its own folder instead, `~/.local/share/pdfmd/python/3.14` (one per Python version), which it adds to the end of
+the module path when it starts. Nothing is installed into the system's Python.
+
 ```powershell
 py -m pip install --user pipx; py -m pipx ensurepath          # Windows
 winget install --id JohnMacFarlane.Pandoc; winget install --id Typst.Typst
@@ -210,12 +227,79 @@ OK    7. weasyprint  (/opt/homebrew/bin/weasyprint)
 MISS  8. wkhtmltopdf
 ...
 OK    14. soffice  (/Applications/LibreOffice.app/Contents/MacOS/soffice)
+OK    calibre (only when named: -e calibre)  (/opt/homebrew/bin/ebook-convert)
 OK    quarto (only needed for .qmd files)  (/usr/local/bin/quarto)
 ```
 
 The numbers are the fallback order, and also shortcuts: `-e 6` means
 `-e typst`.
 
+**An order of your own.** `-e` takes a comma list, tried in the order written and nothing else:
+`-e typst,calibre,lualatex` tries Typst, then Calibre, then LuaLaTeX. A word is an engine (or its alias), a family
+(`tex`, `html`, `typst`: its installed members, in place) or `pandoc` (every engine Pandoc drives; never Calibre). A word
+whose engine is not installed is passed over with a NOTE while another one of the list can run, and the build stops only
+when none can. `pdf-engine:` in `pdfmd-options`, the front matter, a metadata file or the config takes the same list
+(`pdf-engine: [typst, lualatex]`). Without `-e` the chain is the numbered one above, unchanged.
+
+`-e calibre` prints the document with [Calibre](https://calibre-ebook.com)'s `ebook-convert`
+instead: Pandoc writes one HTML page (math as MathML, which Calibre draws with its own
+MathJax) and Calibre turns it into a PDF with the document's paper, margins, `fontsize:` and
+language, page numbers, and bookmarks from the headings. LaTeX in the document is made native
+or drawn as a picture, as for a Word file. Calibre is not in the numbered chain: it comes first when you
+name it (`-e calibre`, or `pdf-engine: calibre` in `pdfmd-options:`), and (v3.29.1) it and the browsers
+(`-e edge`, `chrome`, `chromium`, `brave`: Pandoc's HTML page, printed headless) are tried last when no engine is named
+and LaTeX, Typst and the HTML engines have all failed, ahead of LibreOffice; `--doctor` lists them as last resorts.
+A comma list of your own never adds them (`-e pandoc` is every engine Pandoc drives, not these).
+
+With no Pandoc at all, Calibre reads the Markdown itself (v3.29): its own Markdown reader (tables, footnotes, fenced code, lists)
+prints it, before the rough built-in renderers, with the document's paper and margins. It has no math (formulas are text) and
+none of Pandoc's syntax, and says so (`NOTE`, `WARN`). `-e calibre` or `-e native` without Pandoc picks it; with Pandoc,
+`-e calibre` is the HTML route above.
+
+`pdfmd --install calibre` (v3.29) gets Calibre when it is missing (190 to 360 MB). In a terminal on a Mac or Windows it offers
+`brew install --cask calibre` or `winget install --id calibre.calibre -e` first. Otherwise (or on answering `d`) pdfmd downloads the
+release file for your machine and checks it against the SHA-256 GitHub lists for it, and refuses a download whose checksum is not
+listed: on macOS it opens the disk image read-only and copies `calibre.app` into `~/Applications`, on Linux (x86-64, ARM)
+it unpacks the archive into pdfmd's data folder (no root, no desktop entries), and either way runs `ebook-convert --version`
+to check. Windows: `winget`, or the installer from calibre-ebook.com. Calibre is a program pdfmd runs, never one it contains.
+
+A browser prints a Markdown document too (v3.29): `-e edge`, `-e chrome`, `-e chromium` or `-e brave` (or `-e browser` for the
+first one installed) has Pandoc write one self-contained HTML page and the browser, headless, print it with the document's
+paper and margins (`papersize`, `geometry`, `margin`: as `@page`) and 12pt text. The math is MathML, which the browser draws
+itself; LaTeX in the document is made native or drawn as a picture, as for a Word file. Like Calibre, a browser comes first when you
+name it and last when you do not (see above); an `.html` file already goes to one first when it has scripts or MathML.
+
+Calibre also writes ebooks (v3.29): `pdfmd book.md -o book.azw3` (or `--to azw3`) has Pandoc write an EPUB 3 (chapters,
+contents, the metadata, the math as MathML) and Calibre turn it into the target, `book.azw3` beside the document. The
+twelve targets only Calibre writes are `azw3`, `mobi`, `kepub`, `lit`, `lrf`, `pdb`, `rb`, `snb`, `tcr`, `pmlz`, `htmlz`
+and `txtz`; each was converted back to text to check that its words, list and table are there. (Before v3.29 `-o
+book.azw3` wrote a PDF under that name.) `epub`, `docx`, `rtf`, `txt` and `fb2` Pandoc writes itself, with more of its own
+features (styles, tables, footnotes); they go through Calibre only when `-e calibre` is on the command line (a
+`pdf-engine: calibre` is a PDF setting), with a NOTE. `-e calibre` with another target (`.tex`, `.html`, `.md`) stops and
+lists what Calibre writes. One document at a time, not `-b` or `-r`.
+
+The math of an ebook: a Kindle or a Kobo does not draw MathML, and a MOBI has no place for it. `azw3`, `mobi`, `kepub`, `lit`
+and `lrf` (and `docx` through Calibre) get each formula drawn by LaTeX as a picture, in the document's own preamble and with
+its `\ce` and siunitx, as a Word file's pictures are (needs a LaTeX engine and Poppler's `pdftocairo`); the plain formats
+(`pdb`, `rb`, `snb`, `tcr`, `pmlz`, `txtz`, `rtf`, `txt`, `fb2`) get the formulas as text, the simple ones with their
+superscripts and the rest as TeX, with one `WARN` that counts them, and so does a picture target on a machine with no LaTeX.
+`epub` and `htmlz` keep the MathML. A `--mathml` or `--math-method` of your own is kept.
+
+An ebook can be the input too (v3.29): `pdfmd book.epub` builds `book.pdf` beside it, `pdfmd book.mobi -o book.md` writes its
+Markdown (with its pictures in `media/`) for you to edit, `pdfmd book.azw3 --to docx` a Word file. An EPUB is read by Pandoc;
+`mobi`, `azw`, `azw3`, `azw4`, `kepub`, `lit`, `lrf`, `pdb`, `prc`, `chm`, `snb`, `tcr`, `rb`, `pmlz`, `htmlz` and `txtz` first go
+through Calibre's `ebook-convert` into an EPUB (Calibre is needed for those, not for an EPUB). The closing line names the
+book. One book at a time, not with other files, `-b` or `-r`; a book with DRM, and an ebook of nothing but pictures (a comic),
+cannot be read. A formula a MOBI holds as a picture stays a picture. Calibre's own scaffolding in the converted book (an
+anchor for every file it split the book into, its page-break divs and classes) is dropped from the Markdown; with
+`-o book.md` the pictures are copied to a `media/` folder beside it.
+
+LibreOffice writes what Pandoc cannot too (v3.29): `pdfmd letter.md -o letter.doc` (Word 97) has Pandoc write the Word file (the
+same one `-o letter.docx` writes: your reference document, native equations and tables, pictures for what LaTeX alone can draw)
+and headless LibreOffice turn it into `.doc`. `rtf`, `odt`, `txt` and `epub` go through LibreOffice only with `-e soffice` (or
+`-e libreoffice`, `-e office`) first on the command line, with a NOTE; without it Pandoc writes them from the document itself,
+which is the better file. `-e soffice` with another target (`.tex`, `.md`) lists what it writes.
+
 For everything at once, `pdfmd --doctor` is one page on the Markdown-to-PDF tools, fonts
 and emoji, PDF reading (batchocr, Tesseract, Poppler, OCR languages), your config file and
 the cache, ending with the command that fixes each missing piece:
@@ -246,6 +330,8 @@ MISS  xelatex: could not build it (! LaTeX Error: File `stix2.sty' not found.)
 OK    typst: built a PDF in 1.1 s
 ```
 
+The last resorts are tried too (v3.29): an installed browser (`edge: built a PDF in 6.1 s`) and Calibre, which also writes a small
+ebook (`calibre:azw3: built an AZW3 ebook in 18.0 s`), so a missing Qt library shows here and not in the middle of a book.
 It takes a few seconds per engine (a minute or more if TeX has to fetch packages); without `--deep` nothing is built.
 
 ### Tab completion
@@ -263,7 +349,7 @@ pdfmd --completion fish > ~/.config/fish/completions/pdfmd.fish
 
 The oldest Pandoc `pdfmd` is tested with is **3.1.3** (what the claude.ai sandbox has); the whole test suite runs against
 it. An older one may work, and the first build with it says so once; `pdfmd --doctor` lists what a given Pandoc does
-without. With 3.1.3: Typst PDFs cannot show a picture `pdfmd` drew itself (before 3.2), a numbered equation in a Word file
+without. With 3.1.3: a numbered equation in a Word file
 sits in a plain table instead of a borderless one (before 3.4), and `--extract-tables` leaves a table whose caption has
 a `{#tbl:id}` (before 3.8.2: Pandoc reads that as words, so the change could not be checked). A `pandoc-crossref` must be
 the release built for the Pandoc you run; one built for another is not run, with a warning, because it would put `??` where
@@ -291,7 +377,7 @@ $ pdfmd notes.md
 NOTE  Pandoc was not found: building with the built-in renderer (inkmd). The output is plain ...
 NATIVE  notes.md via inkmd
 WARN  native (inkmd): notes.md: 2 math expression(s) set as plain text (Unicode, sub/superscripts, display math centred); ...
-OK    notes.md
+OK    notes.md > notes.pdf
 ```
 
 - **[inkmd](https://github.com/eagredev/inkmd)**, written by Dylan Moir (MIT
@@ -314,6 +400,13 @@ OK    notes.md
   where the built-in renderer and every engine that can draw colour emoji
   (Typst) find it; without it emoji print as `[rocket]`-style labels in the
   built-in renderer.
+- `pdfmd --install math:mathjax` (MathJax 4 and its STIX Two math font, about 12 MB to download, about 2 MB on
+  disk) and `pdfmd --install math:katex` (KaTeX, about 1.5 MB) are for WeasyPrint's PDFs, not the built-in
+  renderer: they typeset its math (see "WeasyPrint does not typeset math itself" below).
+- `pdfmd --install core:tex` (also `cortex`, about 50 MB) is the other core: **Pandoc and Tectonic**, the self-contained
+  LaTeX engine (its release from GitHub, checked against the SHA-256 GitHub lists, into pdfmd's own tools folder). Tectonic
+  fetches the TeX files a document needs from the network the first time, then works from its cache. `core:typst`
+  (or `core`) is `--install full` below. `pan-tec` (see "Other command names") runs pdfmd on it.
 - `pdfmd --install full` leaves the fallback behind: it installs **Pandoc** (the
   real binary from PyPI's `pypandoc_binary`, about 35 MB, also `--install pandoc`
   / `pdfmd-cli[pandoc]`) and **Typst** (Typst's own release from GitHub, about
@@ -324,7 +417,8 @@ OK    notes.md
 
 Every input is treated as GitHub-flavoured Markdown. Pandoc-only syntax is
 converted where possible (`\newpage` and `<!-- pagebreak -->` become a page
-break, footnotes become endnotes for inkmd, `$` prices are not mistaken for math)
+break, as they do through Pandoc with `pagebreak:`, see *Page breaks in every
+format*; footnotes become endnotes for inkmd, `$` prices are not mistaken for math)
 and removed otherwise (heading and image attributes, `:::` divs, raw LaTeX,
 `<!-- comments -->`), with one warning per kind. CSV tables
 (`::: {.csv file="data.csv"}`) work as they do with Pandoc. The title, author and date in the
@@ -429,6 +523,28 @@ Ctrl-G go to a line, Ctrl-K / Ctrl-U cut and paste a line, Ctrl-Z / Ctrl-Y undo
 when there are unsaved changes); F1 lists them. Options given beside it (`pdfmd --edit lecture -e lualatex`) are used
 for the build, and a name that does not exist yet starts a new file. It is deliberately rough: a base for what comes later.
 
+**Edit a PDF in place.** A PDF that carries its source (`--attach-source`; `pdfmd --check-source` says which do) can be
+edited and rebuilt where it lies:
+
+```sh
+pdfmd --edit report.pdf                          # the built-in editor, on the source as one file in a temporary folder
+pdfmd --edit report.pdf --editor "code --wait"   # your own: the folder is watched and rebuilt on every save
+```
+
+A document is edited as the ONE file its source is: the text with its metadata, preamble, bibliography and style, and the `.tex`
+and CSV files it reads, as blocks after the text (`<!-- pdfmd-at: ... -->` comments say on which line each one is); only what
+is not text (your package, pictures, files in sibling folders) is beside it. You edit that file; Ctrl-B (or each save with
+`--editor`) builds it, and when you leave, `report.pdf` is replaced by the rebuilt one, which carries the source again, and
+the old one is kept in `.backups/` beside it. Before it is replaced pdfmd checks that the rebuilt PDF still carries its source
+and everything the old one carried; a PDF without its source is refused (yours stays as it was), and what is missing is named.
+The temporary folder is removed when you leave. For the files it was made from, `pdfmd --restore report.pdf` (or `--unpack`). Nothing
+changes when you leave without editing, or when the last version does not build. The options of the first build are the
+ones the document and its metadata record; the command-line ones are the ones you give now, and the global metadata of
+`pdfmd --setup` is this machine's (a rebuild on another one can differ). A book built with `-r` is edited as a book: your editor gets every
+chapter file and each save rebuilds all of them in the order the book was built (the built-in editor opens the first chapter and names the
+others). `--editor CMD` also works on a Markdown file
+(a watch that rebuilds on every save, until the editor closes), and `pdfmd --setup` keeps a default editor.
+
 ### In VS Code
 
 `pdfmd --init-vscode` writes a `.vscode/tasks.json` here (build, build and open, watch, check, extract tables; Terminal > Run
@@ -660,6 +776,13 @@ office:
   reference-doc: house.dotx
 ```
 
+The same file can list `lua:` (Lua filters beside the document besides `<package>.lua`, which a document that loads the
+package gets by name anyway), `draft-skip:` (`commands:` that take one argument and `spans:` of a start macro up to its stop
+macro, which the label scan's draft pass need not draw, as it skips `chemfig`) and `picture-cache:` (the macro names and the
+request-file suffix a package used for the picture cache before the protocol had neutral names, see "For a package author").
+pdfmd names no package: all of this is found by reading the packages a document loads, in its preamble files or its
+`header-includes:`.
+
 ```yaml
 pdfmd-options:
   office:
@@ -674,14 +797,20 @@ pdfmd-options:
 **LaTeX in the document.** Pandoc turns `$x^2$` into a Word equation and drops everything else of
 LaTeX. For `.docx` and `.odt` pdfmd adds a filter that makes it native where it can:
 
-- `\ce{Ag+(aq) + Cl-(aq) -> AgCl(s)}` (mhchem) and `\si{\gram\per\mole}`, `\SI{5}{\milli\liter}`,
+- `\ce{Ag+(aq) + Cl-(aq) -> AgCl(s)}` (mhchem) and `\si{\gram\per\mole}`, `\qty{5}{\mL}`,
   `\num{1.5e-3}` (siunitx) become formatted text with real subscripts, charges and units, and, inside
-  math, Word equation pieces;
+  math, Word equation pieces. `\ce` is read by a port of mhchem's own parser, so it comes out as LaTeX sets it;
+  siunitx follows your `\sisetup`, `\DeclareSIUnit`s and unit shortcuts, those of your own packages too. A
+  formula with words over its arrow is an equation;
+  the same in an HTML, EPUB, Markdown, text or Typst file and a PowerPoint deck, whose writers would drop them;
 - `\begin{equation}`, `align`, `reaction`... become Word equations with their number at the right;
 - raw `figure`, `tabular`, lists, `\emph`, `\newpage`... are read by Pandoc's own LaTeX reader;
 - `\ref`, `\eqref`, `\cref`, `\Cref`, `\pageref` and the "Figure 3." in front of a caption use the numbers
   LaTeX itself gave (pdfmd builds the PDF once, in its cache, and reads the `.aux`; reused while the sources
-  are older), with the caption separator (`labelsep=`) and `\crefname`s of your preamble;
+  are older), with the caption separator (`labelsep=`) and `\crefname`s of your preamble. Each reference is a link
+  to what it names. A `\label` in a caption, in a block drawn as a picture or on any line of an equation becomes a
+  bookmark there. In OpenDocument a labelled table, figure or div, and a citation's entry in the references, get one
+  too, since its writer bookmarks none of them;
 - **what is left is drawn by LaTeX**: tikz, chemfig, a house style's own macros, math Pandoc cannot convert are compiled in
   *your document's own preamble* (the same fonts, packages and macros as the PDF, one fragment to a page), and the
   pages go into the Word file as vector pictures: an SVG with a 300 dpi PNG fallback (Word 2016 and later draw the SVG,
@@ -710,9 +839,10 @@ quick way to see what is left to give a recipe (see the profile below).
 (Pandoc's own behaviour). `office: {labels: off}` skips the PDF build (numbers are then counted).
 
 The same filter serves the other outputs when LaTeX is the problem: **the soffice fallback** (the Word file above, then LibreOffice: `pdfmd -e soffice report.md` is the `.docx` as LibreOffice draws it) now
-keeps the page size, margins and fonts, shows equations and draws what LaTeX can; a **Typst or WeasyPrint run after LaTeX
-failed** gets what the document says in LaTeX as native text or pictures instead of nothing; and HTML, Typst and
-WeasyPrint builds do it on request (`pdfmd-options: {office: {latex: auto}}`).
+keeps the page size, margins and fonts, shows equations and draws what LaTeX can. A **Typst or WeasyPrint PDF** (named
+with `-e`, or after LaTeX failed) gets what the document says in LaTeX as native text or pictures instead of nothing,
+whenever it has LaTeX they would drop; `raw: {typst: [typst]}` (or `office: {latex: off}`) keeps Pandoc's own behaviour.
+HTML and Typst *files* (`-o x.html`, `--to typst`) do it on request (`pdfmd-options: {office: {latex: auto}}`).
 
 ### Stopping part-way
 
@@ -735,6 +865,7 @@ them beside it. What the text points at otherwise (images, files a preamble
 the assembled file.
 
 ```sh
+pdfmd report --merge                                           # everything: one file that builds alone, anywhere
 pdfmd report --assemble-only --embed-metadata                  # metadata.yaml, preamble.tex, Lua filters, .bib/.csl
 pdfmd report --assemble-only --embed-metadata metadata preamble   # only those
 pdfmd report --assemble-only --embed-metadata --lua-mode ref   # name the filter instead of copying it
@@ -790,22 +921,36 @@ file you can edit again. Ask for it, on the command line or in the document:
 
 ```sh
 pdfmd report --attach-source     # the source goes into report.pdf as an attachment
-pdfmd report --bundle            # ... and the data and files its LaTeX reads
+pdfmd report --bundle            # ... and the image files too (the data and LaTeX inputs are carried anyway)
 pdfmd --restore report.pdf       # write the folder back into report.restored/
+pdfmd --check-source             # which PDFs in this folder carry their source (a file or folder works too)
 ```
 
+```console
+$ pdfmd --check-source
+NONE      WA1.pdf  no WA1.md beside it
+SOURCE    WA3.pdf  WA3.md, 52 lines, pdfmd 3.28.22
+NONE      WA5.pdf  WA5.md is beside it: pdfmd WA5.md --attach-source
+CHECK     3 PDFs: 1 with the source, 2 without
+```
+
+`--check-source` (alias `--sources`) only reads the attachment list, so it is quick on a whole folder; it notes a
+Markdown file beside the PDF that is newer than the build, and exits 1 when a PDF has no source.
+
 ```yaml
 pdfmd-options:
   attach-source: true            # alias: embed-source
-  bundle: true                   # or `all`: the whole folder, not just what the text points at
+  bundle: sources                # the default: the files the text reads, no images
+                                 # `true`: and the images · `all`: the whole folder · `false`: the source alone
   bundle-packages: true          # also your own LaTeX packages (see below)
   strip-comments: true           # the default for the attached copy; see "Comments"
   attach-bibliography: used      # or `all`
+  attach-csl: false              # the default: the citation style is named, not attached (see below)
 ```
 
 Put these in the shared metadata file and every document that finds it carries
 its source. The attachment is the assembled Markdown with the metadata,
-preamble, Lua filters, bibliography and CSL style folded in (the file
+preamble, Lua filters and bibliography folded in, and the CSL style too when `attach-csl: true` (the file
 `--assemble-only --embed-metadata` writes), plus a manifest of the original
 layout, so `--restore` gives back `report.md`, `metadata/`, `parts/` and the rest
 where they were, each as a standalone file (a symlinked metadata file or
@@ -818,17 +963,41 @@ style, a compound library, a shared bibliography and parts.
   a plain attach needs no bundle for them: a JPEG comes back byte for byte, a PNG
   as the same pixels (alpha kept), and an SVG or PDF figure as a vector PDF
   (`fig.svg` becomes `fig.pdf`, and the restored Markdown follows).
-- **`--bundle` is for what the PDF does not draw:** CSV data, LaTeX included
-  with `\input`, listings. They are stored as separate attachments (`files/...`),
-  found from the text, the preamble and, in turn, from the files found; also
-  those only your own TeX tree resolves (`\input{library}` from `texmf-home`).
-  `--bundle all` takes the whole folder except output and housekeeping. Over
-  100 MB (`bundle-max-mb`) only the source is attached. Data whose file name a
-  macro builds cannot be found: use `all`.
+- **The files the text reads travel with it.** CSV data, LaTeX included with `\input`, listings: stored as
+  separate attachments (`files/...`), found from the text, the preamble and, in turn, from the files found;
+  also those only your own TeX tree resolves (`\input{library}` from `texmf-home`). A restored report builds
+  again; only images are left out (the PDF has them). Over 100 MB (`bundle-max-mb`) only the source is
+  attached. `bundle: false` (or `--no-bundle`) keeps the source alone; `--bundle` (`bundle: true`) stores the
+  image files too, `--bundle all` the whole folder except output and housekeeping. Data whose file name a
+  macro builds cannot be found: use `all`. A Markdown output (`--keep-source`) has no PDF to take pictures
+  from and keeps the source alone unless you ask.
+- **`--restore` and `--unpack` stay short.** They count what they write by folder; `--verbose` lists every
+  file, and `--restore --list` always does.
 - **Your own LaTeX packages** (a house style in `texmf-home`) are recorded with
   their version, and `--restore` tells you what is missing; `--bundle-packages`
-  stores them too (with what they `\input` and the graphics they name).
-  The TeX distribution's own packages, fonts and Pandoc are not carried.
+  stores them too: the style file, the `<package>-pdfmd.yaml` beside it (what the package tells pdfmd: its
+  title-page keys, its picture-cache names), what it `\input`s and the graphics it hands to `\includegraphics`
+  (a logo named by `\newcommand{\LogoFile}{logo}`, not every word that happens to be a file's name). A package that sits
+  in the document's own folder, as it does in a restored source, is kept when the source is attached again. Together
+  with `attach-csl` a report that sets both in its shared metadata rebuilds on a machine with nothing of yours
+  installed (checked in an empty home folder). The TeX distribution's own packages, fonts and Pandoc are not carried.
+- **The text files are in the source's text.** The `.tex` files a document reads and its CSV data are blocks of the
+  attached `pdfmd-source.md`, after the text (`.tex` first, then the data) and before the bibliography and style at the
+  very end, so one file holds everything you edit; the pictures and your package stay separate attachments (and a file
+  that is not text, or too big, or whose line ends are mixed). `<!-- pdfmd-at: ... -->` comments say on which line each block is (an index after the front matter and one
+  before each part of the text that names a file); pdfmd writes them whenever it writes the source and removes them
+  wherever it reads one, so they never reach a build and a restore gives back your text as it was.
+- **Files in sibling folders** (`\input{../schemes/x.tex}`, a CSV in `../ir/`) are stored too, up to two folders above
+  the document's (never the home folder or above), as blocks of the text like the rest (their path starts with `..`),
+  and `--restore` puts the folder back in the same layout: the document in `<folder>/<its folder's name>/`, the siblings
+  beside it. A file with Windows line ends (CRLF all through) is a block with an `eol: crlf` line and comes back byte for
+  byte. `pdfmd --edit report.pdf` writes those files where the document reads them before every build, so editing a
+  block is editing the file; a build of the source file alone (no `--edit`) never writes outside its own folder and
+  says so when a file it reads from there is missing. A bibliography the metadata names by the real
+  folder of a symlinked metadata file (a shared `nulab.bib`) is embedded, pruned to the entries the text cites.
+- **A newer source is refused, not half restored.** The manifest has a format number (2 since v3.28.45, when the chain of
+  folders, the text files as blocks and the `..` files came in). A pdfmd that reads up to 1 stops with `was made by a
+  newer pdfmd (...); upgrade pdfmd to restore it`, and this one restores both 1 and 2.
 - **Comments.** Notes to yourself do not travel: the attached source loses its
   `<!-- -->` comments, the LaTeX preamble's `%` comments, the text between a
   `.bib`'s entries, a CSL file's XML comments and the `#` comments of YAML
@@ -841,9 +1010,18 @@ style, a compound library, a shared bibliography and parts.
   comments and quoting included; `--restore` of such a PDF is a full source
   copy. The data files of `.csv` blocks (`tables/*.csv`) are always stored
   with the source.
+- **Your global metadata (`pdfmd --setup`) stays yours.** It counts in the
+  source below the document's own files, as in a build, but `--restore` does
+  not write it back. It names its keys instead, and a build of the restored
+  folder uses the global metadata of the machine it runs on.
 - **Only the bibliography entries you cite** are attached (and what they
   cross-reference), not a shared file of hundreds; `attach-bibliography: all`
   keeps it whole, and `nocite: '@*'` keeps every entry.
+- **The citation style is not attached unless you ask** (`--attach-csl`, `attach-csl: true`, `--embed-metadata csl` for an
+  assembled file). A style is 10-90 KB (apa.csl 86 KB, nu-labreport.csl 72 KB, ieee.csl 18 KB) and the global metadata sets
+  one for every document, cited or not. A style is only ever attached when the document cites something. Without it the
+  manifest records the name and `--restore` says that a build needs a style of that name (Pandoc's own `csl/` folder, or
+  beside the document); a house style that exists nowhere else should travel, so set `attach-csl: true` for it.
 - **It is opt-in, and it is everything you wrote.** An attached source includes
   what the author would not send in an email; check `--list` before sharing.
 - `--restore` never overwrites a file and never writes outside its folder. A
@@ -945,9 +1123,9 @@ stamped or backed up unless you ask (`stamp=True`, `backup=True`). A failure rai
 `variables=` a dict of Pandoc variables, `extra_args=` anything else the command line takes, `cwd=` the folder it runs
 in and `timeout=` seconds.
 
-### Other command names: `mdpdf` and `inkmd`
+### Other command names: `mdpdf`, `inkmd`, `batchmd` and `pan-tec`
 
-pdfmd also installs `mdpdf` and `inkmd` commands that take those tools' own keys
+pdfmd also installs `mdpdf`, `inkmd`, `batchmd` and `pan-tec` commands that take those tools' own keys
 and do what they did, with pdfmd behind them:
 
 ```sh
@@ -955,8 +1133,18 @@ mdpdf -o out.pdf -f ",,{page}" -a "Name" -p A4 chapter1.md chapter2.md
 inkmd notes.md -o notes.pdf --page-size a4 --family times
 cat notes.md | inkmd > notes.pdf            # standard input and output, like inkmd
 inkmd notes.md -e lualatex                   # naming another engine uses it instead
+batchmd ~/notes                              # every .md in the folder, as pdfmd -b ~/notes
+batchmd -e inkmd                             # the current folder, with the built-in renderer
 ```
 
+`pan-tec` is the first version of pdfmd, a shell function around `pandoc "$@" --pdf-engine=tectonic --pdf-engine-opt=--chatter=minimal`
+(v3.29): `pan-tec test.md -o ex.pdf` is `pdfmd -e tectonic test.md -o ex.pdf --pdf-engine-opt=--chatter=minimal`, with everything else
+pdfmd does. Name another engine (`-e typst`) or a chatter level of your own and that is used instead.
+
+`batchmd` is `pdfmd -b`: each Markdown file in the folder becomes its own PDF beside it.
+It takes the current folder when you name none (`pdfmd -b` alone refuses), and every
+other option is pdfmd's.
+
 `mdpdf` turns bookmarks and attached links on and combines several inputs into one
 PDF. `inkmd` is `pdfmd -e inkmd`; like inkmd it writes the PDF to standard output
 when you give `-o -`, or no `-o` while output is piped (at a terminal it writes
@@ -979,16 +1167,17 @@ pdfmd slides -p                   # Beamer slides; each heading starts a slide
 
 ```console
 $ pdfmd notes -b
-AUTO: READER TITLE MARGIN MONOFONT. Use --verbose to see in full
-AUTO: MARGIN. Use --verbose to see in full
-AUTO: MARGIN. Use --verbose to see in full
-OK    notes/lecture.md
-OK    notes/week1.md
-OK    notes/week2.md
+DEFAULTS  margin 1in, font STIX Two Text, code in JetBrains Mono, title from heading
+AUTO: READER. Use --verbose to see in full
+OK    notes/lecture.md > lecture.pdf
+OK    notes/week1.md > week1.pdf
+OK    notes/week2.md > week2.pdf
 ```
 
 `-b` converts every `.md` in the folder into its own PDF, in parallel
-(`-j N` sets the number of workers). Add `--recursive` to include
+(`-j N` sets the number of workers). `--bopen SPEC` opens some of the finished files when
+the batch is done: `f5` the first five, `l5` the last five, `fl10` the first five and the last five, `e3` the third, sixth, ninth ... file, `s3` the first, fourth, seventh ... (Python's `[::3]`),
+`f2,l3` a mix, or none for all (any number works; the files open in the order the batch lists them). Add `--recursive` to include
 subfolders, and `-o DIR` to collect the PDFs somewhere else.
 
 ### A book or report from several files
@@ -997,7 +1186,7 @@ subfolders, and `-o DIR` to collect the PDFs somewhere else.
 $ pdfmd book -r -o book.pdf
 OK    book/01-intro.md
 OK    book/02-methods.md
-AUTO: MARGIN. Use --verbose to see in full
+DEFAULTS  margin 1in, font STIX Two Text
 OK    REPORT  book.pdf
 ```
 
@@ -1053,11 +1242,16 @@ section, figure, table or equation outside the part then prints its number
 own sections, figures and equations continue from the parts before it. What the
 scan cannot count is whatever the document defines itself (a macro that opens
 a figure, say): that label stays `??`, and the build says the numbers are
-approximate. `\pageref` is always `??`. The last full build's `.aux` (cache on,
+approximate. So does a label after a caption in an environment the document
+defines itself (a table wrapper of a house style): it prints `??`, never the
+number of the heading before it, and the build says how many there were.
+`\pageref` is always `??`. The last full build's `.aux` (cache on,
 below) is exact and is used first; the scan fills in what it does not know.
 `pdfmd-options: {seed-labels: auto|aux|scan|draft|off}` or `--seed-labels` picks
-the source (`draft` runs LaTeX once over the whole document without output, for
-exact numbers at about half a compile's cost); `off` brings back the `??`. A section of an ordinary document
+the source (`draft` runs LaTeX once over the whole document without output and
+without drawing its pictures, TikZ, pgfplots, chemfig and images, for exact
+numbers at a fraction of a compile, though a page reference into what was left out
+prints `??`; `--no-auto draftpictures` draws them); `off` brings back the `??`. A section of an ordinary document
 (`doc#results`) gets the same for the references it makes, but keeps numbering
 its own headings from 1.
 
@@ -1084,11 +1278,27 @@ from the last full build; without the cache they are counted from the
 sources, above). It never skips a build: Pandoc and
 LaTeX still process the whole document from the current sources and package
 every time, so a change shows in the next build. `cache: {plots: true}` (or
-`--cache-plots`, with nulabreport >= 1.26.0) additionally stores each plot as a
-PDF and reuses it until the package, the preamble, the engine or the plot's
-data file changes. Off by default; `--no-cache` for one build; `pdfmd --clear-cache`
+`--cache-plots`; LuaLaTeX) additionally stores each whole picture of a package that takes part
+(nulabreport's plots and chemical schemes do) as a
+PDF in the document's cache folder and reuses it (a part built alone uses the whole
+document's, unless its preamble differs by more than the title) until the package,
+the preamble, the engine, TeX Live's packages (a `tlmgr update`) or a file the plot
+read changes (its data file, a file of the package's own: checked by
+SHA-1 of the contents before every build). Off by default; `--no-cache` for one build; `pdfmd --clear-cache`
 (or deleting the folder) is always safe.
 
+*For a package author:* the protocol names no package. A style file that mentions `pdfmdCacheDir` takes part; pdfmd then
+defines `\pdfmdCacheDir` (the folder, with a trailing slash) and `\pdfmdCacheVersion` (3: the markers below are version 3) before the document. The package looks
+a picture up by its own key as `<folder>/<key>.pdf` with its size in `<key>.dim` (`\pdfmdCacheWd`, `Ht`, `Dp`), typesets
+inline on a miss, and appends `<key>@@|@@<macro>@@|@@<arguments>@@|@@<context>` to `<job>.pdfmdreq`. After the build pdfmd
+runs each request in a standalone job with the same preamble (`\pdfmdCacheRender` defined, so there is no lookup): the
+context, then `\setbox0\hbox{<macro><arguments>}`; that box is the page. A context may hold `@@plain@@` (what follows is read
+with ordinary catcodes, not expl3's: settings with spaces in their names), `@@runs=2@@` (typeset twice, for a picture
+whose arrows point at its own nodes) and `@@margin=56pt@@` (the page is the box plus that on every side, `\pdfmdCacheMargin` in
+the `.dim`: for ink that overflows its box, which you include shifted back). If the job defines `\pdfmdCachePost` after the
+box, its text comes back as `\pdfmdCachePostStored` in the `.dim`, for you to run on a hit (a global the picture changes). nulabreport's first names (`\LabPlotCacheDir`, `.plotreq`, `\Lab@pc@wd`) still work as
+aliases.
+
 **Where the cache lives.** By default in `~/.cache/pdfmd`, one folder per document.
 Folders get moved (a lab report from Downloads into OneDrive), and a cache keyed by
 the old path would be lost: so each cache folder records which document it is, and a
@@ -1141,16 +1351,25 @@ Water,18.015,1.20
   braces, with the identifier as `#tbl:id` there too. A caption in the attributes wins over a line after the block.
 - A relative `file=` is found beside the document (and along the resource path), wherever Pandoc runs. With both
   `file=` and data inside the block, the file is used.
-- The delimiter is `delimiter=";"` or its name (`semicolon`, `tab`, `pipe`, `space`, `colon`, `comma`); without one it
-  comes from the extension (`.tsv` means tab) or from the first line (whichever of `,` `;` tab `|` it holds most of).
+- The delimiter is `delimiter=";"` or its name (`semicolon`, `tab`, `pipe`, `space`, `colon`, `comma`), or
+  `pdfmd-options: {csv: {delimiter: semicolon}}` for every table; without one it is guessed: whichever of `,` `;` tab `|`
+  splits the first lines into the same number of fields (the extension's own, comma or tab for `.tsv`, on a tie). When
+  the guess is not what the file's name says (a `;` file named `.csv`), the build warns and says how to name it.
 - Columns are aligned with `align="lcr"` (or `align="left,center,right"`), or by a second row in the data made of
   `---`, `:--`, `:-:`, `--:` as in a pipe table; `align=` wins. If such a row is really data, say `separator="none"`.
   `widths="5,1,1"` sets relative widths, and a second row with unequal dashes does too. Without either, pdfmd picks
   widths that suit the contents.
 - The first row is the header unless you add `header="false"`.
 - Large files are capped at 10 rows × 7 columns, so a huge CSV can't
-  silently fill 40 pages. `rows=all` or `cols=20` raise the cap. When a
-  table is cut, the PDF itself shows a note saying so.
+  silently fill 40 pages. A cut table keeps both ends: the first 7 rows, a row
+  of `…`, the last 3, and the first 5 columns, a `…` column, the last 2 (about
+  any cap keeps its last ⌊√cap⌋: 16 + 4 of 20, 25 + 5 of 30; `cut="head"` or `csv: {cut: head}` keeps the first
+  ones only). `rows=all` or `cols=20` raise the cap. When a table is cut, the
+  build warns and the PDF itself shows a note saying so. For every table of a
+  document: `--csv-rows N|all` / `--csv-cols N|all`, or
+  `pdfmd-options: {csv: {rows: all, cols: 12, cut: ends, delimiter: auto, header: false, reader: gfm}}`
+  (in the front matter, a metadata file, or the config, where `pdfmd --setup`
+  sets rows, columns, the cut and the delimiter); a div's own attributes still win.
 
 This works for every output format.
 
@@ -1183,6 +1402,38 @@ line above it (or under its caption); the comment survives comment stripping, be
 A comment between a table and its caption would stop Pandoc from reading the caption as one, so there is no such
 position.
 
+### One style sheet for the page: `--css`, `pdfmd.css`, `css-scope`
+
+A `.css` file styles the writers that read CSS: HTML, EPUB, the PDF the HTML engines make (WeasyPrint and the rest) and
+Calibre. pdfmd finds `pdfmd.css` or `<name>.css` beside the document (and in its `metadata/` folder; `--no-auto css` turns the
+search off), takes `css:` from the front matter or a metadata file (Pandoc's own key), `pdfmd-options: {css: file.css}`
+(a name or a list; `pdfmd --setup` keeps one for every document) and `--css FILE`; they come in that order, the last after the
+others, as in CSS.
+
+```css
+@page { size: A4; margin: 2cm 2.5cm }                 /* paper and margins */
+body  { font-family: "STIX Two Text"; font-size: 11pt; line-height: 1.3; text-indent: 1.2em }
+a     { color: #0645AD }                              /* links */
+code, pre { font-family: "JetBrains Mono" }
+```
+
+With `css-scope: all` (`pdfmd-options`, or `--css-scope all`; the default is `html`) the sheet is read for the other writers
+too: those four rules become the paper, margins, font, size, line spacing, indent, link colour and code font that LaTeX,
+Typst and Word take, **below** what the document, its metadata and the command line set (`--verbose` says
+"body font-size 11pt -> fontsize=11pt" for each one it used, and names what it did not: tables, anything else).
+Only rules that say it plainly count: `@page`, `html`/`body`/`:root`, `a`, `code`/`pre`, `h1`-`h5`; the last one wins. A media
+query is read as a browser prints (v3.29): `print` and `all` apply, `screen` and the other media types do not, a comma is "or",
+`only` and `not` count, `(orientation: landscape)` is read against the sheet's own `@page` size, and a feature of the screen or of
+a width (`(min-width: 600px)`) is not for a printed page and is named. A body size LaTeX has no class for (anything but 10, 11
+and 12 pt) is named, not used. It is a small reader on purpose: a CSS cascade has no counterpart in LaTeX.
+
+Headings (v3.29): `h1`-`h5` with a `color`, `font-size` (`em`, `%`, `pt`, `px`: of the body's size), `font-family`,
+`font-weight` or `font-style` are set for LaTeX too, as titlesec's starred formats (the numbering and the spacing stay the
+class's; `h1` is `\section`, `h2` `\subsection` ... `h5` `\subparagraph`; `h6` has no LaTeX level). It is done only for the plain
+article class, and never over a document that formats its headings itself: a `titlesec`, `sectsty`, KOMA or memoir command, or a
+`\section` of its own, in the preamble, the `header-includes` or a metadata file, is named in a `CSS` note and nothing is added
+(and when `titlesec` is not installed, one LaTeX warning says so). A family needs XeLaTeX or LuaLaTeX.
+
 ### Code: wrapping and line numbers
 
 With a LaTeX engine a long line of code wraps at the margin instead of running off the page (a long path or option list
@@ -1238,7 +1489,12 @@ Drawings are kept in the cache by their content, so a rebuild does not draw them
 (`{#fig:id}` with pandoc-crossref numbers it), `width=` sizes it, `engine=` picks the Graphviz layout (`dot`, `neato`,
 `fdp`, `sfdp`, `circo`, `twopi`), `theme=` the Mermaid theme, `layout=` the D2 layout (`dagre`, `elk`). A tool that is
 not installed leaves the block as code with one warning (`--strict` makes it an error) and says how to install it;
-a diagram the tool cannot parse stays as code too. `pdfmd --doctor` shows which tools are there, and
+a diagram the tool cannot parse stays as code too, and the warning gives the tool's own words. `pdfmd --install diagram:d2`
+puts D2's release binary (17 MB, checked against the SHA-256 GitHub lists) in pdfmd's tools folder, and `--install
+diagram:dot` Graphviz built to WebAssembly (2 MB, run by node, which pdfmd fetches when there is none): it writes only SVG,
+which pdfmd converts for a PDF or Word picture with `rsvg-convert` or `inkscape` (D2 needs the same), and it sizes labels
+by Graphviz's own estimate of the font, a couple of percent off the real tool's. A tool of your own on PATH is always the one
+that runs. `pdfmd --doctor` shows which tools are there, and
 `--no-auto diagrams` turns the whole thing off. The attributes need Pandoc's Markdown (a file with front matter); a file
 read as gfm takes the plain ```` ```dot ```` form. Mermaid needs Chrome (mermaid-cli downloads one); in a sandbox
 `PDFMD_MMDC_CONFIG=puppeteer.json` is handed to `mmdc -p`.
@@ -1294,6 +1550,30 @@ in HTML, Typst and flat Markdown builds (an SVG for HTML and Markdown; a piece t
 out). Not yet: HTML drawn as a picture, Word XML as
 anything but Word XML.
 
+**Page breaks in every format.** Each output understands one way of writing a page break and drops the others: LaTeX
+takes `\newpage`, WeasyPrint a CSS-break `<div>`, Word only its own XML, Typst none of them. Ask for it and every
+spelling of the families you name becomes the output's own (LaTeX `\newpage`, Typst `#pagebreak`, a CSS break for HTML,
+EPUB and WeasyPrint, a Word or OpenDocument page break, a form feed in `--to txt`, `<!-- pagebreak -->` in `--to gfm`):
+
+```yaml
+pdfmd-options:
+  pagebreak: true              # every family; or a list of them:
+  # pagebreak: [comment, tex]
+```
+
+| family | spellings |
+|---|---|
+| `comment` | `<!-- pagebreak -->`, `<!-- page-break -->`, `<!-- newpage -->`, `<!-- new-page -->`, `<!-- pdfmd: pagebreak -->` |
+| `tex` | `\newpage`, `\pagebreak`, `\pagebreak[3]`, `\clearpage`, `\cleardoublepage` (an odd page) |
+| `html` | `<div style="page-break-after: always"></div>` (or `break-before: page`), `<div class="pagebreak"></div>`, `<hr class="pagebreak">` |
+| `div` | an empty `::: pagebreak` (or `newpage`) |
+| `typst` | a raw `` ```{=typst} `` `#pagebreak()` |
+| `word` | a raw `` ```{=openxml} `` page-break paragraph |
+
+It is off unless asked (the document, a metadata file, or `pdfmd --setup` under *Universal markup*); `--pagebreak
+[KIND ...]` and `--no-pagebreak` decide for one run. A spelling already in the output's own language stays as written,
+and slides leave a break out with a note. The built-in renderer (no Pandoc) reads the comment and TeX spellings anyway.
+
 **PDF images in HTML.** A browser does not show a PDF in `<img>`, an SVG it does. For an HTML build (a web page, an
 EPUB, a PDF through WeasyPrint) every image that is a PDF, `![fig](plot.pdf)` or `<img src="plot.pdf">`, is converted to
 an SVG with poppler's `pdftocairo` (or `mutool`, `pdf2svg`, `inkscape`) and stays vector; the first page is used and the
@@ -1308,16 +1588,16 @@ pdfmd paper.tex          # compiled directly with a LaTeX engine: reruns until
                          # no .aux/.log clutter (--keep-aux keeps them)
 pdfmd minutes.docx       # Word/PowerPoint/Excel/ODF: converted by LibreOffice
 pdfmd analysis.qmd       # handed to Quarto, so code chunks actually run
-pdfmd page.html          # built by WeasyPrint, or a browser if the page runs scripts: no Pandoc
+pdfmd page.html          # built by WeasyPrint, or a browser if the page runs scripts or has MathML: no Pandoc
 pdfmd note.typ           # compiled by Typst itself: the page setup in the file is kept
 pdfmd notes.rst          # anything else Pandoc can read (give the extension)
 ```
 
 A finished `.typ` or `.html` file goes straight to its own engine, because Pandoc would read it into its own model
 and write it out again, and the page size, the styles and the scripts would not survive the trip. For a page that is
-WeasyPrint first (it is quiet and needs no browser); a page with `<script>` goes to Chrome, Chromium, Edge or Brave
-(headless, printing the page), as does one WeasyPrint cannot draw, and wkhtmltopdf, Prince, pagedjs-cli and LibreOffice
-come after. `-e edge` (or `weasyprint`, `chromium`...) picks one. As with an Office file, such a document gets none of
+WeasyPrint first (it is quiet and needs no browser); a page with `<script>` or MathML (`<math>`, which WeasyPrint prints
+as flat text) goes to Chrome, Chromium, Edge or Brave (headless, printing the page), as does one WeasyPrint cannot draw,
+and wkhtmltopdf, Prince, pagedjs-cli and LibreOffice come after. `-e edge` (or `weasyprint`, `chromium`...) picks one. As with an Office file, such a document gets none of
 pdfmd's defaults, since it is finished; `--apply-defaults` (also in `pdfmd --setup`) gives it the title, author, date,
 language, font, font size, paper and margin of its `metadata.yaml`, ahead of its own settings so those win. A `.tex`
 file that no LaTeX engine can compile is tried through Pandoc, with a warning.
@@ -1345,6 +1625,7 @@ Most of these print an `AUTO` line, and each can be switched off individually.
 | `TITLE` | a Markdown file with no front matter, first line is `# Title` | that heading becomes the document title, and the remaining headings move up one level |
 | `MARGIN` | no margin or geometry set anywhere | 1-inch margins instead of LaTeX's wide defaults |
 | `MAINFONT` | no `mainfont:` and no `-f` | STIX Two Text (Times New Roman if it isn't installed), or a serif that has the letters when the document is mostly in a script STIX Two Text lacks (Kazakh Cyrillic, say); retried with DejaVu Serif if a glyph is still missing. A font you name is never changed except by `fallback: document` |
+| `MATHFONT` | pdfmd chose the main font itself (no `-f`, no `mainfont:`/`mathfont:` in the document or its metadata), the engine is LuaLaTeX, XeLaTeX, Tectonic or Typst (Pandoc 3.12+), and the companion is installed | the math font that goes with the text font: STIX Two Math for STIX Two Text, DejaVu Math TeX Gyre for DejaVu Serif, Libertinus Math, New Computer Modern Math, TeX Gyre Termes/Pagella Math; without it formulas are set in Latin Modern Math (Typst: New Computer Modern Math). `--no-auto mathfont` (or `font`) stops it |
 | `UNICODE` | text the main font cannot draw (Arabic, Han, Greek with accents, rare symbols...) | sets each run in an installed font for its script (see *Other scripts*), instead of printing boxes |
 | `MONOFONT` | the document contains code | JetBrains Mono for code (Menlo or another installed monospace font if it isn't installed) |
 | `tablewidth` | a pipe table with plain `---` separators and long lines | picks the column widths that give the fewest lines within the text width (a column never narrower than its longest word), and gives a table that fits its natural width back; unequal dashes (`--|-----`) are kept, and `table-widths: keep` in `pdfmd-options` leaves every table as written |
@@ -1353,8 +1634,11 @@ Most of these print an `AUTO` line, and each can be switched off individually.
 | `codewrap` | code blocks in a LaTeX build | long lines wrap at the margin (`--no-code-wrap` or `--no-auto codewrap` for the old behaviour) |
 | `YAML` / `TEX` / `LUA` | project files found | attaches `metadata.yaml`, `preamble.tex`, `<name>.lua` (see below) |
 | `citeproc` | `@key` / `[@key, p. 90]` citations (as Pandoc reads them: `@key` in a code span or an e-mail address is none) | adds `--citeproc`, so citations and the reference list render from your `bibliography:` without any flag (`--no-citeproc` turns it off) |
+| `remotecsl` | `csl: https://.../ieee.csl` in the front matter or a metadata file | fetches the style once and keeps it (again after 30 days), so a Pandoc built without HTTP support and a build with no network still work: offline it takes that copy, else a style of the same name in Pandoc's own `csl/` folder, with a WARN, else Pandoc's default style with a WARN (`pdfmd-options: {csl-fallback: error}` stops instead) |
 | `crossref` | `@fig:`/`@tbl:` references or `{#fig:...}` labels | adds the `pandoc-crossref` filter, ahead of citeproc |
 | `papersize` | `pagesize: a4` (a common typo) | converts it to Pandoc's real `papersize:` |
+| `texpackages` | `\ce{H2O}` (mhchem) or `\SI{25}{\celsius}`, `\num`, `\qty` (siunitx) in a LaTeX build whose preamble does not load the package | loads it, last in the preamble, unless it is loaded already (your options win), the command is defined some other way, or the package is not installed |
+| `draftpictures` | a part (or section) built alone with `seed-labels: draft` | the draft pass over the whole document does not draw TikZ pictures (pgfplots too), `\chemfig`, chemfig schemes or images: they step no counter. A page reference into what was left out prints `??`; a picture that ends inside a macro makes pdfmd run the pass again with the pictures |
 
 `-v` explains each decision and prints the exact command it runs:
 
@@ -1366,7 +1650,7 @@ AUTO READER  lecture.md: no YAML front matter; reading as gfm
 AUTO TITLE  lecture.md: promoted leading '# ' heading to Pandoc title metadata
 AUTO MARGIN  lecture.md: no geometry/margin set; using geometry:margin=1in on LaTeX-family engines
 AUTO MONOFONT  lecture.md: has code but no monofont set; using JetBrains Mono on LaTeX-family engines
-OK    lecture.md  (lualatex)
+OK    lecture.md > lecture.pdf  (lualatex)
 ```
 
 The second `CMD` line is the font fallback at work: STIX Two Text was
@@ -1383,12 +1667,32 @@ build that quietly fell back to Typst does not look like one that did not:
 $ pdfmd paper
 WARN  paper.md: lualatex failed (! Undefined control sequence.); trying xelatex...
 WARN  paper.md: xelatex failed (! Undefined control sequence.); trying typst...
-OK    paper.md  (typst; lualatex, xelatex failed)
+OK    paper.md > paper.pdf  (typst; lualatex, xelatex failed)
 ```
 
 When LaTeX itself stops, the warning also says where: Pandoc reports a line of the LaTeX it wrote, so pdfmd finds those
 words in your Markdown and prints `near line 9 of paper.md: ...has \badmacro`.
 
+WeasyPrint does not typeset math itself. With MathJax in place, `pdfmd --install math:mathjax` (MathJax 4.1's TeX input
+and HTML output and the STIX Two math font, which goes with pdfmd's default body font: about 12 MB to download, about 2 MB
+on disk in `~/.local/share/pdfmd/mathjax`, each package pinned and checked against its SHA-256; and node, when there is
+none on your PATH: node's own release from nodejs.org, about 30 MB, checked the same way, into pdfmd's tools folder), a
+Markdown document built with `-e weasyprint` (or one that falls back to it) has its math typeset by MathJax before
+WeasyPrint prints it: fractions, roots, matrices, accents, limits, stretchy arrows and braces, `\ce` reactions, in the
+STIX Two Math, sized to the body font's x-height when the body is not STIX Two Text. (MathJax's other math fonts, New
+Computer Modern, TeX Gyre Termes and Pagella and DejaVu, are not offered yet: their tall delimiters built from pieces came
+out broken in WeasyPrint.) WeasyPrint draws some of MathJax's output a little off (an accent three points over its letter, a
+fraction's denominator too low, a bar that ran past its letter); pdfmd's own style rules put that right. A formula MathJax cannot read goes to KaTeX when `pdfmd --install math:katex` has put it in place (a `NOTE` says
+how many), and a formula neither reads (a macro from your LaTeX preamble, say) stays text, with one `WARN` for all of
+them. KaTeX alone, without MathJax, does what it did: `--no-auto mathjax` asks for that. Without either, the math is
+Pandoc's plain math, simple formulas in Unicode (`αᵢ ≤ β`) and the others as their TeX, with one `WARN`; Typst or a
+LaTeX engine typesets them. A math option of your own (`--mathml`, `--math-method=...`) is kept, and `--doctor` says
+which of them you get.
+
+A link to an anchor the document does not have (`[see 13.5](#135-your-own-defaults)` quoted from another document) is
+only a warning for LaTeX and HTML, but Typst stops on it. For Typst, PDF or `.typ`, such a link becomes its text, and
+one `WARN` names the anchors.
+
 `--strict` (or `pdfmd-options: {strict: true}` in the document; `--no-strict` overrides it) makes that, and every other
 warning, an error for scripts and CI: a file whose build printed a `WARN` line, or about which Pandoc warned (an image
 or citation it could not find, a LaTeX reference left undefined), is reported `FAIL` with the first warnings listed and
@@ -1534,21 +1838,45 @@ options:
   pdf-engine: lualatex
 ```
 
-**`pdfmd --setup`** changes the same defaults from a menu, without editing the files: a numbered list (nothing to
+**`pdfmd --setup`** (or `pdfmd --config`) changes the same defaults from a menu, without editing the files: a numbered list (nothing to
 install, works over ssh), each setting with its choices and what they mean. It covers what a document would otherwise
 say in `pdfmd-options:` or its front matter, for every document:
 
 - *global metadata* (a `metadata.yaml` beside the config file, below anything a document's own folder says): author, language,
   paper size, font size, page geometry, main and code font, line spacing, coloured links, table of contents, and for
   citations the bibliography file, the CSL style and linked citations;
+  The global metadata can be switched off (`--no-global-metadata`, `pdfmd-options: {global-metadata: false}`, or
+  the *Use the global metadata* row; `--global-metadata` turns it back on for one run) and replaced by a **preset**: another
+  file, `presets/NAME.yaml` beside the config file. `--preset lab` (or `lab.yaml`, or a path), `pdfmd-options: {preset: lab}`
+  in a document or a folder's metadata, or the *Which set of global metadata* row chooses it; `--preset none` takes no global
+  metadata, `default` is `metadata.yaml`. `pdfmd --setup --preset lab` edits that preset's rows (it makes the file), and
+  `pdfmd --presets` lists them and marks the one a build here would use. The command line wins, then the document, then the
+  folder's metadata, then the config.
 - characters a font lacks or none draws, fonts for other scripts, romanization packs;
-- the citation engine, the PDF engine, the default output format, HTML (one file, math method), LaTeX and reference
-  numbers in Word files;
-- PDF finishing (header, footer, bookmarks, attached links) and the source file (the "Compiled with..." stamp, backups,
-  comment stripping, attaching the source and its files to the PDF);
-- the cache, reading `.txt` as Markdown, and which of pdfmd's automatic behaviours (`--no-auto` kinds) are off.
-
-Choosing 0 (for a text, `-`) gives a setting its built-in default back; `s` saves, `q` quits. The files are rewritten without your
+- the citation engine; output (the PDF engine, the default output format, defaults for `.typ` and `.html` files);
+  HTML (full page, one file, style sheet, math method); tables (the rows, columns, cut and delimiter of `.csv` tables,
+  pipe-table widths); code (wrapping, line numbers); Word and OpenDocument (LaTeX in them, reference numbers, the
+  template);
+- plain Markdown, text and ASCII output (`--to gfm`, `txt`, `ascii`: scripts, math, title block, the source carried at
+  the end);
+- PDF finishing (header, footer, bookmarks, attached links, a hybrid PDF); the build history (the "Compiled with..."
+  stamp and its details); backups (their folder, names and how many are kept); the source inside the PDF (attaching
+  the source, its files and its LaTeX packages, comment stripping);
+- the cache (reference numbers, plots, a part built alone); input (the Markdown reader, reading `.txt` as Markdown, raw
+  pieces);
+- checks and limits (`--strict`, the size budgets, the codes `--check` leaves out), and which of pdfmd's automatic
+  behaviours (`--no-auto` kinds) are off.
+
+Every flag and every `pdfmd-options` key is either one of these rows or left out on purpose: `o` lists the rest (commands,
+what is about one run or one document, trust, what pdfmd writes for itself) with the reason, and a test keeps that
+complete. Choosing 0 (for a text, `-`) gives a setting its built-in default back; `s` saves, `q` quits.
+
+**Switching whole features off.** `d` in `--setup` (or `disabled: [history, tables]` in `config.yaml`) switches off
+features you never use: modes, source, tables, history, code, raw, markdown, fonts, builtin, office, cache (the topics
+of `--help`; output, setup and debug stay on). Their options leave `--help`, shell completion (regenerate it with
+`--completion`) and the setup screen, and the command line refuses them; `pdfmd --disabled --history doc` uses one for a
+single run and `pdfmd --disabled --help all` shows them. A document's own `pdfmd-options` still apply, so a document
+from someone else builds the same. In the full-screen setup, `r` resets a row (it used to be `d`). The files are rewritten without your
 comments (the old one is kept as `.bak`). The same keys can be written by hand under `options:` of `config.yaml`. A
 full-screen version is optional: `pdfmd --install tui` (prompt_toolkit, about 1 MB), then `pdfmd --setup fancy`, or set
 "This setup screen" to fancy to make it the one `pdfmd --setup` opens. The first time pdfmd finishes a build in a terminal
@@ -1579,6 +1907,24 @@ files could apply and none is clearly meant, `pdfmd` stops and asks you to
 choose with `-y FILE`, rather than guessing. `-y` alone turns discovery
 off.
 
+**When two metadata files set the same key, the later one wins**, as in Pandoc:
+`<name>.yaml` over `metadata.yaml`, `report.yaml` over `metadata.yaml`, and the
+second of `-y base.yaml -y extra.yaml`. This holds for Pandoc's keys and for
+pdfmd's own (`pdfmd-options:`, `margin:`), key by key: the earlier file still
+gives whatever the later one leaves out. The document's own front matter beats
+every file. `--metadata-precedence first` (or `metadata-precedence: first` in
+`pdfmd --setup`, under Input) turns this round so that the first file wins.
+Until 3.27.22, pdfmd's own keys followed that `first` rule while Pandoc's followed
+the later file.
+
+A `header-includes:` stays when a preamble file joins it: the document's own, or
+else the one of the metadata file that wins (above). The same holds
+for the header files pdfmd adds itself, such as the code-wrapping header of a
+document with code. A metadata file's lines go before `preamble.tex`, and the
+document's own go after everything. An `--include-in-header` you pass yourself
+replaces them all, as it does in Pandoc. The global `metadata.yaml` that
+`pdfmd --setup` writes is the lowest of all metadata files.
+
 With a `metadata/` folder, a report's own folder can hold nothing but
 `report.md` and `report.pdf`. Relative paths inside the metadata (such as
 `bibliography: refs.bib`) resolve from `metadata/`, and image paths in the
@@ -1662,3 +2008,7 @@ read with `pdfinfo -meta`. Turn this off with `--no-stamp-pdf-metadata`.
 ## License
 
 [MIT](https://github.com/aliperdehan/pdfmd/blob/main/LICENSE)
+
+`pdfmd_mhchem/` is a Python port of Martin Hensel's
+[mhchemParser](https://github.com/mhchem/mhchemParser) (the parser of mhchem's `\ce` and `\pu` that MathJax and KaTeX
+use) and keeps its [Apache License 2.0](https://github.com/aliperdehan/pdfmd/blob/main/pdfmd_mhchem/LICENSE).