| Commit message (Collapse) | Author | Age |
|---|
| |
|
|
|
|
|
|
|
| |
Renamed some tests, introducing subsidiary directories
for fb2, docx, epub.
Cleaned up tests in cabal file.
Combined dokuwiki-writer and dokuwiki_inline_formatting tests.
|
| |
|
|
|
|
|
|
|
| |
This was just too fragile and dependent on a changing Cabal API
(see #1526).
Instead of passing the bulid directory to the test program, we
now let the test program find itself (using executable-path)
and then find the pandoc executable relative to itself.
|
| |
|
|
|
| |
This epub contains many epub:type elements including footnotes and
titlepage.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Rewrote features test to remove all unimplemented features.
There are now all three examples of where an image can be included in
the test.
1. Cover image
2. As a spine elemnt
3. In the document
Tests have also been added to make sure that the mediabag contains all
these images after processing.
|
| | |
|
| |
|
|
|
|
|
|
|
| |
Renamed epub test files so they're identified more clearly as
epub: features.{epub,native} -> epub.features.{epub,native},
and similarly with formatting.{epub,native}.
Added epub test files to cabal file, so they'll be included in
the tarball.
|
| | |
|
| |\
| |
| |
| |
| |
| |
| | |
mpickering-epubend
Conflicts:
pandoc.cabal
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| | |
Using `map toUpper` to capitalise text is wrong, as e.g.
“Straße” should be converted to “STRASSE”, which is 1 character
longer. This commit adds a `capitalize` function and replaces
2 identical implementations in different modules (`toCaps` and
`capitalize`) with it.
|
| |/
|
|
|
|
|
|
|
|
| |
This will allow us to test the whole mediabag (making sure, for example,
that images are added with the correct keys) instead of just individual
extracted images. We compare each entry in the media bag to an image
extracted on the fly from the docx. As a result, we only need one file
to test with.
The image in the current tests was also replaced with a smaller one.
|
| |
|
|
|
|
|
| |
Moved `MediaBag` definition and functions from Shared:
`lookupMedia`, `mediaDirectory`, `insertMedia`, `extractMediaBag`.
Removed `emptyMediaBag`; use `mempty` instead, since `MediaBag`
is a Monoid.
|
| |
|
|
|
|
|
|
|
|
| |
Shared now exports functions for interacting with a MediaBag:
- `emptyMediaBag`
- `lookuMedia`
- `insertMedia`
- `mediaDirectory`
- `extractMediaBag`
|
| | |
|
| |
|
|
|
| |
Also tell pandoc.cabal that we'll be needing base64, since we want to
compare strings here.
|
| | |
|
| |
|
|
| |
Closes #1464.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
| |
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.
|
| | |
|
| |
|
|
| |
Closes #1452. Added test.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* 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.
|
| |
|
|
| |
Test auto ident header anchors with pandoc-generated pandoc.
|
| | |
|
| | |
|
| | |
|
| |\
| |
| |
| | |
claremacrae-dokuwiki
|
| | | |
|
| | |\ |
|
| | |\ \ |
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
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.
|
| | | | |
| | | |
| | | |
| | | | |
In this first version, all dokuwiki files are straight copies of the
media wiki counterparts.
|
| | |_|/
|/| |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
- We no longer include trailing spaces and newlines in the
raw blocks.
- We look for closing tags for elements (but without backtracking).
- Each block-level tag is its own RawBlock; we no longer try to
consolidate them (though `--normalize` will do so).
Closes #1330.
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
* Added normalizeInlines, normalizeBlocks.
* Type signature is now more narrow, `Pandoc -> Pandoc` instead of
`Data a :: a -> a`. Some users may need to change their uses of
`normalize` to the newly exported `normalizeInlines` or
`normalizeBlocks`.
|
| | |/
|/|
| |
| |
| |
| |
| |
| | |
We want to treat it as a plain paragraph if the hanging amount is
greater to or equal to the left indent---i.e., if the first line has
zero indentation. But we still want it to be a block quote if it starts
to the right of the margin. Someone might format verse with wrapping
lines with a hanging indent, for example.
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| | |
This is what seems like the sensible default: read in insertions, and
ignore deletions. In the future, it would be good if options were
available for either taking in deletions or keeping both in some
scriptable format.
|
| | | |
|
| | | |
|
| |\ \
| | |
| | | |
Docx rewrite and cleanup (in terms of Reducible typeclass)
|
| | | |
| | |
| | |
| | |
| | | |
This used to be fixed in the tree-walking. We need to make sure we're doing it
right now.
|
| |/ /
| |
| |
| |
| | |
Otherwise we get curly quotes in the PDF output.
Closes #1364.
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| | |
Add torture-test for new normalization functions.
One problem that this test demonstrates is that word has a tendency to
turn off formatting at a space, and then turn it back on after. I'm not
sure yet whether this is something we should fix.
|
| | |
| |
| |
| |
| |
| |
| | |
This is just a wrapper around Pandoc that doesn't normalize with
`toString`. We want to make sure that our own normalization process
works. If, in the future, we are able to hook into the builder's
normalization, this will be removed.
|
| | |
| |
| |
| | |
Previously strikeout highlighted code caused an error.
|
