| Commit message (Collapse) | Author | Age |
|---|
| |
|
|
| |
Now doing auto ids for all headers, so tests should reflect that.
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
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.
|
| | |
|
| |
|
|
| |
This previously allowed spaces at the beginning of a paragraph.
|
| |
|
|
|
| |
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.
|
| |
|
|
| |
For consistency with the existing writer.
|
| |\ |
|
| | | |
|
| | |
| |
| |
| | |
Note this makes use of input and output files in the tests/ dir.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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.
|
| | | |
|
| |/
|
|
| |
See #1341.
|
| | |
|
| |\
| |
| | |
Org reader: support for inline LaTeX
|
| | |
| |
| |
| |
| |
| | |
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.
|
| |/
|
|
| |
Closes #1313.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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 reader produced wrong results for block containing non-letter chars
in their parameter arguments. This patch relaxes constraints in that it
allows block header arguments to contain any non-space character (except
for ']' for inline blocks).
Thanks to Xiao Hanyu for noticing this.
|
| |
|
|
|
| |
Blank lines were parsed as two newlines instead of just one.
Thanks to Xiao Hanyu (@xiaohanyu) for pointing this out.
|
| |
|
|
|
|
|
|
|
|
| |
The general form of source block headers
(`#+BEGIN_SRC <language> <switches> <header arguments>`) was not
recognized by the reader. This patch adds support for the above form,
adds header arguments to the block's key-value pairs and marks the block
as a rundoc block if header arguments are present.
This closes #1286.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
| |
Org's inline code blocks take forms like `src_haskell(print "hi")` and
are frequently used to include results from computations called from
within the document. The blocks are read as inline code and marked with
the special class `rundoc-block`. Proper handling and execution of
these blocks is the subject of a separate library, rundoc, which is
work in progress.
This closes #1278.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
| |
* Use isTightList from Shared.
* Adjust writer test, since isTightList is a bit different from what
was used before.
Closes #1250.
|
| |
|
|
| |
Determined by the first block of the first item being Plain.
|
| |
|
|
| |
Includes test.
|
| |
|
|
| |
Closes #1218.
|
| |\
| |
| | |
Org reader: add support for custom link types
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Org allows users to define their own custom link types. E.g., in a
document with a lot of links to Wikipedia articles, one can define a
custom wikipedia link-type via
#+LINK: wp https://en.wikipedia.org/wiki/
This allows to write [[wp:Org_mode][Org-mode]] instead of the
equivallent [[https://en.wikipedia.org/wiki/Org_mode][Org-mode]].
|
| | | |
|
