Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
Otherwise they can be interpreted as footnote definitions.
Closes #4171.
|
|
This fixes a regression in 2.0.
Note that extensions can now be individually disabled, e.g.
`-f opml-smart-raw_html`.
Closes #4164.
|
|
This mainly affects the Markdown reader when parsing
raw LaTeX with escaped spaces. Closes #4159.
|
|
Previously we erroneously included the enclosing
backticks in a reference ID (closes #4156).
This change also disables interpretation of
syntax inside references, as in docutils.
So, there is no emphasis in
`my *link*`_
|
|
|
|
This should be a nonbreaking space, as long as it's not
followed by a blank line. This has been fixed at the tokenizer
level.
Closes #4134.
|
|
Closes #4125.
|
|
|
|
Closes #4119.
|
|
* Deprecate `--strip-empty-paragraphs` option. Instead we now
use an `empty_paragraphs` extension that can be enabled on
the reader or writer. By default, disabled.
* Add `Ext_empty_paragraphs` constructor to `Extension`.
* Revert "Docx reader: don't strip out empty paragraphs."
This reverts commit d6c58eb836f033a48955796de4d9ffb3b30e297b.
* Implement `empty_paragraphs` extension in docx reader and writer,
opendocument writer, html reader and writer.
* Add tests for `empty_paragraphs` extension.
|
|
Closes #4113.
|
|
Previously both needed to be specified (unless the image was
being resized to be smaller than its original size).
If height but not width is specified, we now set width to
textwidth (and similarly if width but not height is specified).
Since we have keepaspectratio, this yields the desired result.
|
|
This reverts commit 171187a4527497701b3c77bd56cea2d770d4e3b0.
|
|
...if only one of height/width is given.
|
|
|
|
This fixes a bug where pandoc would stop parsing a URI with an
empty attribute: for example, `&a=&b=` wolud stop at `a`.
(The uri parser tries to guess which punctuation characters
are part of the URI and which might be punctuation after it.)
Closes #4068.
|
|
Closes #4062.
|
|
Closes #4061.
|
|
This is equivalent to `rr`. We now expand it like a macro.
Closes #4056.
|
|
See #4056.
|
|
Previously if a YAML block under `|-` contained
a blank line, pandoc would not parse it as metadata.
|
|
This brings our handling of them into alignment with
CommonMark's.
Closes #??.
|
|
It should replace a metadata value set in the document
itself, rather than creating a list including a new value.
Closes #4054.
|
|
Previously we got a crash, because we were trying to print
a native cmark STRIKETHROUGH node, and the commonmark writer
in cmark-github doesn't support this. Work around this by
using a raw node to add the strikethrough delimiters.
Closes #4038.
|
|
* Move as much as possible to the CSS in the template.
* Ensure that all the HTML-based templates (including epub)
contain the CSS for columns.
* Columns default to 50% width unless they are given a width
attribute.
Closes #4028.
|
|
* Remove "width" attribute which is not allowed on div.
* Remove space between `<div class="column">` elements,
since this prevents columns whose widths sum to 100%
(the space takes up space).
Closes #4028.
|
|
The previous fix only worked in certain cases.
Other cases with `>` in an HTML attribute broke.
|
|
We didn't fix it completely before.
|
|
and other non-HTML formats (`Text.Pandoc.Readers.HTML.htmlTag`).
The parser stopped at the first `>` character, even if it wasn't
the end of the comment.
Closes #4019.
|
|
Minor API change.
Now sizes given in 'mm' are no longer converted to 'cm'.
Closes #4012.
|
|
For example
\emph%
{hi}
|
|
Previously the following failed:
::: {.class}
1. one
2. two
:::
and you needed a blank line before the closing `:::`.
|
|
If `fenced_divs` is enabled, fenced divs will be used.
|
|
|
|
Added test case.
|
|
|
|
+ Added Ext_fenced_divs to Extensions (default for pandoc Markdown).
+ Document fenced_divs extension in manual.
+ Implemented fenced code divs in Markdown reader.
+ Added test.
Closes #168.
|
|
We previously failed on cases where an attribute contained a `>`
character. This patch fixes the bug.
Closes #3989.
|
|
!! warning
-- info
|
|
|
|
|
|
Closes #3983.
|
|
|
|
Previously `\include` wouldn't work if the included file
contained, e.g., a begin without a matching end.
We've changed the Tok type so that it stores a full SourcePos,
rather than just a line and column. So tokens keeep track
of the file they came from. This allows us to use a simpler
method for includes, which doesn't require parsing the included
document as a whole.
Closes #3971.
|
|
(Use a :literal: role.)
Closes #3974.
|
|
Closes #3978.
|
|
Closes #3968.
|
|
|
|
Closes #3947.
|