| Age | Commit message (Collapse) | Author |
|---|
|
This is a behavior change, not an API change, since there
was already a definition that defaulted to using Show.
The change here is that we use renderError for a more human-readable
version.
|
|
instead of a directory. This happens when the path given has a
.tar extension.
|
|
|
|
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 adds support for a `notes` field in the YAML metadata block
that will be used as speaker notes for the title slide in PowerPoint
output.
Previously, there was no way to add speaker notes to the title slide
since it is generated from metadata rather than from content blocks.
The `::: notes` syntax only works for content slides.
Example usage:
---
title: My Presentation
notes: |
Welcome everyone to this presentation.
Remember to introduce yourself.
---
Closes #5844 (for PPTX output).
Co-authored-by: Chris Callison-Burch <[email protected]>
|
|
This reverts to earlier < 3.7 behavior.
Closes #11384.
|
|
(From fontspec and ngerman babel.)
Closes #6120.
|
|
This just reproduces the output of `logMessage`, for convenience
for those who are using the JSON output outside of Haskell.
|
|
Here we use aside elements, which are popups, and the backlinks
are not needed; in some readers they cause a redundant number to
appear, since the reader adds a note number.
Standard practice seems to be not to use these.
|
|
Closes #11380.
|
|
Pandoc's docx writer was previously adding an `<Override>`
for `/word/media/` in `[Content_Types].xml` when the reference doc
contains media, which violates OPC rules and causes Word
to report corruption.
|
|
The `role` attribute is parsed and added to Pandoc AST elements,
using a wrapper Div if needed.
|
|
|
|
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.
|
|
Parse the number-rows-spanned and number-columns-spanned attributes to
create Cells for the Table.
|
|
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.
|
|
Unexported module.
|
|
|
|
This allows pandoc to be compiled without support for making
HTTP requests, which is useful when WASM is the target.
Closes #10980.
|
|
Now it takes a Text instead of an HttpException as the second
argument. [API change]
Motivation: if we expose HttpException in the public API, it
makes it difficult to provide a version of pandoc that can
be compiled to wasm, which currently can't handle the network
libraries.
See #10980.
|
|
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.
|
|
|
|
`foldl'` is exported by Prelude by base 4.20+. So we need to do
some qualified importing to avoid warnings about redundant imports.
|
|
|
|
|
|
|
|
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.
|
|
|
|
[API change]
Formerly defined in the DocBook writer but more generally useful.
|
|
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 commit 7fe8c928212197354196724e9b95b71a854fdca9.
See #10643 and #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.
|
|
Closes #11321.
|
|
Previously they were skippedas comments due to a bug.
Closes #11322.
|
|
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.
|
