Age | Commit message (Collapse) | Author | Files | Lines |
|
Closes #6288.
|
|
Closes #6265.
|
|
See https://developer.mozilla.org/en-US/docs/Web/HTML/Element/bdo
Closes #5794
|
|
- SmallCaps instead of Span for the part after the initial capital.
- Ensure that both arguments are parsed, so that in Markdown both
are treated as raw LateX. (Closes #6258.)
|
|
This reverts commit 3493d6afaa6586c46898cf8bdb0c45bb70d31f28.
This might be worth considering in the future, but let's not do
it yet...the additional complexity needs a better justification.
|
|
This is experimental. Normally metadata values are interpreted
as markdown, but if the !!literal tag is used they will be interpreted
as plain strings.
We need to consider whether this can still be implemented if
we switch back from HsYAML to yaml for performance reasons.
|
|
Closes #5849. Previously biblatex citations were only grouped if
there was no prefix. This patch allows them to be grouped in
subgroups split by prefixes and suffixes, which allows better citation
sorting.
|
|
- Don't emit empty Span elements for labels.
- Put tables with labels in a surrounding Div.
|
|
Closes #6137.
|
|
Closes #6133 (regression).
|
|
Closes #5819.
|
|
This confuses mediawiki's parser. So we insert a `<nowiki/>`
no-op between a literal `[` and a link. Closes #6119.
|
|
Closes #6114.
|
|
Close #6107.
|
|
|
|
This adds csv as an input format.
The CSV table is converted into a pandoc simple table.
Closes #6100.
|
|
Another regression from 2.7.x. Closes #6062.
|
|
This affecs parsing of raw tex in LaTeX and in Markdown and
other formats.
Closes #6043.
|
|
If parsing fails in a raw environment (e.g. due to special
characters like unescaped `_`), try again as a verbatim
environment, which is less sensitive to special characters.
This allows us to capture special environments that change
catcodes as raw tex when `-f latex+raw_tex` is used.
Closes #6034.
|
|
Columns in title slides were causing problems with
slide division. Closes #6033.
|
|
The fix to #6030 actually changed behavior, so that the
2D nesting occurred at slide level N-1 and N, instead of
at the top-level section. This commit restores the 2.7.3 behavior.
If there are more than 2 levels, the top level is horizontal
and the rest are collapsed to vertical.
Closes #6032.
|
|
Closes #6030.
|
|
Partially addresses #6030.
|
|
Closes #6009, #5360.
|
|
Closes: #5984
|
|
|
|
|
|
Closes #5986.
|
|
|
|
|
|
The table `#+NAME:` or `#+LABEL:` is added to the table's caption in the
form of an empty span with the label set as the span's ID.
Closes: #5984
|
|
Closes #5967.
|
|
With positive heading shifts, starting in 2.8 this option caused
metadata titles to be removed and changed to regular headings.
This behavior is incompatible with the old behavior of
`--base-header-level` and breaks old workflows, so with this
commit we are rolling back this change.
Now, there is an asymmetry in positive and negative heading
level shifts:
+ With positive shifts, the metadata title stays the same and
does not get changed to a heading in the body.
+ With negative shifts, a heading can be converted into the
metadata title.
I think this is a desirable combination of features, despite
the asymmetry. One might, e.g., want to have a document
with level-1 section headigs, but render it to HTML with
level-2 headings, retaining the metadata title (which pandoc
will render as a level-1 heading with the default template).
Closes #5957.
Revises #5615.
|
|
This will allow styling unordered task lists in a way that omits
the bullet.
|
|
|
|
With simple tables, we have a clash with heading syntax.
Closes #5936.
|
|
Closes #5918.
|
|
If a simple table would be too wide, we use a grid table.
The code for generating grid tables has been adjusted to
give more intelligent column widths when widths aren't
given. (This also affects the markdown writer.)
Closes #5899.
|
|
`Nothing` means: nothing specified.
`Just []` means: an empty list specified (e.g. in defaults).
Potentially these could lead to different behavior: see #5888.
|
|
Closes #5904.
|
|
|
|
See #5904.
|
|
|
|
Closes #5898.
|
|
Superscripts and subscripts cannot contain spaces,
but newlines were previously allowed (unintentionally).
This led to bad interactions in some cases with footnotes.
E.g.
```
foo^[note]
bar^[note]
```
With this change newlines are also not allowed inside
super/subscripts.
Closes #5878.
|
|
(#5882)
* Add HTML Reader support for `<dfn>`, parsing this as a Span with class `dfn`.
* Change `htmlSpanLikeElements` implementation to retain classes,
attributes and inline content.
|
|
Closes #5885.
|
|
Previously, if a document contained two YAML metadata blocks
that set the same field, the conflict would be resolved in favor
of the first. Now it is resolved in favor of the second (due to
a change in pandoc-types).
This makes the behavior more uniform with other things in pandoc
(such as reference links and `--metadata-file`).
|
|
Closes #5681.
|
|
...to ensure that space is left between a control seq and
a following word that would otherwise change its meaning.
Closes #5836.
|