| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
Previously, when using headers below the slide level, pauses are left
uninterpreted into pauses. In my opinion, unexpected behavior but
intentional looking at the code.
Fixes #2530
|
|
See #2528.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
There are separate relationship (link) files for foot and
endnotes. These had previously been grouped together which led to
links not working correctly in notes. This should finally fix that.
|
|
|
|
|
|
|
|
Some of the unicode characters cause ghc parse errors in older
ghc versions.
|
|
Org reader: Require whitespace around def list markers
|
|
Definition list markers (i.e. double colons `::`) must be surrounded by
whitespace to start a definition item. This rule was not checked
before, resulting in bugs with footnotes and some link types.
Thanks to @conklech for noticing and reporting this issue.
This fixes #2518.
|
|
|
|
Org reader: Fix emphasis rules for smart parsing
|
|
|
|
This is enabled by default in `markdown_github`.
Added `Ext_emoji` to `Extension` in `Text.Pandoc.Options` (API change).
Closes #2523.
|
|
Smart quotes, ellipses, and dashes should behave like normal quotes,
single dashes, and dots with respect to text markup parsing. The parser
state was not updated properly in all cases, which has been fixed.
Thanks to @conklech for reporting this issue.
This fixes #2513.
|
|
Closes jgm/pandoc-citeproc#166.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
This should make it easy to build in different virtual
machines, e.g. 32-bit.
|
|
|
|
- Formatting of some conditionals is adjusted to provide cleaner spacing and
punctuation in generated preamble.
- `$for$` is always provided where the user might want to use multiple options
(does not change existing functionality).
- `hyperref` link rendering revised per discussion in
https://github.com/jgm/pandoc-templates/commit/a84f822c30fde1802131c1c7d69d6ebae4550f72:
- the `hidelinks` option is now effectively the default (and has
been removed as a separate option), rather than setting all links to
black;
- link colours can be enabled more easily (using a slightly darker version
of the old Pandoc defaults) using a new `colorlinks` variable;
- `pdfborder={0 0 0}` is automatically enabled in `hyperref` when
`colorlinks` is enabled, and is now only applied.
- ConTeXt only:
- microtype applied to both regular text and small caps;
- `indenting` variable added;
- renamed `style` to `linkstyle` for consistency (had not yet made it
into the README through my oversight, which I will correct);
- separated `linkcontrastcolor` from `linkcolor`;
- matching LaTeX `hyperref` usage, only disable link styling rather
than providing a specific setting.
|
|
|
|
|
|
By default pandoc downloads all linked media and includes it in the
EPUB container. This can be disabled by setting `data-external`
on the tags linking to media that should not be downloaded.
Example:
<audio controls="1">
<source src="http://www.sixbarsjail.it/tmp/bach_toccata.mp3"
type="audio/mpeg"></source>
</audio>
Closes #2473.
|
|
if `linkcolor`, `urlcolor`, `citecolor`, or `toccolor` is set.
Closes #2508.
|
|
|
|
|
|
Don't use custom prelude for latest ghc.
This is a better approach to making 'stack ghci' and 'cabal repl'
work. Instead of using NoImplicitPrelude, we only use the custom
prelude for older ghc versions. The custom prelude presents a
uniform API that matches the current base version's prelude.
So, when developing (presumably with latest ghc), we don't
use a custom prelude at all and hence have no trouble with ghci.
The custom prelude no longer exports (<>): we now want to
match the base 4.8 prelude behavior.
|
|
This reverts commit c423dbb5a34c2d1195020e0f0ca3aae883d0749b.
|
|
This reverts commit 67cabb2a0d09df17fa4f86b77f66e39a6f036c1d.
|
|
This reverts commit e0c83f74f39ca94437d0b6f823c6f932aa663fe0.
|
|
This is no longer needed with the updates to the template in https://github.com/jgm/pandoc-templates/commit/da139313d2e2ba99f4d31be6ea376dabf8c877ff
|
|
|
|
To satisfy 'cabal check'.
|
|
LaTeX reader: Handle `comment` environment.
|
|
Org reader: fix markup parsing in headers
|
|
This is needed for ghci to work with pandoc, given that we
now use a custom prelude.
Closes #2503.
|
|
Markup as the very first item in a header wasn't recognized. This was
caused by an incorrect parser state: positions at which inline markup
can start need to be marked explicitly by changing the parser state.
This wasn't done for headers. The proper function to update the state
is now called at the beginning of the header parser, fixing this issue.
This fixes #2504.
|
|
The `comment` environment is handled in a similar way to the `verbatim` environment, except that its content is discarded.
|
|
Update LaTeX/ConTeXt variable usage in README.
|
|
Closes #1506.
|
