| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
Notes can't contain figures in LaTeX, so we fake it to avoid
an error. Closes #1053.
|
|
When the `hard_line_breaks` option was specified, pandoc would
produce a spurious line break after a tight list item. This
patch solves the problem. Closes #1137.
|
|
in exif header. Closes #1358.
|
|
We let a `</table>` tag close an open `<tr>` or `<td>`.
Closes #1167.
|
|
|
|
Previously strikeout highlighted code caused an error.
|
|
This was how it used to be before it was folded into blockNormalize.
|
|
`normalize` from Text.Pandoc.Shared is more general. In tests, though,
it more than doubles the run time. `strNormalize` does less, but it does
what we need. This comment is added for future maintainability.
|
|
Previously DefinitionList had been left out of `blockNormalize`. Now it
is included.
|
|
Use a function `stripSpaces`, instead of recursion. Makes it a bit
easier to read and mantain, and simplify normalizing DefinitionList,
which was left out the first time.
|
|
`blockNormalize` previously forgot to account for the case in which a
Header's inlines did not start with a space.
|
|
Otherwise we get overly tall lines when there are empty
table cells and the other cells are compact.
Closes #1353.
|
|
Test case:
```
<table border="1">
<colgroup>
<col> </col>
<col></col>
</colgroup>
<tbody>
<tr>
<td>X</td>
<td>Y</td>
</tr>
<tr>
<td>1</td>
<td>2</td>
</tr>
</tbody>
</table>
```
|
|
Parse literal tabs in docx
|
|
This will help take care of spaces introduced at the beginning of strings.
|
|
|
|
|
|
Some images seem to have tag type of 256, which was causing
a runtime error.
|
|
Avoids interpretation as list.
|
|
|
|
|
|
|
|
|
|
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.
|
|
Changes also include generalising the types of reader allowed. The
mechanism now mimics the more general output mechanism.
|
|
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.
|
