Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
|
|
This fixes a regression in 2.2.3, which cause boolean values to
be parsed as MetaInlines instead of MetaBool.
Note also an undocumented (but desirable) change in 2.2.3:
numbers are now parsed as MetaInlines rather than MetaString.
Closes #4819.
|
|
This fixes a regression in 2.2.3 which caused embedded mappings
(e.g. mappings in sequences) not to work in YAML metadata.
Closes #4817.
|
|
* 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.
|
|
Previously in 2.2.2 you could not do
---
0: bar
...
but only
---
'0': bar
...
With this change, both forms work.
|
|
(Minor)
|
|
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.
|
|
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
|
|
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.
|
|
|
|
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.
|
|
|
|
|
|
|
|
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)
|
|
Closes #4725.
|
|
|
|
E.g. `` ` ` ``.
|
|
closes #4700
|
|
Closes #4698.
|
|
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.
|
|
|
|
|
|
|
|
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.
|
|
|
|
|
|
instead of trying to strip "URL:" prefix after parsing.
|
|
|
|
Improves on earlier fix for #4296.
|
|
Closes #4653. Note that this only affected LaTeX in markdown.
Added regression test.
|
|
Use a function from the *filepath* library to check whether a string is
a valid file name. The custom validity checker that was used before gave
wrong results, e.g. for absolute file paths on
Windows (kawabata/ox-pandoc#52).
|
|
This fixes the main problem in #4576.
There is still an issue about `\SI`, but that's a separate issue.
|
|
|
|
Author has given permission in an email, 3 May 2018.
See #4591.
|
|
Now FB2 reader can read writer.fb2, which does not validate (yet).
|
|
|
|
Closes #4598.
|
|
|
|
|