Age | Commit message (Collapse) | Author | Files | Lines |
|
Exposes a function converting which flattenes a list of blocks into a
list of inlines. An example use case would be the conversion of Note
elements into other inlines.
|
|
RST does not allow nested emphasis, links, or other inline
constructs.
Closes #4581, double parsing of links with URLs as
link text. This supersedes the earlier fix for #4581
in 6419819b46c0d69c7024ba8aa4a6381cb311341c.
Fixes #4561, a bug parsing with URLs inside emphasis.
Closes #4792.
|
|
Note that the old output is semantically identical, but the
new output looks better.
Closes #4794.
|
|
Emphasis was not parsed when it followed directly after some block types
(e.g., lists).
The org reader uses a wrapper for the `parseFromString` function to
handle org-specific state. The last position of a character allowed
before emphasis was reset incorrectly in this wrapper. Emphasized text
was not recognized when placed directly behind a block which the reader
parses using `parseFromString`.
Fixes: #4784
|
|
Link labels containing raw URLs were parsed as autolinks,
but links within links are not allowed.
Closes #4581.
|
|
Starting in 2.2.2, everything after an `\input` (or `\include`)
in a markdown file would be parsed as raw LaTeX.
This commit fixes the issue and adds a regression test.
Closes #4781.
|
|
|
|
Under version 2.2.1 and prior pandoc found latex templates in the
templates directory under the data directory, but this no longer
works in 2.2.2.
MANUAL says: "If the template is not found, pandoc will search for it in
the templates subdirectory of the user data directory (see `--data-dir`)."
This commit fixes the regression, which stems from 07bce91.
Closes #4777.
|
|
|
|
Text.Pandoc.Emoji now exports `emojiToInline`, which returns a Span inline containing the emoji character and some attributes with metadata (class `emoji`, attribute `data-emoji` with emoji name). Previously, emojis (as supported in Markdown and CommonMark readers, e.g ":smile:")
were simply translated into the corresponding unicode code point. By wrapping them in Span
nodes, we make it possible to do special handling such as giving them a special font
in HTML output. We also open up the possibility of treating them differently when the
`--ascii` option is selected (though that is not part of this commit).
Closes #4743.
|
|
|
|
We now allow arbitrary LaTeX values.
This helps with #4761. The `\maxwidth` is still not
propagated to the latex destination, but at least we don't
choke on parsing.
|
|
closes #4545
|
|
Closes #4755.
This will mean some increase in the time it takes to
produce an image-heavy PDF with xelatex, but it will
make tables of contents correct, which is more important.
Note that the production time should also be decreased
by the previous commit, which fixed a logic error
affecting the number of runs. That change might mitigate
the effect of this one.
|
|
We were running the tex program one more time than requested.
This should speed up pdf production.
|
|
|
|
|
|
This fixes conversions from org with example blocks.
Closes #4748.
|
|
|
|
yaml wraps a C library; HsYAML is pure Haskell.
Closes #4747. Advances #4535.
|
|
|
|
Non-ascii characters were not stripped from identifiers even if the
`ascii_identifiers` extension was enabled (which is is by default for
gfm).
Closes #4742
|
|
|
|
- remove trailing Space from list items
- parse lists that have no space after marker (fixes #4722)
|
|
This removes a compiler warning.
There is no need for the old network-uri flag, since
network 2.6 was released in 2014.
|
|
Closes #4725.
|
|
|
|
Fixes #4728
|
|
E.g. `` ` ` ``.
|
|
closes #4700
|
|
As noted [here](https://tex.stackexchange.com/a/49805) ([beamer
commit here](https://github.com/josephwright/beamer/commit/ff70090f36b631667b472cfe675fc3514fe46f7e)),
`noframenumbering` is an undocumented, but long existing option
to disable frame numbering for a particular slide. This is useful
to avoid numbering backup slides.
|
|
|
|
...provided by the argument to `--mathjax` or the normal
pandoc default, rather than a hard-coded one in the template.
Closes #4701.
|
|
Closes #4698.
|
|
Address #2424
|
|
Address issue #2424
|
|
Refactored code from figure captions to use in both places.
Closes #4683.
|
|
fixes #4690
|
|
|
|
Fixes #4681.
|
|
via the "section-numbering" directive in standalone output.
|
|
In addition, `\input` can now be used in an inline context,
e.g. to provide part of a paragraph, as it can in LaTeX.
Closes #4553.
|
|
|
|
|
|
|
|
Note that it will not take effect when readers/writers are called as libraries (#4674).
|
|
This reverts commit 50c71b5bc5db797ac46550ed54e91196269716e3.
This was a bad idea, since tests depend on recent haddock-library.
We'd be able to build but fail tests.
|
|
haddock-library-1.6 requires Cabal >= 2.0. This change allows
systems with older Cabal versions to build pandoc.
|
|
...`\begin` or `\end`.
Fixes #4667.
|
|
Ideally we'd turn these on only when reading beamer, but currently
beamer is not distinguished from latex as an input format.
This commit also activates parsing of overlay specifications
after commands in general (e.g. `\item`), since they can occur
in many contexts in beamer.
Closes #4669.
|