Age | Commit message (Collapse) | Author | Files | Lines |
|
Not only faster but uses less memory.
|
|
This should work on Windows, unlike the TH solution with
file-embed.
|
|
This module just exports the association list of embedded data files,
which is used by Shared.
|
|
* Tilde code fences can again take bare language.
So
~~~ haskell
is okay, not just
~~~ {.haskell}
* Backtick code blocks can take the bracketed attributes.
* Backtick code blocks don't require a language.
* Consolidated code for the two kinds of fenced code blocks.
Closes #722.
|
|
|
|
|
|
Otherwise \begin{code}...\end{code} isn't handled
properly in markdown+lhs.
Thanks to Daniel Miot for noticing the bug and
suggesting the fix.
|
|
blaze-html/blaze-markup-0.5 has Text.Blaze.Html.Renderer.Utf8
whereas blaze-html-0.4 has Text.Blaze.Renderer.Utf8.
So this needs to be conditional on the version for pandoc
still be with blaze-html-0.4.x
|
|
Closes #714.
|
|
The 1.10 code assumed that each table header cell contains
exactly one block. That failed for headerless tables (0) and also
for tables with multiple blocks in a header cell.
The code is fixed and tests provided. Thanks to Andrew Lee for
pointing out the bug.
|
|
The bug prevented an autolink at the end of a string (e.g.
at the end of a line block line) from counting as a link.
Closes #711.
|
|
Also added tests. Closes #710.
|
|
This contains a space-separated list of citation IDs.
|
|
* RTF writer: Export writeRTFWithEmbeddedImages instead of
rtfEmbedImage.
* Text.Pandoc: Use writeRTFWithEmbeddedImages for RTF.
* Moved code for embedding images in RTF out of pandoc.hs.
|
|
if --listings is used.
Closes #704.
|
|
These are used in revealjs css.
|
|
This reverts commit b158b3fb2182b5c8a6f03759277f4f73cdc24797.
|
|
This allows attributes like `C++`. Any nonspace and non-}.
|
|
|
|
Also simplified source URL and link title parsers.
|
|
|
|
|
|
Also added 'markdown_mmd' as input/output option.
|
|
|
|
The previous default was to use `<q>` tags in HTML5.
But `<q>` tags are also valid HTML4, and they are not very
robust in HTML5. Some user agents don't support them,
and some CSS resets prevent pandoc's quotes CSS from working
properly (e.g. bootstrap). It seems a better default just
to insert quote characters, but the option is provided for
those who have gotten used to using `<q>` tags.
|
|
Added tests.
|
|
|
|
oneOfStrings will now take the longest match it can in a
list of strings, so if 'foo' and 'foobar' are both included,
'foobar' will match even if 'foo' is first in the list.
|
|
* It no longer uses Network.URIs URI parser, which is too restrictive
(not allowing unicode URIs unless encoded).
* It allows many more schemes.
* It better handles punctuation so as to avoid capturing trailing
punctuation in bare URLs.
|
|
Revises 1a4b47e93368bfbd31daccdfedbd9527ee740201
|
|
* In markdown reader, add a '\1' character to the beginning
of the title of an image that is alone in its paragraph,
if implicit_figures extension is selected.
* In writers, check for Para [Image alt (src,'\1':tit)] and treat
it as a figure if possible.
* Updated tests.
This is a bit of a hack, but it allows us to make implicit_figures
an extension of the markdown reader, rather than the writers.
|
|
|
|
Otherwise Network.URI.parseURI fails on e.g. Chinese
URLs. Changed an incorrect test in markdown-reader-more.
|
|
No code to hook this in yet.
|
|
This makes 's', 'l', etc. parse properly.
Formerly we had some English-centric heuristics, but they
are no longer needed now that we keep track of the last
'Str' position in state.
Closes #698.
|
|
We now (a) use anonymous links for links with inline URLs, and
(b) use an inline link instead of a reference link if the
reference link would require a label that has already been
used for a different link.
Closes #511.
|
|
Closes #678.
|
|
This depends on the new Ext_line_blocks extension.
|
|
This will be used by both RST and markdown readers.
|
|
|
|
|
|
* Use nonbreaking spaces for initial indent (otherwise lost in HTML and
LaTeX).
* Allow multiple paragraphs in a single line block.
|
|
Previously linebreaks weren't supported in RST, since RST
has no native linebreak construct.
|
|
|
|
|
|
This avoids a clash with highlighting-kate's macros, which
redefine | as a short verbatim delimiter. Thanks to
Björn Peemöller for raising this issue.
|
|
This seems to match the spacing of ~ exactly.
|
|
Since `~` spaces after a line break are just ignored.
Closes #687.
|
|
We need to ensure that all headers have attributes, since
this is no longer guaranteed by hierarchicalize.
Explicitly given headers remain the same.
|
|
|