| Commit message (Collapse) | Author | Age |
| |
|
|
|
|
|
|
|
|
|
| |
Added `Ext_gfm_auto_identifiers`: new constructor for `Extension`
in `Text.Pandoc.Extensions` [API change].
Use this in githubExtensions.
Closes #2821.
|
|
|
|
|
|
|
| |
We bypass the commonmark writer from cmark and construct our
own pipe tables, with better results. (Note also that cmark-gfm
currently doesn't support rendering table nodes; see
kivikakk/cmark-gfm-hs#3.)
|
|
|
|
|
|
|
|
| |
when enabled (as with gfm). Note: because of limitations in
cmark-gfm, which will hopefully soon be corrected, this currently
gives an error on Tables.
Also properly support `--wrap=none`.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
We no longer have a separate readGFM and writeGFM;
instead, we'll use readCommonMark and writeCommonMark
with githubExtensions.
It remains to implement these extensions conditionally.
Closes #3841.
|
|
|
|
| |
Advise to use `gfm` instead.
|
| |
|
| |
|
| |
|
|
|
|
| |
Closes #3832.
|
|
|
|
|
| |
We now disallow reference keys starting with `@` if the
`citations` extension is enabled. Closes #3840.
|
|
|
|
| |
This reverts commit 8995281691b56d711c44fb0c5cae2fc675d12eb9.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This uses bindings to GitHub's fork of cmark, so it should parse
gfm exactly as GitHub does (excepting certain postprocessing
steps, involving notifications, emojis, etc.).
* Added Text.Pandoc.Readers.GFM (exporting readGFM)
* Added Text.Pandoc.Writers.GFM (exporting writeGFM)
* Added `gfm` as input and output forma
Note that tables are currently always rendered as HTML
in the writer; this can be improved when CMarkGFM supports
tables in output.
|
|
|
|
| |
rather than WARNING.
|
| |
|
|
|
|
|
|
|
| |
Note that we still don't support macros with fancy parameter
delimiters, like
\def\foo#1..#2{...}
|
|
|
|
|
|
|
|
| |
Also, fix regular macros so they're expanded at the
point of use, and NOT also the point of definition.
`\let` macros, by contrast, are expanded at the
point of definition. Added an `ExpansionPoint`
field to `Macro` to track this difference.
|
|
|
|
| |
Closes #3836.
|
|
|
|
| |
Take only first line indentation into account
and do not start new paragraph on indentation change.
|
|
|
|
|
|
|
|
|
|
| |
We used to parse paragraphs styled with "HeadingN" as "nth-level
header." But if a document has a custom style named "Heading0", this
will produce a 0-level header, which shouldn't exist. We only parse
this style if N>0. Otherwise we treat it as a normal style name, and
follow its dependencies, if any.
Closes #3830.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Closes #3824.
|
|
|
|
|
| |
If `all_symbols_escapable` is set, we backslash escape these.
Otherwise we use entities as before.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
We previously did this only with raw blocks, on the assumption
that math environments would always be raw blocks. This has changed
since we now parse them as inline environments.
Closes #3816.
|
|
|
|
|
|
|
|
|
|
| |
Thus, a span with attribute 'foo' gets written to HTML5
with 'data-foo', so it is valid HTML5.
HTML4 is not affected.
This will allow us to use custom attributes in pandoc without
producing invalid HTML.
|
|\
| |
| |
| | |
into schrieveslaach-textcolor-support
|
| |\ |
|
| |\ \ |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
It is no longer necessary, since the rawLaTeXBlock parser
will parse macro definitions.
This also avoids the need for a separate latexMacro parser
in the Markdown reader.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Fixed applyMacros so that it operates on the whole
string, not just the first token!
Don't remove macro definitions from the output,
even if Ext_latex_macros is set, so that macros will
be applied. Since they're only applied to math in
Markdown, removing the macros can have bad effects.
Even for math macros, keeping them should be harmless.
|
| | | | |
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
An unknown command at the beginning of the line that could
be either block or inline is treated as block if we have
a sequence of block commands followed by a newline or a
`\startXXX` command (which might start a raw ConTeXt environment).
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Added TikiWiki reader, including tests and documentation.
It's probably not *complete*, but it works pretty well, handles all
the basics (and some not-so-basics).
|