| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
|
|
This brings pandoc's rendering of haddock markup in line
with the new haddock.
Note that we preserve line breaks in `@` code blocks, unlike
the earlier version.
Modified tests pass. More tests would be good.
|
|
This also removes the dependency on alex and happy.
|
|
Closes #1287, jgm/highlighting-kate#40.
|
|
Closes #1236.
Note, this is a bit of a kludge, to work around the fact that xml-light
doesn't parse `<?asciidoc-br?>` correctly. We preprocess the input,
replacing that instruction with `<br/>`, and then parse that as a line
break. Other XML instructions are simply removed from the input stream.
|
|
LaTeX seems to treat them as if they have empty cells at the
end. Closes #241.
|
|
|
|
For consistency with the existing writer.
|
|
|
|
Closes #1345. Also relabeled 'code' and 'verbatim' parsers
to accord with the org-mode manual.
I'm not sure what the distinction between code and verbatim
is supposed to be, but I'm pretty sure both should be represented
as Code inlines in pandoc. The previous behavior resulted in the
text not appearing in any output format.
|
|
This allows blank lines at end of multiline headers.
|
|
|
|
`\emph{ hi }` gets parsed as `[Space, Emph [Str "hi"], Space]`
so that we don't get things like `* hi *` in markdown output.
Also applies to textbf and some other constructions.
Closes #1146. (`--normalize` isn't touched by this, but
normalization should not generally be necessary with the
changes to the readers.)
|
|
Closes #1338.
|
|
Table cells were being combined into one cell. Closes #1341.
|
|
Moved extractSpaces to Shared.hs
|
|
This change rewrites `inlineLaTeXCommand` so that parsec will
know when input is being consumed. Previously a run-time
error would be produced with some input involving raw latex.
(I believe this does not affect the last release, as the inline
latex reading was added recently.)
|
|
Generalised and move the extractSpaces function from `HTML.hs` to
`Shared.hs` so that the docx reader can also use it.
|
|
This introduces Text.Pandoc.DocX, and its exported `readDocX` function.
|
|
|
|
This resolves the issue illustrated in
http://stackoverflow.com/questions/24009489/comments-in-latex-break-pandoc-table.
|
|
Columns are now aligned. Closes #1323.
|
|
Closes #1305.
|
|
This should have fixed #1305, allowing the reference.docx to define
section numbering, but it doesn't. Now the headings appear with proper
indentation, but the numbers don't appear. Unclear why. styles.xml and
numbering.xml basically match the docx which has the expected result.
|
|
This opens up the possiblity (with further code changes) of
preserving some numbering from the reference.docx (e.g. header
numbering.) See #1305.
|
|
Now the minimum id used by pandoc is 990. All ids start with "99".
This gives some room for a reference.docx to define numbering styles.
Note: this is not yet possible, since pandoc generates numbering.xml
entirely on its own.
|
|
Instead of sequential numbering, we assign numbers based on the
list marker styles. This simplifies some of the code and should
make it easier to modify numbering in the future.
|
|
Closes #1022.
|
|
API change (adds export).
|
|
This should be somewhat more robust and cover more types
of images.
|
|
No need to parse the XML if we're just going to render it
right away!
|
|
* All media from reference.docx are copied into result.
* Added defaults for common image types to [Content Types].
* Avoided redundant XML parse + write for entries taken over from
reference.docx, for better performance.
|
|
With the move from parsec to attoparsec, we lost good error
reporting. In fact, since we weren't testing for end of input,
malformed templates would fail silently. Here we revert back to
Parsec for better error messages.
|
|
|
|
|
|
|
|
This includes margins, page size, page orientation.
|
|
Closes #1062.
|
|
Org reader: support for inline LaTeX
|
|
in github-style fenced blocks. Closes #1318.
Note: This is special-case handling of these two cases.
It would be good to do something more systematic.
|
|
Closes #1313.
|
|
Inline LaTeX is now accepted and parsed by the org-mode reader. Both,
math symbols (like \tau) and LaTeX commands (like \cite{Coffee}), can be
used without any further escaping.
|
|
Note: in EPUB3 we can have only one dc:date, so only the first
one is used.
|
|
See #1309.
|
|
* http-conduit flag is now https.
* Instead of http-conduit, we depend on http-client and http-client-tls.
|
|
In 1.12.4 and 1.12.4.2, the cover image would not appear properly,
because the metadata id was not correct.
This was introduced by the fix to #1254.
Now we derive the id from the actual cover image filename,
which we preserve rather than using "cover-image."
|
|
Process: Fix minor typo in pipeProcess' docs
|
|
Org reader: support Pandocs citation extension
|
|
Citations are defined via the "normal citation" syntax used in markdown,
with the sole difference that newlines are not allowed between "[...]".
This is for consistency, as org-mode generally disallows newlines
between square brackets.
The extension is turned on by default and can be turned off via the
default syntax-extension mechanism, i.e. by specifying "org-citation" as
the input format.
Move `citeKey` from Readers.Markdown into Parsing
The function can be used by other readers, so it is made accessible for
all parsers.
|
|
The function can be used by other readers, so it is made accessible for
all parsers.
|
