| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
They are now rendered with a `>` between them.
Closes #1817.
|
|
Closes #1816.
|
|
Closes #1815.
|
|
Org reader: properly handle links to `file:target`
|
|
Org links like `[[file:target][title]]` were not handled correctly,
parsing the link target verbatim. The org reader is changed such that
the leading `file:` is dropped from the link target.
This is related to issues #756 and #1812.
|
|
Closes #1811.
The price of this is that autolinked bare URIs can no longer
contain `>` characters, but this is not a big issue.
|
|
|
|
Move recursive role lookup from renderRole to addNewRole. The Attr value
will be the same for every occurance of this role, so there's no reason
to compute it every time. This allows simplifying the
stateRstCustomRoles map considerably.
We could go even further, and remove the fmt and attr arguments to
renderRole, which are null except for custom roles.
|
|
|
|
- Add "sourceCode" to classes for :code: role, and anything inheriting
from it.
- Add the name of the custom role to classes if the Inline constructor
supports Attr.
- If the custom role directive does not specify a parent role, inherit
from the :span: role.
This differs somewhat from the rst2xml.py behavior. If a custom role
inherits from another custom role, Pandoc will attach both roles' names
as classes. rst2xml.py will only use the class of the directly invoked
role (though in the case of inheriting from a :code: role with a
:language: defined, it will also provide the inherited language as a
class).
|
|
code role should have "code" class.
http://docutils.sourceforge.net/docs/ref/rst/roles.html says that
`text`:literal` is the same as ``text``. docutils outputs a <literal>
element in both cases, whereas for the code role, it outputs a <literal>
element with the "code" class.
|
|
This commit moves some code which was only used for the Markdown Reader
into a generic form which can be used for any Reader. Otherwise, it
takes naming and interface cues from the preexisting Markdown code.
|
|
Escape inline verbatim spaces in LaTeX output
|
|
DocBook reader: add support for "classname", document and test "type"
|
|
|
|
DocBook reader: add support for calloutlist and callout
|
|
|
|
Link the test suite using -threaded
|
|
|
|
This allows the test suite to be run using "+RTS -N".
Doing so improves the performance of the test suite on my quad-core Mac laptop as follows:
Before: 8.2 seconds
After: 2.5 seconds
|
|
We treat a calloutlist as a bulleted list. This works well in practice.
|
|
DokuWiki writer: fix external images
|
|
Fix for #1641 (docx table captions above tables)
|
|
Add an -email address link- example to README.
|
|
Word doesn't really treat table captions as something special. It's just a paragraph with special style, nothing more, so simple reversal of output order in writer works fine.
|
|
move `addWarning` to Parsing.hs, so it can be used by Markdown & RST readers.
|
|
Closes #1788.
|
|
First step to fixing internationalisation problems with docx output
|
|
Text.Pandoc.Pretty: Improve performance of realLength
|
|
Eliminates memory usage and twofold increase in speed.
|
|
Update pandoc.cabal, Bumping JuicyPixels upper bound
|
|
|
|
parse RST quoted literal blocks and class directives
|
|
The class directive accepts one or more class names, and creates a Div
value with those classes. If the directive has an indented body, the
body is parsed as the children of the Div. If not, the first block
folowing the directive is made a child of the Div.
This differs from the behavior of rst2xml, which does not create a Div
element. Instead, the specified classes are applied to each child of
the directive. However, most Pandoc Block constructors to not take an
Attr argument, so we can't duplicate this behavior.
|
|
closes #65
RST quoted literal blocks are the same as indented literal blocks (which
pandoc already supports) except that the quote character is preserved in
each line.
This includes test cases for the quoted literal block, as well as
additional tests for line blocks and indented literal blocks, to verify
that these are unaffected by the changes.
|
|
|
|
Now we do as before, including blank lines after list items in
loose lists (even though RST doesn't care -- this is just a matter
of visual appeal). But we chomp any excess whitespace after the
last list item, which solves #1777.
|
|
They are optional in RST (except after the last list item,
of course).
Fixes #1777.
|
|
|
|
See jgm/pandoc-citeproc#26.
|
|
Closes #1769.
|
|
Not title page!
|
|
This includes the HTML doctype.
Closes #1759.
|
|
This fixes a bug introduced by the previous fix.
|
|
This aids styling, making it possible for example to set 0 margins
on the title page. Closes jgm/pandoc#1758.
|
|
Closes #1756.
|
|
|
|
Closes #1761. This is needed for epub3 validation.
See http://www.idpf.org/epub/20/spec/OPF_2.0.1_draft.htm#Section2.3.1
|
|
- a
- b
* c
was being parsed as a list, even though an unindented `*`
should make a heading. See
<http://orgmode.org/manual/Plain-lists.html#fn-1>.
|
|
|
