Age | Commit message (Collapse) | Author | Files | Lines |
|
Closes #4803
After this commit use `$titleblock$` in order to get what was contained
in `$title$` before, that is a title and subtitle rendered according to
the official rST method:
http://docutils.sourceforge.net/docs/user/rst/quickstart.html#document-title-subtitle. from
With this commit, the `$title$` and `$subtitle$` metadata are available and they
simply carry the metadata values. This opens up more possibilities in templates.
|
|
Now we properly parse title and subtitle elements that are
direct children of book and article (as well as children of
bookinfo, articleinfo, or info).
We also now use the "subtitle" metadata field for subtitles,
rather than tacking the subtitle on to the title.
|
|
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.
|
|
|
|
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.
|
|
closes #4545
|
|
|
|
This fixes conversions from org with example blocks.
Closes #4748.
|
|
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)
|
|
Fixes #4728
|
|
E.g. `` ` ` ``.
|
|
closes #4700
|
|
Address #2424
|
|
Address issue #2424
|
|
This is fraught on Windows.
|
|
This should fix commercialhaskell/stackage#3719, once
a new release is made.
|
|
fixes #4690
|
|
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.
|
|
|
|
|
|
...`\begin` or `\end`.
Fixes #4667.
|
|
...even if `implicit_attributes` is not set, by rendering in
raw HTML.
Fixes #4677.
|
|
|
|
|
|
Closes #4653. Note that this only affected LaTeX in markdown.
Added regression test.
|
|
This adds proper bookmarks to the headers with non-null IDs.
Closes #4358.
|
|
These were added by
https://github.com/schrieveslaach/pandoc/commit/96d10c72cc95e56c9e49db3e6db7118e89d1f1e0
Closes #4648.
|
|
|
|
Closes #4639.
|
|
Closes #4637.
|
|
|
|
|
|
We need to find something that will work on windows.
|
|
It should be installed on all *nix systems.
|
|
|
|
Previously it was assumed that the system would have `/bin/false`
and `/bin/sed`, and these tests were skipped otherwise.
On MacOS, these utilities are located in `/usr/bin`.
Fixed by just using `sed` and `false` -- these should always be
in the path. Removed the "skipping" behavior, replaced with a
check for Windows. On Windowns, we use `echo` and `cd`, which
should always exist.
Not yet checked on Windows.
|
|
Updated golden test and confirmed validity of file.
Closes #4633.
|
|
Closes #4576.
|
|
Address issue #4542
|
|
|
|
|
|
|
|
|
|
labdsf-fb2-hrblankline
|