Age | Commit message (Collapse) | Author | Files | Lines |
|
rST parser now supports:
- All built-in rST roles
- New role definition
- Role inheritance
Issues/TODO:
- Silently ignores illegal fields on roles
- Silently drops class annotations for roles
- Only supports :format: fields with a single format for :raw: roles,
requires a change to Text.Pandoc.Definition.Format to support multiple
formats.
- Allows direct use of :raw: role, rST only allows indirect (i.e.,
inherited use of :raw:).
|
|
Closes #1122.
|
|
|
|
Closes #1106.
|
|
Closes #1104.
|
|
Remove parens enclosing a single element.
|
|
|
|
A consequence of this change is that the backtick form will be
preferred in general if both are enabled. I think that is good,
as it is much more widespread than the tilde form.
Closes #1084.
|
|
"$" is now a special character.
|
|
[ci skip]
|
|
E.g.
- foo
- bar
- baz
Previously a spurious blank line was included before the last item.
Closes #1050.
|
|
This is reported to be necessary to avoid an error from recent
versions of Libre Office when files contain more than one image.
Closes #1069.
Thanks to wmanley for reporting and diagnosing the problem.
|
|
|
|
In some of the Wikipedia versions the local version of 'File' is used (for example 'Archivo' in Spanish)
|
|
Instead of adding 'nunumber' every time we place a figure...
Closes #1067.
|
|
Closes #1066.
|
|
|
|
|
|
This allows better control of formatting, since the `<a>`
tags have a distinguishing class.
Closes #1049.
|
|
Deprecate readTeXMath, and use readTeXMath' in all the writers.
Require texmath >= 0.6.5.
|
|
This fix puts braces around a term that contains an internal
link, to avoid problems with square brackets.
|
|
Allows test suite to work with cabal sandboxes.
Previously we hard-coded the build directory.
|
|
Otherwise we get problems when converting to markdown.
Closes #1027.
|
|
|
|
Not ???.
Reason: Less surprising, especially for people using @ as
in twitter.
|
|
|
|
|
|
Closes #937.
|
|
This produces automatic header identifiers, unless `auto_identifiers`
extension is disabled.
Closes #967.
|
|
This will give automatic unique identifiers, unless
`-auto_identifiers` is specified.
|
|
|
|
|
|
Write id for code block to label attr in latex when listing is used
|
|
|
|
Going forward we'll use pandoc-citeproc, as an external filter.
The `--bibliography`, `--csl`, and `--citation-abbreviation` fields
have been removed. Instead one must include `bibliography`, `csl`,
or `csl-abbrevs` fields in the document's YAML metadata. The filter
can then be used as follows:
pandoc --filter pandoc-citeproc
The `Text.Pandoc.Biblio` module has been removed. Henceforth,
`Text.CSL.Pandoc` from pandoc-citations can be used by library users.
The Markdown and LaTeX readers now longer format bibliographies and
citations. That must be done using `processCites` or `processCites'`
from Text.CSL.Pandoc.
All bibliography-related fields have been removed from `ReaderOptions`
and `WriterOptions`: `writerBiblioFiles`, `readerReferences`,
`readerCitationStyle`.
API change.
|
|
|
|
The code:
~~~{#test}
asdf
~~~
gets compiled to html:
<pre id="test">
asdf
</pre>
So it is possible to link to the identifier `test`
But this doesn't happen on latex
When using the listings package (`--listings`) it is possible to set the
identifier using the `label=test` property:
\begin{lstlisting}[label=id]
hi
\end{lstlisting}
And this is exactly what this patch is doing.
Modified LaTeX Reader/Writer and added tests for this.
|
|
|
|
* Add ??? as fallback text for non-resolved citations.
* Biblio: Put references (including a header at the end of
the document, if one exists) inside a Div with class "references".
This gives some control over styling of references, and allows
scripts to manipulate them.
* Markdown writer: Print markdown citation codes, and disable
printing of references, if `citations` extension is enabled.
NOTE: It would be good to improve what citeproc-hs does for
a nonexistent key.
|
|
|
|
|
|
|
|
Textile, MediaWiki, Markdown, Org, RST will emit raw HTML div tags for divs.
Otherwise Div and Span are "transparent" block containers.
|
|
|
|
When the original document had text containing //, this was previously
included, unchanged, in the dokuwiki output, and this interacted badly
with later, intended, formating text.
|
|
Done because I noticed that in the Autolinks section of writer.dokuwiki, the URL in inlined code was getting auto-linked, when it wasn't supposed to.
This also meant that any inline code examples that had text that looked like dokuwiki syntax could break the formatting of later text.
|
|
writer (#386)
|
|
|
|
I've found some incorrect behaviours with the dokuwiki output, for which
extra test cases will be needed - that aren't covered by the standard
pandoc test input files.
|
|
|