| Commit message (Collapse) | Author | Age |
|---|
| ... | |
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This will make paragraphs styled with `Author`, `Title`, `Subtitle`,
`Date`, and `Abstract` into pandoc metavalues, rather than text. The
implementation only takes those elements from the beginning of the
document (ignoring empty paragraphs).
Multiple paragraphs in the `Author` style will be made into a metaList,
one paragraph per item. Hard linebreaks (shift-return) in the paragraph
will be maintained, and can be used for institution, email, etc.
|
| |/
|
|
|
|
|
|
|
| |
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.
|
| | |
|
| |
|
|
| |
Closes #1452. Added test.
|
| |
|
|
|
| |
Of course, we can't include structure in the code block, but
this way we at least preserve the text. Closes #1449.
|
| |
|
|
| |
Closes #1434.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* 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.
|
| |
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
| |
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.
|
| |\
| |
| | |
Fix auto identified headers when already auto-id'ed
|
| | |
| |
| |
| | |
Test auto ident header anchors with pandoc-generated pandoc.
|
| |/
|
|
|
|
| |
This allows them to be styled using `\urlstyle{tt}`.
Thanks to Ulrike Fischer for the solution.
|
| |
|
|
|
|
| |
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)
|
| | |
|
| | |
|
| |\
| |
| |
| |
| | |
Use removeFormatting from Shared instead of the custom unfancy
function.
|
| | | |
|
| | | |
|
| |/
|
|
|
| |
The standard seems to be captions above tables. (See
http://tex.stackexchange.com/questions/3243/why-should-a-table-caption-be-placed-above-the-table)
|
| | |
|
| | |
|
| | |
|
| |\
| |
| |
| | |
claremacrae-dokuwiki
|
| | |
| |
| |
| |
| |
| |
| | |
This reverts commit 23d71b13e7b462229427e2437a8dd9c8f72d72f1.
This is now resulting in a testsuite failure, and I can't see why
it didn't do so before
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| | |
This doesn't change the testsuite behaviour, but it does mean that
all the testsuite output files are exactly identical to the
output obtained by running the current pandoc.
|
| | |
| |
| | |
This added \cite and \begin latex to the testuite output.
|
| | |
| |
| | |
TODO Also implement nested blockquotes.
|
| | |\ |
|
| | | | |
|
| | | |
| | |
| | |
| | | |
For example, this fixes the display of a broken table, and
it also fixes the various HTML horizontal rules.
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The new code was got from inspecting changes in MediaWiki.hs
This slightly changes the output of Div blocks, but I'm not
convinced the original behaviour was really correct anyway.
The code for handling Span does nothing for now, until I can
work out the desired behaviour, and add tests for it.
|
| | |\ \ |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
When the original document had text containing //, this was previously
included, unchanged, in the dokuwiki output, and this interacted badly
with later, intended, formating text.
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
Done because I noticed that in the Autolinks section of writer.dokuwiki, the URL in inlined code was getting auto-linked, when it wasn't supposed to.
This also meant that any inline code examples that had text that looked like dokuwiki syntax could break the formatting of later text.
|
| | | | |
| | | |
| | | |
| | | | |
writer (#386)
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
I've found some incorrect behaviours with the dokuwiki output, for which
extra test cases will be needed - that aren't covered by the standard
pandoc test input files.
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
