| Age | Commit message (Collapse) | Author |
|
|
|
|
|
|
|
Previously we added semicolons after inline commands not
followed by spaces, but mainly this was to deal with one issue:
the presence of a semicolon after an inline command, which
would be swallowed as a command separator (#9252).
This commits adopts an approach that should avoid so many
superfluous semicolons: it escapes semicolons that might come
right after a command. See #11196.
|
|
|
|
Only a relative path can be used here.
See #11190.
|
|
A template change in 3.8 added a show rule for links which
causes them to disappear except in special cases.
This change fixes the problem.
Closes #11194.
|
|
Use accumulator.
|
|
As in #1294 \url and \href need to be protected
inside an mbox for soul commands.
Closes #9366.
|
|
|
|
macos-13 will be retired by Dec. 4, 2025.
|
|
When `table_attributes` is enabled (as it is by default for
pandoc's Markdown), attributes can be attached to a table by
including them at the end of the caption. Previously the writer
would emit an identifier in this position, but the reader didn't
handle it. Now arbitrary attributes are allowed, and they work in
both the reader and writer.
Closes #10884.
[API change]: Text.Pandoc.Extensions: Add `Ext_table_attributes`
constructor for `Extension`.
|
|
in COPYING.
|
|
|
|
Closes #11178.
In documenting LaTeX packages used by generated documents, don’t mention
some packages twice in one (already long) paragraph.
Add missing link for multirow.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Closes #11176.
|
|
Closes #10127.
|
|
This was causing links in iOS books app not to be distinguished in
any way (since underlining is not used there).
Closes #11174.
|
|
beamer uses pdfstring for the pdfinfo which can't handle soul strikeouts.
Therefore, the title, subtitle and author contents need to be put inside
texorpdfstring to deal with both the pdfinfo as well as the formatting.
Fixes #11168.
|
|
See #11171. Previously the native typst highlighting was
always used, regardless of the setting of `--syntax-highlighting`.
With this change, `--syntax-highlighting=none` and
`--syntax-highlighting=<style name>` (with skylighting) will work.
Completes #10525.
|
|
[API change] New exported functions `formatTypstBlock`,
`formatTypstInline`, `styleToTypst`.
|
|
|
|
Previously they would appear before the content to which
the note was attached, when there were pauses in a slide.
Closes #5954.
See related discussion in https://github.com/josephwright/beamer/issues/565.
|
|
If true, pandoc will allow language-specific shorthands
when loading babel.
Closes #11160.
|
|
Closes #11162.
|
|
Add missing header rows after the first one,
footer rows as well as TableBody header rows.
Also apply hlint suggestions to use Down and fuse mapM/map.
Closes #10002.
|
|
We added DefaultHighlighting in commit 6475725 but didn't adjust the
pattern-match here.
Closes #11156.
|
|
Previously these were omitted. Closes #11028.
|
|
Since underscores are common in filenames, and pandoc will
render strings to variables using default LaTeX escaping, we
special-case `bibliography`, under the assumption that this variable
will be used in the context of the `\bibliography{..}` command,
which accepts unescaped underscores.
Closes #11152.
|
|
|
|
Closes #11150.
|
|
containts non-tabular content.
|
|
Leading space in a cell should not cause the contents to
be parsed as a block quote.
Closes #11146.
|
|
This should only be used if sectPr is not found.
|
|
Previously we assumed that every table took up the full text
width. Now we read the text width from the document's
sectPr.
Closes #9837.
Closes #11147.
|
|
This way we can update them with `--accept`.
|
|
Closes #11141.
|
|
|
|
We do not allow inline notes to be followed by `(` or `[`.
Otherwise, we parse inline notes before superscripts.
This fixes #8652.
Also, the sub/superscript parsers have been adjusted so that they
really exclude unescaped spaces (as they did not before, when the
spaces occurred in nested inlines). See #5878 for comment.
|
|
|
|
Support for vimdoc, documentation format used by vim in its help pages.
Relies heavily on definition lists and precise text alignment to generate tags.
|
|
|
|
Third issue in #11140.
|
|
Allow implicit figures when alt text differs from caption
(in this case, we use an image attribute to add the alt).
Closes #11140.
|