| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
- Improved support for custom macro definitions.
- LinePart type has been added. RoffStr is now one
constructor of LinePart (the other being MacroArg).
- MComment has lost its argument.
- MEndMacro has been removed.
- MStr has been removed (we now simply use LinePart).
- Macros now store a list of tokens.
- Each macro argument is a [LinePart], instead of a LinePart.
- .BR now behaves as documented in man (and doesn't create a link).
|
|
Closes #4987.
|
|
- .SH should be level 1, .SS level 2.
- The header title can come on the next line.
|
|
Closes #4985.
|
|
Closes #4983.
|
|
use `trimInlines` for Para content to avoid leading and
trailing spaces.
Fix handling of \" in middle of line.
Add more tests for escapes.
|
|
|
|
|
|
|
|
|
|
|
|
Yanpas-groff_reader
|
|
|
|
Some of the round-trip tests are set to do a maximum of 25
trials when the default value is given.
Closes #4956.
|
|
|
|
|
|
(fixed by previous commit)
|
|
|
|
|
|
|
|
`enclosedByPair` alone does not the handle the empty array properly since it uses `many1Till`.
|
|
|
|
Check that indented blocks that end in self-terminating blocks (such as block tags and verse) can be terminated by paragraphs.
|
|
|
|
With this change, autolinks are parsed as Links with
the `uri` class. (The same is true for bare links, if
the `autolink_bare_uris` extension is enabled.) Email
autolinks are parsed as Links with the `email` class.
This allows the distinction to be represented in the
URI.
Formerly the `uri` class was added to autolinks by
the HTML writer, but it had to guess what was an autolink
and could not distinguish `[http://example.com](http://example.com)`
from `<http://example.com>`. It also incorrectly recognized
`[pandoc](pandoc)` as an autolink. Now the HTML writer
simply passes through the `uri` attribute if it is present,
but does not add anything.
The Textile writer has been modified so that the `uri`
class is not explicitly added for autolinks, even if it
is present.
Closes #4913.
|
|
this eliminates a regression error introduced after pandoc 2.1.1,
affecting rST inline parsing. see the issue for details
|
|
|
|
|
|
This way testcase can be shrinked better up to removing all blocks completely.
|
|
|
|
|
|
Inclusion of planning info (*DEADLINE*, *SCHEDULED*, and *CLOSED*) can
be controlled via the `p` export option: setting the option to `t` will
add all planning information in a *Plain* block below the respective
headline.
|
|
There is already a separate test for unclosed </quote>.
|
|
Planning info is parsed, but not included in the output (as is the
default with Emacs Org-mode).
Fixes: #4867
|
|
|
|
Parsing now stops at each section header to ensure the
header is registered before parsing of the next section starts.
|
|
Emacs Muse allows this.
|
|
instead of using parseFromString.
This change makes it possible to have verbatim </verse> tag
inside verse.
|
|
|
|
This change makes reader more compatible with Emacs Muse
|
|
* 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.
|
|
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.
|
|
|
|
|
|
|
|
|
|
|
|
|
