| 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.
|
|
Use accumulator.
|
|
As in #1294 \url and \href need to be protected
inside an mbox for soul commands.
Closes #9366.
|
|
|
|
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`.
|
|
Closes #11176.
|
|
Closes #10127.
|
|
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.
|
|
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.
|
|
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.
|
|
Also give a better default if `alt` is not specified, using
the stringified caption rather than the filename.
Partially addresses #11140.
Add failing test case for Markdown writer issue in #11140.
|
|
Also apply hlint suggestions for fewer imports and
moving brackets to avoid $.
|
|
`<MetaString>` contents parsing was missing.
|
|
Take wide characters into account when determining the alignment.
|
|
The pagebreak is parsed as a HorizontalRule inside a wrapper Div with class `page-break`.
Closes #11101.
|
|
If we have a table with row/colspans that can rendered as an
approximate pipe table (without row/colspans), and no other table
format is enabled that could render the table, we fall back to
an "approximate" pipe table, with no row/colspans.
Closes #11128.
|
|
|
|
HTTP requests that don't return a 200 error code are now treated as an
error. This ensures that a warning is triggered when using
`--embed-resources` or `--extract-media`.
|
|
[API change] Text.Pandoc.Parsing: New functions `tableWithSpans`,
`tableWithSpans'`, `toTableComponentsWithSpans` and
`toTableComponentsWithSpans'` take a list of lists of
(Blocks, RowSpan, ColSpan) to parse a Table with different RowSpan and
ColSpan values accordingly.
New helper functions `singleRowSpans` and `singleColumnSpans` help set
all RowSpans or ColSpans to be 1 in case the table format only allows
setting one or the other.
|
|
Fixes: #11124
|
|
The function converts links to spans. It is used, for example, to avoid
nested links.
The HTML writer used to put the description of nested links into small
caps, but uses a simple *span* now.
|
|
Add an additional guard for a single column to be able to process it.
|
|
as well as `refs`. Reason: when `--file-scope` is used, a Div
with id `refs` gets a prefix attached, derived from the filename.
The prefix ends in `__`.
Closes #11072.
|
|
|
|
This revises the solution to #9214 in commit 2e8ecb3 in order to
handle a standard Word way of inserting emojis.
Closes #11113.
|
|
This was too heavy-handed a fix, and it interferes with processing
Word emojis (#11109).
|
|
|
|
Thus, for example, `{npj} Quantum Information` should translate as
`[npj]{.nocase} Quantum Information`.
Closes #11048.
|
|
...without query or fragment if the original fetch fails.
This provides a fix for #1477 in a way that doesn't raise the
problems mentioned in #11021.
|
|
A new command line option `--syntax-highlighting` is provided; it takes
the values `none`, `default`, `idiomatic`, a style name, or a path to a
theme file. It replaces the `--no-highlighting`, `--highlighting-style`,
and `--listings` options.
The `writerListings` and `writerHighlightStyle` fields of the
`WriterOptions` type are replaced with `writerHighlightStyle`.
Closes: #10525
|
|
The Text.Pandoc.Options module exports the `HighlightMethod` data type
and it's constructors. Furthermore, three pattern synonyms are exported,
`NoHighlightingString`, `DefaultHighlightingString`, and
`IdiomaticHighlightingString`, which hold the string value that's used
for decoding and encoding of HighlightMethod values.
|
|
This allows to be more explicit about using a default style, and
providing a single point of truth for its value. The variable is an
alias for `pygments`.
|
|
[API change] Text.Pandoc.Parsing: `tableWith` and `tableWith'` now
return a list of lists of Blocks, rather than a list of Blocks, for the
header rows, allowing for multiple header rows.
Closes #10338.
|