| Commit message (Collapse) | Author | Age |
|
|
|
| |
Previously strikeout highlighted code caused an error.
|
|\
| |
| | |
Make strNormalize go bottomUp.
|
|/
|
|
| |
This was how it used to be before it was folded into blockNormalize.
|
|\
| |
| | |
Docx reader: Fixes to block Normalization
|
| |
| |
| |
| |
| |
| | |
`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 previously allowed spaces at the beginning of a paragraph.
|
| |
| |
| |
| | |
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.
|
|/
|
|
|
| |
This change to highlighting-kate means that PHP fragments no longer
need to start with `<?php`. Closes #1271.
|
|\
| |
| | |
Add ReaderOptions to the docx tests
|
|/
|
|
|
| |
This will allow for testing different media embedding (in addition to
any other applicable options.)
|
|
|
|
| |
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.
|
| |
|
|\ |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| | |
Note this makes use of input and output files in the tests/ dir.
|
| |
| |
| |
| |
| | |
Changes also include generalising the types of reader allowed. The
mechanism now mimics the more general output mechanism.
|
| |
| |
| |
| |
| | |
Note there is a build warning for unused `makeImagesSelfContained`
function, since there isn't yet a command-line-option to make use of it.
|
| |
| |
| |
| | |
This introduces Text.Pandoc.DocX, and its exported `readDocX` function.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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.)
|