| Commit message (Collapse) | Author | Age |
|
|
|
| |
[API change]
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Technically `**@user` is a valid email address, but if we
allow things like this, we get bad results in markdown flavors
that autolink raw email addresses. (See #2940.)
So we exclude a few valid email addresses in order to
avoid these more common bad cases.
Closes #2940.
|
|
|
|
|
|
|
| |
Only works on posix. On Windows, pandoc works as before and
requires an output file parameter for binary formats.
Closes #2677.
|
| |
|
| |
|
|
|
| |
Errors are encountered while reading, not writing
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Added `--list-input-formats`, `--list-output-formats`,
`--list-extensions`, `--list-highlight-languages`,
`--list-highlight-styles`.
Removed list of highlighting languages from `--version`
output.
Removed list of input and output formats from default
`--help` output.
Closes #3173.
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
This is needed because github flavored Markdown has a slightly
different set of escapable symbols than original Markdown;
it includes angle brackets.
Closes #2846.
|
|
|
|
|
|
| |
Closes #3150.
Thanks to @lep for the bug report and patch.
|
|
|
|
|
|
|
|
|
| |
* "Merge" MANUAL.txt into README.md
Pull request #3157 without the automatic building from MANUAL.txt to
README.md
* remove contributors in README.md
|
|\
| |
| | |
Use the markdown version of COPYING from GNU
|
| |
| |
| |
| | |
From https://www.gnu.org/licenses/old-licenses/gpl-2.0.md
|
|\ \
| | |
| | | |
Add command line option allowing to set type of top-level divisions
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The `--chapters` option is replaced with `--top-level-division` which allows
users to specify the type as which top-level headers should be output. Possible
values are `section` (the default), `chapter`, or `part`.
The formats LaTeX, ConTeXt, and Docbook allow `part` as top-level division, TEI
only allows to set the `type` attribute on `div` containers. The writers are
altered to respect this option in a sensible way.
|
| | |
| | |
| | |
| | |
| | | |
TEI doesn't have `<book>` elements but only generic `<divN>` division elements.
Checking the template for a trailing `</book>` is nonsensical.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Add --parts command line argument.
This only effects LaTeX writer, and only for non-beamer output formats.
It changes the output levels so the top level is 'part', the next
'chapter' and then into sections.
|
|\ \ \
| |/ /
|/| | |
[odt] proper formatting of an image with a caption
|
|/ /
| |
| |
| |
| | |
Latex Writer only handles captions if the image's title
is prefixed with 'fig:'.
|
|\ \
| | |
| | | |
Issue 3143: Don't duplicate text for anchors
|
| | |
| | |
| | |
| | |
| | | |
When creating an anchor element we were adding its representation
as well as the original content, leading to text duplication.
|
|\ \ \
| | | |
| | | | |
[odt] images parser
|
| | | | |
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Frame can contain other frames with the text boxes.
This is something that has not been considered before
and meant that the whole construction of images was
broken in those cases. Also the captions were fixed/ignored.
|
| |/ /
| | |
| | |
| | |
| | | |
Highly influenced by the docx support, refactored
some code to avoid DRY.
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
@tarleb this is an interesting one, see the build log in
https://travis-ci.org/jgm/pandoc/jobs/168612017
It only failed on ghc 7.8; I think this must have to do with
the change making Monad a superclass of Applicative, hence
this change.
|
| | | |
|
| | |
| | |
| | |
| | | |
Otherwise we can't set flags.
|
| | | |
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | | |
Disable optimizations.
Make sure we don't change flag on aeson.
|
| | |
| | |
| | |
| | |
| | |
| | | |
The writer no longer adds an extra space before footnote markers.
Fixes: #3162
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
RST requires a space before a footnote marker. We discard those spaces
so that footnotes will be adjacent to the text that comes before
it. This is in line with what rst2latex does. rst2html does not discard
the space, but its html output is different than pandoc's, so this seems
the most semantically correct approach.
Closes #3163
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|