Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
The only possible effect will be with rst fragments that
begin with an rst title block, which will now cause the
header transform.
|
|
|
|
|
|
|
|
|
|
Better to keep reader and writer options separate.
|
|
This is the beginning of a larger transition that will make
Options, not ParserState, the parameter of the read functions.
(Options will also be used in writers, in place of WriterOptions.)
Next step is to remove strict, replacing it with granular
tests for different extensions.
|
|
|
|
A Writer can be a PureStringWriter, an IOStringWriter, or
an IOByteStringWriter. ALL writers are now in the 'writers'
list, including the binary writers and fb2 writer. Code simplified
at end of pandoc.hs.
|
|
|
|
These now take WriterOptions and Pandoc only.
The extra parameters for epub stylesheet, epub fonts,
reference Docx, and reference ODT have been removed, since
these things are now in WriterOptions.
Note: breaking API change!
|
|
|
|
|
|
|
|
Closes #568.
|
|
This means that duplicate variables specified later on the command
line take precedence.
It also allows the default `-slidy-url` to be overridden even when
`--self-contained` is used (provided the `-V` comes after
`--self-contained`. Previously this could not be done. Note
that when `--self-contained` is used, the `slidy-url` variable is
set to `slidy` so that local copies are used.
|
|
|
|
Prior to base 4.5 (and perhaps earlier - check), filepaths and command
line arguments were treated as unencoded lists of bytes, not unicode
strings, so we had to work around that by encoding and decoding
them. This commit adds CPP checks for base 4.5 that disable the
encoding/decoding.
Fixes a bug with multilingual filenames when pandoc was compiled
with ghc 7.4. Closes #540.
|
|
|
|
Depend on h-k 0.5.0.6.
|
|
This is useful for those who want to use advanced OpenType features
with xelatex/lualatex.
|
|
|
|
Such keys get the value `true`.
|
|
|
|
|
|
Now it is implemented in pandoc.hs, not in the HTML writer.
|
|
Remove old 'deEntities' from pandoc.hs.
|
|
|
|
* The new reader is more robust, accurate, and extensible.
It is still quite incomplete, but it should be easier
now to add features.
* Text.Pandoc.Parsing: Added withRaw combinator.
* Markdown reader: do escapedChar before raw latex inline.
Otherwise we capture commands like \{.
* Fixed latex citation tests for new citeproc.
* Handle \include{} commands in latex.
This is done in pandoc.hs, not the (pure) latex reader.
But the reader exports the needed function, handleIncludes.
* Moved err and warn from pandoc.hs to Shared.
* Fixed tests - raw tex should sometimes have trailing space.
* Updated lhs-test for highlighting-kate changes.
|
|
|
|
* This can be repeated for multiple fonts.
* Added parameter for fonts to embed to writeEPUB.
* Added ttf, otf to Mime types in Text.Pandoc.MIME.
|
|
Removed `--beamer` option; instead, use `beamer` as output format.
There is no longer a `pdf` output format; instead, pandoc tries
to produce a pdf if the output file has a `.pdf` extension.
(The output format can be latex -- the default for pdf output,
latex+lhs, or beamer.)
This seems more consistent with the way pandoc currently works
(e.g. we have an `html5` output format, not an `--html5` option).
|
|
|
|
|
|
This allows users to select a slide level below the first
header level with content.
Note that content under sections above the slide level will not appear
in slides (either in beamer or in HTML slide shows).
This is primarily useful for creating documents that can be made
into both slides and handouts (which contain additional content
outside the slides).
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
* New module `Text.Pandoc.Docx`.
* New output format `docx`.
* Added reference.docx.
* New option `--reference-docx`.
The writer includes support for highlighted code blocks
and math (which is converted from TeX to OMML using
texmath's new OMML module).
|
|
* `---` is always em-dash, `--` is always en-dash.
* pandoc no longer tries to guess when `-` should be en-dash.
* A new option, `--old-dashes`, is provided for legacy documents.
Rationale: The rules for en-dash are too complex and
language-dependent for a guesser to work reliably. This
change gives users greater control. The alternative of
using unicode isn't very good, since unicode em- and en-
dashes are barely distinguishable in a monospace font.
|