...so that, when the input format is not markdown or a markdown
variant, pandoc's markdown is used. When the input format is
a markdown variant, the same format is used. Reason for the change:
it doesn't make sense to run the markdown parser with a set of
extensions designed for a non-markdown format, and this dramatically
limits what people can do in metadata files.
Refines #6832. Closes#7926.
Perhaps this can be reconsidered if we come up with a way
of specifying an arbitrary format for the metadata file (#5914).
- Allow any type of callable object as argument to List
functions `filter`, `map`, and `find_if`. These previously
required the argument to be of type `function`, which was too
restrictive.
- Inline: the type of Image captions is now `Inlines` instead
of `List`.
Footnotes in `<fn-group>` elements are collected and re-inserted into
the document as proper footnotes in the place where they are referenced.
Fixes: #6348
Closes#5202.
Within each cell, determine the cell alignment as per
https://www.dokuwiki.org/wiki:syntax#tables. The current approach, as
per the issue treats the first row's alignment as determining
that of the entire column. Given this, it wastes some work in
determining an alignment for every cell.
This change ensures that example list items all belong to a single
number sequence, so that if items are added or deleted in a word
processor, the other items will renumber automatically.
when parsing `<a epub:type="noteref">` and the identifier
doesn't correspond to anything in the note table.
Previously we just silently skipped these cases.
See #7884.
The Org Manual page at https://orgmode.org/manual/Property-Syntax.html
says (as of 2022-02-03):
"Property blocks defined before first headline needs to be located at
the top of the buffer, allowing only comments above."
This commit allows comments above.
Any non-space character is allowed as property drawer key, including ":"
itself (so it is not really a delimiter). The real delimiter is a space
character, so in a drawer like
:PROPERTIES:
::k:ey:: value
:END:
":k:ey:" is a key with value "value".
This usage can be seen in the Org Manual at
https://orgmode.org/manual/Using-Header-Arguments.html,
where the Org snippet
* Heading
:PROPERTIES:
:header-args:clojure: :session *clojure-1*
:header-args:R: :session *R*
:END:
is listed as an example.
Links without text contents are converted to `<xref>` elements. DocBook
processors will generate appropriate cross-reference text when presented
with an xref element.
New input format: endnotexml
New reader module: Text.Pandoc.Readers.EndNote, exporting
`readEndNoteXML` and `readEndNoteXMLReferences`. [API change]
This reader is still a bit rudimentary, but it should get
be good enough to be helpful.
These are supported in the same way as Zotero citations,
using the same code. As with Zotero, enable the `citations`
extension on `docx` to parse these as native citations.
Closes#7840.
Previously we used System.FilePath's isRelative to
determine when paths are relative (since absolute
paths need to get a new name based on the sha1 hash).
But this has an OS-specific behavior and actually
returns True on Windows for paths like `/media/file.png`.
This ought to fix#7881.
