Age | Commit message (Collapse) | Author | Files | Lines |
|
Previously the div-enclosed reference section produced
by pandoc-citeproc would not be split into its own chapter,
which caused various problems.
See #2162, #2163.
I'm not sure this is a complete fix. I note that the bibliography
doesn't appear in nav or toc, which seems bad.
|
|
This might help diagnose #777.
|
|
This makes the writer work properly with linked bibliographic
items with pandoc-citeproc.
Closes jgm/pandoc-citeproc#132.
|
|
Added `stateHeaderKeys` to `ParserState`; this is a `KeyTable`
like `stateKeys`, but it only gets consulted if we don't find
a match in `stateKeys`, and if `Ext_implicit_header_references`
is enabled.
Closes #1606.
|
|
We only support the href attribute, as there's no place for
"target" in the Pandoc document model for links.
Added HTML reader test module, with tests for this feature.
Closes #1751.
|
|
Closes #2119.
|
|
We now look at the mime type from the server and attach an
appropriate extension.
Closes #1855.
|
|
Introduced by e9d7504.
This regression caused link and image references containing
raw tex not to parse correctly.
Added test.
Closes #2150.
|
|
Instead, just use an a element with class `footnoteRef`.
This allows more styling options, and provides better results
in some readers (e.g. iBooks, where anything inside the a
tag breaks popup footnotes).
Closes #1995.
|
|
Earlier versions had a bug and would wrongly think
opening tags containing attributes with slashes in them
were self-closing.
Closes #2146.
|
|
Closes #1834. The image originally supplied works fine now
with pandoc.
|
|
Closes #1834.
|
|
|
|
See #1834.
|
|
This will give us better error reporting options.
This is part of a fix for #1834.
|
|
This reverts commit 1c2951dfd9ee72e5270cb974a06098adb9178f89.
See #2040.
The semantics was too squishy. `--css` takes a URL, but
for EPUB we need files that we can read. I prefer keeping
the old system for now, with `--epub-stylesheet`.
|
|
* Allow `--css` to be used to specify stylesheets.
* Deprecated `--epub-stylesheet` and made it a synoynym of
`--css`.
* If a code block with class "css" is given as contents of the
`stylesheet` metadata field, use its literal code as contents of
the epub stylesheet. Otherwise, treat it as a filename and
read the file.
* Note: `--css` and `stylesheet` in metadata are not compatible.
`stylesheet` takes precedence.
|
|
|
|
Previously we just stripped them out; now we convert
other line ending styles to LF line endings.
Closes #2132.
|
|
Also use a proper css parser (adds dependency on text-css).
Closes #2129.
|
|
Closes #2127.
|
|
Otherwise links don't work.
|
|
This gives better results when we have, e.g. multiple paragraphs.
Note that tags aren't allowed in these fields.
Closes #2121.
|
|
The current test is: does the URL start with a `#`?
Closes #2121.
|
|
|
|
Closes #2122.
|
|
Closes #1609.
|
|
This fixes a regression (not in any released version) on
things like
hi
: - there
Closes #2098.
|
|
Custom Writer: Set foreign encoding to UTF-8
|
|
|
|
Closes #2101, #1634
Also factored out ByteString, since it's only used as an intermediate
representation.
|
|
|
|
This might help with #2101.
|
|
This version should be a bit more efficient.
This doesn't help with #1735, however.
|
|
Footnotes: check if '^' follows '['
Links: check if '[' or '(' follows ']'
Shorthand links: attempt to lazily parse suffix as referenceLink
|
|
Closes #2062.
This reverts commit c302bdcdbe97b38721015fe82403b2a8f488a702, reversing
changes made to b983adf0d0cbc98d2da1e2751f46ae1f93352be6.
Conflicts:
src/Text/Pandoc/Parsing.hs
src/Text/Pandoc/Readers/Markdown.hs
src/Text/Pandoc/Readers/Org.hs
src/Text/Pandoc/Readers/RST.hs
|
|
`<` should not be escaped as `\<`, for compatibility with
original Markdown. We now escape `<` and `>` with entities.
Also, we now backslash-escape square brackets.
Closes #2086.
|
|
Previously the body of the definition (after the `:` or `~` marker)
needed to be in column 4. This commit relaxes that requirement,
to better match the behavior of PHP Markdown Extra. So, now
this is a valid definition list:
foo
: bar
This patch also helps resolve a potentially ambiguity with table
captions:
foo
: bar
-----
table
-----
Is "bar" a definition, or the caption for the table? We'll count
it as a caption for the table.
Closes #2087.
|
|
If the tag parses as a comment, we check to see if the
input starts with `<!--`. If not, it's bogus comment mode
and we fail htmlTag.
Includes test case. Closes #1820.
|
|
jlduran-latex-tightlist
Conflicts:
data/templates
|
|
Allow digit as first character of a citation key.
|
|
RST Writer: Normalize headings to sequential levels
|
|
MD Reader: Smart apostrophe after inline math
|
|
Require that `<!` or `<?` be followed by nonspace.
This prevents `</ div>` from being parsed as a comment.
Closes #1820.
|
|
Closes #1909.
Adds new parser combinator to Parsing.hs
`a <+?> b`
: if a succeeds, applies b and mappends
output (if any) to result of a. If b fails,
it's just a, if a fails, whole expression fails.
|
|
|
|
|
|
This is pretty much required by docutils.
|
|
|
|
Previously the depth was being rendered as a floating point
number with a decimal point. Thanks to Nick Yakimov for
noticing this.
|