| Age | Commit message (Collapse) | Author |
|---|
|
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.
These spaces may casue problems for some output formats, e.g.
asciidoc, but these issues should be addressed in the
corresponding writers, as they are in the Markdown writer,
using Text.Pandoc.Writers.Shared.delimited.
Closes #11398.
|
|
This reverts to earlier < 3.7 behavior.
Closes #11384.
|
|
Closes #11374.
|
|
Both the field instruction and its result may be ungrouped.
Closes #10942.
|
|
`<mark>`, `<var>`, `<samp>`, and `<kbd>` 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.
Closes #11299.
|
|
Partially addresses #11299.
|
|
...incorporated into a following table.
Closes #11364.
|
|
|
|
Also escape the `#` character.
Closes #11362.
An alternative solution, raised in #11362, would be to
rely less on escaping and simply always use doubled delimiters.
However, there would still be a need for escaping, since one
might use a literal `##` (for example)>
|
|
New paragraphs may start with \pard alone without an explicit paragraph
break with \par preceding it.
|
|
MediaWiki format supports [magic
words](https://www.mediawiki.org/wiki/Help:Magic_words). These are
basically built-in templates. This commit introduces support for behavior
switches, which is one of the three types of magic words. They add
a field to metadata without producing any text.
Signed-off-by: botantony <[email protected]>
|
|
Do not allow blank lines before closing `$` delimiter.
This brings the parser in line with the documentation.
Closes #11311.
|
|
Now keep track of the current element stack to only add metadata if
inside an appropriate parent element.
Closes #11300.
|
|
Subfigures are now wrapped inside a `<fig-group>` element. Furthermore,
figure content that isn't allowed as children of `<fig>` elements, such
as raw text, gets wrapped in `<p>` elements to ensure schema-conform
XML production.
Fixes: #11342
|
|
...for commonmark. Closes #11341.
|
|
These are just unmarked code blocks.
Closes #11339.
|
|
Closes #11334.
|
|
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.
Requires a dependency on a development version of citeproc.
|
|
This is a cleaner fix to #10643 than the reverted commit 7fe8c92.
Styles are not stripped, but with this change they will not
interfere with inline parsing.
Closes #11246.
|
|
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.
Closes #11323.
|
|
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.
Closes #11312.
|
|
This PR aims to handle a common run field instruction (fieldInstr)
from docx format : REF, specifically those with the "link" switch \h.
In word software, you can create REF field instruction with the
Cross-reference button. You can create cross-reference to
many things such as Equation, Table, Title...
|
|
The ANSI writer is now able to keep track of row spans and apply them in rows.
[API change] T.P.Writers.Shared:
Add functions `insertCurrentSpansAtColumn`, `takePreviousSpansAtColumn`
and `decrementTrailingRowSpans` for applying and keeping track of
RowSpans over multiple rows.
Fixes: #10149
|
|
Closes #11309.
|
|
Closes #11270.
|
|
|
|
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.
|
|
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.
|
|
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.
|
|
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 #10127.
|
|
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.
|
|
Closes #11150.
|
|
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.
|
|
Third issue in #11140.
|
