| Age | Commit message (Collapse) | Author |
|---|
|
Paragraph styles. This should ensure that existing documents
still work with the FirstParagraph style, without the need
to define new styles.
|
|
Closes #11268.
|
|
Closes #11270.
|
|
This reverts commit 22863a3e124215e6fd24efe55a5a99fb2d605e5b.
|
|
containing macro definitions with `\makeatletter` and `\makeatother`.
Closes #9953, see also #11270.
|
|
The preparser doesn't need to return a value.
|
|
Previously, a math environment with extra space before the
`\end` would get rendered with a blank line, which LaTeX
treats as a paragraph break.
Signed-off-by: Emmanuel Ferdman <[email protected]>
|
|
Fix `rawTeXParser`. Make macro expansion in raw LaTeX depend on
the setting of the `latex_macros` extension. Previously macros
were always expanded, even in raw TeX in markdown. In addition,
there was previously a bug that caused content to be garbled
in certain cases.
Closes #11253.
Handle `ifstrequal` at a lower level, like the other `if` commands.
See #11253.
|
|
This adds the following table features:
- row span and column span
- footer row
- individual horizontal cell alignment
[API change] T.P.Writers.Shared: Add functions `allRowsEmpty` and
`tableBodiesToRows` from the RST writer for reuse in other writers.
Also fix hlint warning about `unzip` from `NonEmpty`:
The exported polymorphic function will become
monomorphic in the future. Restrict the `NonEmpty`
import to use the Prelude `unzip` function.
|
|
Closes #10880.
|
|
Previously the special handling added for #9711 worked only
when the math element did not contain spaces before the
math environment.
Closes #11266.
|
|
See jgm/typst-hs#80.
Note that previously, the typst reader never returned document
metadata. Now it does, even if the typst document does not contain
a `#title` function that would result in actually printing the
title block.
|
|
Before 3.8, the default behavior when producing a PDF `-t typst`
was to produce smart quotes according to typst's defaults.
(This could be defeated by specifying `-t typst-smart`.)
This behavior broke in 3.8 because of a change to Text.Pandoc.PDF.
This change caused `smart` to be disabled for all formats when
producing PDFs, when before it was only disable for TeX-based
formats (to avoid bad ligatures).
This commit restores the old behavior. Possibly the regression also
other affects other non-TeX formats, e.g. HTML.
Closes #11256.
|
|
They are not environments! `ifstrequal`, `iftoggle`, etc.
ifstrequal, iftoggle, etc. -- these are not environments,
and they are handled under inlineCommands.
|
|
Previously we just got big Str elements with spaces included.
But many pandoc writers assume that breakable spaces will be
Space elements. So, we got odd results with e.g. jira output.
Closes #11250.
|
|
We do this indirectly, by rendering the formatting using the
HTML tags that citeproc recognizes. Fixes jgm/citeproc#68
and jgm/citeproc#163.
Note that formatting is only possible for locators given in
the explicit form, surrounded by curly braces. It won't work
for implicit locators, since these expect number-like expressions.
|
|
The reader tries to parse the rest of the opening line of a block, e.g.,
`#+begin_myblock …`, as a parameters list. It first assumes that the parameters
are in lisp-style (`:key value`), then alternatively tries to read python-style
key-value pairs (`key=value`) and falls back to reading the entire remaining
line as a single `parameter` attribute.
This method is also applied to dynamic blocks.
Closes: #11188
|
|
|
|
Patch credit: @mmourino.
Closes #8189. Closes #6959.
|
|
|
|
Closes #11211.
|
|
This fixes an issue that occurs if an open paren comes
right after e.g. `#strong[test]`.
Closes #11210.
|
|
|
|
This improves on commit e13aa5c0157744de262ac512cc95a76a4562e37b,
which worked only for recent versions of longtable.
For older versions, we need to define a dummy counter `none`.
Closes #11201. Thanks to @priiduonu for the solution.
|
|
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.
|
