Age | Commit message (Collapse) | Author | Files | Lines |
|
Closes #1434.
|
|
It now works as in PHP markdown extra. Setting `markdown="1"` on
an outer tag affects all contained tags until it is reversed with
`markdown="0"`. Closes #1378.
Added `stateMarkdownAttribute` to `ParserState`.
|
|
Test case:
<aside markdown="1">
*hi*
</aside>
Previously gave:
<article markdown="1">
<p><em>hi</em> </article></p>
|
|
|
|
* This change brings pandoc's definition list syntax into alignment
with that used in PHP markdown extra and multimarkdown (with the
exception that pandoc is more flexible about the definition markers,
allowing tildes as well as colons).
* Lazily wrapped definitions are now allowed; blank space is required
between list items; and the space before definition is used to
determine whether it is a paragraph or a "plain" element.
* For backwards compatibility, a new extension,
`compact_definition_lists`, has been added that restores the behavior
of pandoc 1.12.x, allowing tight definition lists with no blank space
between items, and disallowing lazy wrapping.
|
|
We need input to be a string so we can print the offending line
on an error.
|
|
This gives better results for tight lists. Closes #1437.
An alternative solution would be to use Para everywhere, and
never Plain. I am not sufficiently familiar with org to know
which is best. Thoughts, @tarleb?
|
|
Closes #1441.
|
|
Renamed readTeXMath' to avoid name conflict with texmath 0.6.7
|
|
|
|
Also removed deprecated readTeXMath.
|
|
|
|
Org reader: Respect :exports header arguments on code blocks
|
|
Adds support to the org reader for conditionally exporting either the code block,
results block immediately following, both, or neither, depending on the value
of the `:exports` header argument. If no such argument is supplied, the default
org behavior (for most languages) of exporting code is used.
|
|
|
|
Removed HTML header scaffolding from data/sample.lua.
|
|
|
|
|
|
Thanks @dubiousjim. Close #1431.
|
|
Fix auto identified headers when already auto-id'ed
|
|
If header anchors (bookmarks in a header paragraph) already have an
auto-id, which will happen if they're generated by pandoc, we don't want
to rename it twice, and thus end up with an unnecessary number at the
end. So we add a state value to check if we're in a header. If we are,
we don't rename the bookmark -- wait until we rename it in our header
handling.
|
|
We don't need `updateDState` -- the built-in `modify` works just
fine. And we redefine `withDState` to use modify.
|
|
|
|
This allows them to be styled using `\urlstyle{tt}`.
Thanks to Ulrike Fischer for the solution.
|
|
This allows easier diff-ability. Closes #1424.
|
|
For correct highlighting of identifiers in prolog and other languages.
|
|
Close #1427.
|
|
Test auto ident header anchors with pandoc-generated pandoc.
|
|
Closes #1421.
|
|
As far as I can see, dokuwiki markup is pretty limited in what
can go in a `>` block quote: just a single line of paragraph
text. (#1398)
|
|
as in the mediawiki writer. The dokuwiki markup isn't able
to handle multiple block-level items within a list item, except
in a few special cases (e.g. code blocks, and these must be started
on the same line as the preceding paragraph). So we fall back to
raw HTML for these.
Perhaps there is a better solution. We can "fake" multiple
paragraphs within list items using hard line breaks (`\\`), but
we must keep everything on one line.
(#1398)
|
|
|
|
|
|
|
|
(#1398)
|
|
|
|
* Use uppercase HTML tags for block-level content, lowercase for
inline.
* Newline before closing HTML tag.
|
|
* mediawiki > dokuwiki
* ignore raw content other than html or dokuwiki.
(#1398)
|
|
|
|
|
|
|
|
As far as I can tell, it does about the same thing.
|
|
|
|
|
|
Use removeFormatting from Shared instead of the custom unfancy
function.
|
|
API change (addition of exported function).
|
|
This properly handles tags that should be self-closing.
Previously `<hr/>` would appear in EPUB output as `<hr></hr>`.
Closes #1420.
|
|
Thanks to @dubiousjim. Closes #1419.
|
|
This originated with @dubiousjim's observation in #1419
that there was a typo in the definition of enDash.
It returned an em dash character instead of an en dash.
I thought about why this had not been noticed before, and
realized that en dashes were just being parsed as regular
symbols.
That made me realize that, now that we no longer have
dedicate EnDash, EmDash, and Ellipses inline elements, as
we used to in pandoc, we no longer need to parse the
unicode characters specially. This allowed a considerable
simplification of the code.
Partially resolves #1419.
|
|
|