| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
* Use a Span with class "title-reference" for the default
title-reference role.
* Use B.text to split up contents into Spaces, SoftBreaks, and Strs
for title-reference.
* Use Code with class "interpreted-text" instead of Span and Str for
unknown roles. (The RST writer has also been modified to round-trip
this properly.)
* Disallow blank lines in interpreted text.
* Backslash-escape now works in interpreted text.
* Backticks followed by alphanumerics no longer end interpreted text.
Closes #4811.
|
|
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.
|
|
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.
|
|
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
|
|
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.
|
|
|
|
|
|
|
|
|
|
|
|
These were added by
https://github.com/schrieveslaach/pandoc/commit/96d10c72cc95e56c9e49db3e6db7118e89d1f1e0
Closes #4648.
|
|
Address issue #4542
|
|
|
|
|
|
|
|
labdsf-fb2-hrblankline
|
|
nested inlines are not valid RST syntax, so we flatten them following
some readability criteria discussed in #4368.
|
|
|
|
Removed `--latexmathml`, `--gladtex`, `--mimetex`, `--jsmath`, `-m`,
`--asciimathml` options.
Removed `JsMath`, `LaTeXMathML`, and `GladTeX` constructors from
`Text.Pandoc.Options.HTMLMathMethod` [API change].
Removed unneeded data file LaTeXMathML.js and updated tests.
Bumped version to 2.2.
|
|
Previously we used an odd mix of 3- and 4-space indentation.
Now we use 3-space indentation, except for ordered lists,
where indentation must depend on the width of the list marker.
Closes #4563.
|
|
|
|
|
|
|
|
|
|
Muse writer indents verse blocks in definition list more than necessary, so Muse reader should parse them.
|
|
|
|
|
|
|
|
|
|
Muse writer can write links with empty URLs, so Muse reader should read them.
|
|
Fixes #4551
|
|
Closes #4550.
|
|
> should be escaped only when it can start verse, i.e., at the beginning of the line.
|
|
|
|
|
|
|
|
|
|
In https://github.com/jgm/pandoc-types/pull/36 we changed
the table builder to pad cells. This commit changes tests
(and two readers) to accord with this behavior.
|
|
HorizontalRule corresponds to <hr> element in the default output
format, HTML. Current HTML standard defines <hr> element as
"paragraph-level thematic break". In typography it is often
represented by extra space or centered asterism ("⁂"), but since
FB2 does not support text centering, empty line (similar to extra space)
is the only solution.
Line breaks, on the other hand, don't generate <empty-line />
anymore. Previously line breaks generated <empty-line /> element
inside paragraph, which is not allowed. So, this commit addresses
issue #2424 ("FB2 produced by pandoc doesn't validate").
FB2 does not have a way to represent line breaks inside paragraphs.
They are replaced with LF character, which is not rendered by
FB2 readers, but at least preserves some information.
|
|
|
|
|
|
See https://github.com/melmothx/text-amuse/issues/39
|
|
It includes cases when they can be mistaken for footnotes
and links, as well as inside link description.
|
|
|
|
|
|
Close #4468
|
|
|
|
Also reduced amount of <verbatim> tags in output to avoid escaping every "-" and word that ends in a full stop.
|
|
|
