| Age | Commit message (Collapse) | Author |
|---|
|
This causes compilation errors, and I don't know how
to work around them. Closes #5574.
|
|
We try to parse the date and convert to year, month, day,
as expected in pub-date. We also add an iso-8601-date attribute
if possible.
|
|
It's only allowed in a few special contexts, and not in
p elements.
|
|
The JATS spec restricts contents of certain
elements (fn, list-item); this patch wraps
elements that can't go in these contexts inside
p elements with specific-use "wrapper", so the
documents will conform.
Closes #5570.
|
|
Closes #5529.
|
|
Closes #5566.
|
|
Closes #5565.
|
|
|
|
Sometimes custom elements are used, and the reader should
not abort but skip them with a warning. (For example,
id element in author.)
Closes #5560.
|
|
SkippedContent doesn't work for some of the XML-based
readers, which don't have access to source positions.
|
|
This was added in pandoc 2.7.2, but it makes it impossible
to use pandoc-crossref. So this has been rolled back for now,
until we find a good solution to make this behavior optional
(or a creative way to let pandoc-crossref and this feature
to coexist).
See #5474.
|
|
Previously if the language was not in the list of listings-
supported languages, it would not be added as a class, so
custom syntax highlighting could not be used.
Closes #5540.
|
|
Previously the TOC appeared at the end of the document,
and was not bookmarked.
If you want it to continue appearing at the end, add
`--pdf-engine-opt=--no-toc-relocation` to your command
line.
Closes #5553.
|
|
Closes #5420.
|
|
This adds support for Atlassian's jira markup.
Closes #2497
|
|
Change is in rawLaTeXInline in LaTeX reader, but
it affects the markdown reader and other readers
that allow raw LaTeX.
Previously, trailing `{}` would be included for
unknown commands, but not for known commands.
However, they are sometimes used to avoid a trailing
space after the command. The chances that a `{}`
after a LaTeX command is not part of the command
are very small.
Closes #5439.
|
|
Closes #5545.
|
|
For example, introduction should go in bodymatter, not frontmatter, and
epigraph, conclusion, and afterward should go in bodymatter, not
backmatter.
For the full list of assignments, see the manual.
Closes #5546.
|
|
Closes #5549.
|
|
e.g. ordered list item, in Markdown writer.
Closes #554.
|
|
Opening and closing tag for math output match now.
|
|
If the character isn't in the console font, the
message is pretty useless, so we show the code
point for anything non-ASCII.
Closes #5538.
|
|
Function `pandoc.mediabag.delete` allows to remove a single item of the given
name from the media bag.
|
|
Function `pandoc.mediabag.empty` was added. It allows to clean-out the media
bag, removing all entries.
|
|
A new function `pandoc.mediabag.items` was added to Lua module
pandoc.mediabag. This allows users to lazily iterate over all media bag
items, loading items into Lua one-by-one. Example:
for filename, mime_type, content in pandoc.mediabag.items() do
-- use media bag item.
end
This is a convenient alternative to using `mediabag.list` in combination
with `mediabag.lookup`.
|
|
|
|
Lua: add Version type to simplify comparisons
|
|
Output HTML5 video and audio elements
|
|
- With epub extensions, check for epub:type in addition to type.
- Fix problem with noteref parsing which caused block-level
content to be eaten with the noteref.
- Rename pAnyTag to pAny.
- Refactor note resolution.
|
|
Version specifiers like `PANDOC_VERSION` and `PANDOC_API_VERSION` are
turned into `Version` objects. The objects simplify version-appropriate
comparisons while maintaining backward-compatibility.
A function `pandoc.types.Version` is added as part of the newly
introduced module `pandoc.types`, allowing users to create version
objects in scripts.
|
|
depending on file extension of the image path
|
|
|
|
The same text is already in the <figcaption> and
screen-readers would read it twice, see #4737
|
|
Move up the pattern match to be reachable, closes #5517.
Previously `file:/` URLs were handled wrongly and pandoc attempted
to make HTTP requests, which failed.
|
|
Previously we could get an empty ol element, which caused
validation errors with epubcheck.
|
|
add `onlySimpleTableCells` to `Text.Pandoc.Shared`
[API change]
This fixes an inconsistency in the HTML reader, which did not treat tables with `<p>` inside cells as simple.
|
|
|
|
|
|
|
|
Previously too few backticks were used when the code block
contained an indented line of backticks. (Ditto tildes.)
Cloess #5519.
|
|
A `do` notation was left in a non-monadic function.
|
|
Previously if labels had integer names, it could produce a conflict
with auto-labeled reference links. Now we test for a conflict and find
the next available integer.
Note that this involves adding a new state variable `stPrevRefs` to
keep track of refs used in other document parts when using
`--reference-location=block|section`
Closes #5495
|
|
This form is now supported in multimarkdown,
in addition to `tex_math_double_backslash`.
See #5512.
|
|
"Best Practice: When footnotes are grouped at the end of an article,
wrap them in a `<fn-group>` and use an `<xref>` element in the text, as
usual, to tie each footnote in the list to a particular location in the
text."
Closes #5511.
|
|
Existing FB2 readers, such as FBReader, already display links with type="note" as a superscript.
|
|
|
|
Planning info is now always placed before the subtree contents.
Previously, the planning info was placed after the content if the
header's subtree was converted to a list, which happens with headers of
level 3 and higher per default.
Fixes: #5494
|
|
Unknown export options are properly ignored and omitted from the output.
|
|
Emacs always uses two spaces when indenting the content of src blocks,
e.g., when exiting a `C-c '` edit-buffer. Pandoc used to indent contents
by the space-equivalent of one tab, but now always uses two spaces, too.
Closes: #5440
|
|
Closes #5493
|
