Age | Commit message (Collapse) | Author | Files | Lines |
|
Simplified code by using plainExtensions from Options.
Closes #2237.
|
|
|
|
`<` should not be escaped as `\<`, for compatibility with
original Markdown. We now escape `<` and `>` with entities.
Also, we now backslash-escape square brackets.
Closes #2086.
|
|
|
|
Support shortcut reference links in markdown writer
|
|
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`).
|
|
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 #1946.
|
|
https://ghc.haskell.org/trac/ghc/wiki/Migration/7.10#GHCsaysNoinstanceforFoldable...arisingfromtheuseof...
|
|
`tex_math_dollars`, `superscript`, and `subscript` extensions,
respectively.
Closes #1127.
|
|
|
|
pandoc -t markdown-raw_html should not emit any raw HTML, even
span and div tags that go with pandoc Span and Div elements.
Cleaned up a bit of the logic with extensions and plain.
|
|
|
|
Using `map toUpper` to capitalise text is wrong, as e.g.
“Straße” should be converted to “STRASSE”, which is 1 character
longer. This commit adds a `capitalize` function and replaces
2 identical implementations in different modules (`toCaps` and
`capitalize`) with it.
|
|
Closes #1458.
|
|
Math now appears in unicode if possible, without the distracting
italics around identifiers.
Blank lines around headers are more consistent.
Footnotes appear in regular [n] style.
|
|
We now largely follow the style of Project Gutenberg.
Emphasis is rendered with `_underscores_`, strong with ALL CAPS.
The appearance of horizontal rules has changed (even in regular
markdown) to a line across the whole page.
Headings are rendered differently, using space to set them off.
|
|
They now behave like the new reader does. The old behavior
can be activated with the `compact_definition_lists` extension.
|
|
Or a blockquote or header. Closes #1013.
|
|
Also removed deprecated readTeXMath.
|
|
|
|
|
|
This properly handles tags that should be self-closing.
Previously `<hr/>` would appear in EPUB output as `<hr></hr>`.
Closes #1420.
|
|
Removed `Ext_fenced_code_attributes` from `markdown_github`
extensions.
If this extension is not set, the first class attribute will
be printed after the opening fence as a bare word.
Closes #1416.
|
|
Columns are now aligned. Closes #1323.
|
|
|
|
Previously we used 0-width spaces, an ugly hack.
Closes #980.
|
|
If the content contains a backtick fence and there are
attributes, make sure longer fences are used to delimit the code.
Note: This works well in pandoc, but github markdown is more
limited, and will interpret the first string of three or more
backticks as ending the code block.
Closes #1206.
|
|
Replaces long conditional chains with calls to `elem` and `notElem`.
|
|
A consequence of this change is that the backtick form will be
preferred in general if both are enabled. I think that is good,
as it is much more widespread than the tilde form.
Closes #1084.
|
|
E.g.
- foo
- bar
- baz
Previously a spurious blank line was included before the last item.
Closes #1050.
|
|
|
|
Deprecate readTeXMath, and use readTeXMath' in all the writers.
Require texmath >= 0.6.5.
|
|
It allows fragments identifiers.
|
|
|
|
|
|
|
|
* Add ??? as fallback text for non-resolved citations.
* Biblio: Put references (including a header at the end of
the document, if one exists) inside a Div with class "references".
This gives some control over styling of references, and allows
scripts to manipulate them.
* Markdown writer: Print markdown citation codes, and disable
printing of references, if `citations` extension is enabled.
NOTE: It would be good to improve what citeproc-hs does for
a nonexistent key.
|
|
Textile, MediaWiki, Markdown, Org, RST will emit raw HTML div tags for divs.
Otherwise Div and Span are "transparent" block containers.
|
|
They are significantly faster.
|
|
Currently these are "transparent" containers, except in HTML,
where they produce div and span elements with attributes.
|
|
|
|
Previously it was only rendered if title, author, or date set.
Now any metadata field can be set.
|
|
|
|
It's just commas with brackets that can cause problems.
|
|
This makes the output predictable; previously it varied across
implementations.
|
|
* Text.Pandoc.Writers.Shared contains shared functions used
only in writers.
* metaToJSON now takes a WriterOptions parameter, and will
return an empty object if standalone is not specified.
|
|
|