Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
rootzlevel-master
Conflicts:
src/Text/Pandoc/Readers/Org.hs
|
|
mpickering-errortype
Conflicts:
benchmark/benchmark-pandoc.hs
src/Text/Pandoc/Readers/Markdown.hs
src/Text/Pandoc/Readers/Org.hs
src/Text/Pandoc/Readers/RST.hs
tests/Tests/Readers/LaTeX.hs
|
|
`many1Till` will gobble up newline, and then whole following line will
match, so I had to use guard here.
|
|
Require space after key-value delimiter colon in mmd title block.
Issue #2026
Amend: parsec's `spaces` include newlines, but we don't want that. Had
to make custom `spaceNoNewline` parser here
|
|
Disable all metadata block extensions when parsing metadata field
values. Issue #2026
|
|
I've messed up badly with it, so it didn't work properly most of the
time. At the plus side, fallback mechanic is working wonderfully.
|
|
Closes #2017.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
- Added commonmark as an input format.
- Added `Text.Pandoc.Readers.CommonMark.readCommonMark`.
- For now, we use the markdown writer to generate benchmark
text for the CommonMark reader. We can change this when we
get a writer.
|
|
Fixes for multiple docx writer style bugs.
|
|
Support shortcut reference links in markdown writer
|
|
Closes #2007.
|
|
Closes #2001.
|
|
Issue #1977
Most markdown processors support the [shortcut format] for reference links.
Pandoc's markdown reader parsed this shortcuts unoptionally.
Pandoc's markdown writer (with --reference-links option) never shortcutted links.
This commit adds an extension `shortcut_reference_links`. The extension is
enabled by default for those markdown flavors that support reading shortcut
reference links, namely:
- pandoc
- strict pandoc
- github flavoured
- PHPmarkdown
If extension is enabled, reader parses the shortcuts in the same way as
it preveously did. Otherwise it would parse them as normal text.
If extension is enabled, writer outputs shortcut reference links unless
doing so would cause problems (see test cases in `tests/Tests/Writers/Markdown.hs`).
|
|
|
|
The `tabular` environment allows non-empty column separators
with the "@{...}" syntax. Previously, pandoc would fail to
parse tables if a non-empty colsep was present. With this
commit, these separators are still ignored, but the table gets
parsed. A test case is included.
|
|
The `tabular` environment takes an optional parameter for
vertical alignment. Previously, pandoc would fail to parse
tables if this parameter was present. With this commit,
the parameter is still ignored, but the table gets
parsed. A test case is included.
|
|
Rather than raising a parse error. Closes #1997.
|
|
This mimics MediaWiki itself. Closes #1982.
|
|
GFM and PHP Markdown Extra pipe tables require headers.
Previously pandoc allowed pipe tables not to include headers,
and produced headerless pipe tables in Markdown output, but this
was based on a misconception about pipe table syntax. This
commit fixes this.
Note: If you have been using headerless pipe tables, this may
cause existing tables to break.
Closes #1996.
|
|
|
|
|
|
Closes #1973.
|
|
Org-Mode's own html exporter converts the following org link:
[[http://example.com][https://www.haskell.org/static/img/logo.png]]
to
<a href="http://example.com">
<img src="https://www.haskell.org/static/img/logo.png" alt="logo.png" />
</a>
but pandoc generates:
<a href="http://example.com">
<a href="https://www.haskell.org/static/img/logo.png" class="uri">
https://www.haskell.org/static/img/logo.png
</a>
</a>
which is useless. With this patch, it generates:
<a href="http://example.com">
<img src="https://www.haskell.org/static/img/logo.png" alt="" />
</a>
|
|
The previous commits had some code repetition. This just makes it a bit
easier to read.
|
|
Verbatim usually shuts off all other run styles, but we don't want it to
shut off sub/superscript.
|
|
This allows inherited styles with numbering (lists). It works like this:
1. check to see if the style has numbering info.
2. if the paragraph has explicit numbering info in the doc that takes
precedence.
3. if not we use the numbering info in the style, if it's there.
4. otherwise normal paragraph.
We no longer assume it's not a numbering element if it doesn't have an
explicit level---we just set that level to 1. (In the style files, the
examples I've seen don't have that explicit level.)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|