aboutsummaryrefslogtreecommitdiff
AgeCommit message (Collapse)AuthorFilesLines
2018-08-10Avoid non-exhaustive pattern match.John MacFarlane1-11/+5
2018-08-10Avoid non-exhaustive pattern match.John MacFarlane1-7/+8
2018-08-10Avoid non-exhaustive pattern match.John MacFarlane1-3/+1
2018-08-10Avoid non-exhaustive pattern matches.John MacFarlane1-4/+6
2018-08-10Avoid non-exhaustive pattern match.John MacFarlane1-11/+12
2018-08-10Avoid non-exhaustive pattern match.John MacFarlane1-10/+12
2018-08-10Avoid non-exhaustive pattern match.John MacFarlane1-2/+3
2018-08-10Avoid a non-exhaustive pattern match.John MacFarlane1-3/+2
2018-08-08HTML writer: Don't prefix epub: attributes with data-.John MacFarlane1-0/+1
2018-08-07Bump to 2.2.3.2, update man page, changelog.John MacFarlane4-3/+13
2018-08-07Markdown reader: Properly handle boolean values in YAML metadata.John MacFarlane2-1/+62
This fixes a regression in 2.2.3, which cause boolean values to be parsed as MetaInlines instead of MetaBool. Note also an undocumented (but desirable) change in 2.2.3: numbers are now parsed as MetaInlines rather than MetaString. Closes #4819.
2018-08-06Bump to 2.2.3.1, update man page and changelog.John MacFarlane4-3/+9
2018-08-06Fix parsing of embedded mappings in YAML metadata.John MacFarlane2-24/+32
This fixes a regression in 2.2.3 which caused embedded mappings (e.g. mappings in sequences) not to work in YAML metadata. Closes #4817.
2018-08-05Update README.md.John MacFarlane1-6/+6
2018-08-05Bump to 2.2.3, update changelog and man page.John MacFarlane4-17/+110
2018-08-05RST reader: improve parsing of inline interpreted text roles.John MacFarlane6-19/+86
* Use a Span with class "title-reference" for the default title-reference role. * Use B.text to split up contents into Spaces, SoftBreaks, and Strs for title-reference. * Use Code with class "interpreted-text" instead of Span and Str for unknown roles. (The RST writer has also been modified to round-trip this properly.) * Disallow blank lines in interpreted text. * Backslash-escape now works in interpreted text. * Backticks followed by alphanumerics no longer end interpreted text. Closes #4811.
2018-08-05Added test case for #4669 to repository.John MacFarlane1-0/+29
2018-08-04Describe required space as breaking change (#4808)Kirill Müller1-0/+5
2018-08-03RST writer: allow images to be directly nested within links, closes #4810 ↵Francesco Occhipinti1-0/+2
(#4814)
2018-08-03Better error message on `-t pdf -o out.pdf` (#4815)Mauro Bieg1-5/+9
closes #1155 (again)
2018-08-01RST writer: use `titleblock` instead of `title` variable for title blockFrancesco Occhipinti3-6/+15
Closes #4803 After this commit use `$titleblock$` in order to get what was contained in `$title$` before, that is a title and subtitle rendered according to the official rST method: http://docutils.sourceforge.net/docs/user/rst/quickstart.html#document-title-subtitle. from With this commit, the `$title$` and `$subtitle$` metadata are available and they simply carry the metadata values. This opens up more possibilities in templates.
2018-08-01fix broken link for cabal-install (#4806)ChanHoHo1-1/+1
2018-07-31MANUAL: Add beamer info for slide backgrounds (#4802)John Muccigrosso1-12/+16
2018-07-30Markdown reader: allow unquoted numbers, booleans as YAML mapping keys.John MacFarlane1-26/+28
Previously in 2.2.2 you could not do --- 0: bar ... but only --- '0': bar ... With this change, both forms work.
2018-07-30Use YAML.decode rather than YAML.decodeStrict.John MacFarlane1-1/+1
(Minor)
2018-07-30DocBook reader: metadata handling improvements.John MacFarlane2-39/+29
Now we properly parse title and subtitle elements that are direct children of book and article (as well as children of bookinfo, articleinfo, or info). We also now use the "subtitle" metadata field for subtitles, rather than tacking the subtitle on to the title.
2018-07-30Lua Utils module: add function blocks_to_inlines (#4799)Albert Krewinkel5-3/+69
Exposes a function converting which flattenes a list of blocks into a list of inlines. An example use case would be the conversion of Note elements into other inlines.
2018-07-30Remove duplicate instruction (#4796)Josh1-1/+0
2018-07-24RST reader: remove support for nested inlines.danse3-23/+26
RST does not allow nested emphasis, links, or other inline constructs. Closes #4581, double parsing of links with URLs as link text. This supersedes the earlier fix for #4581 in 6419819b46c0d69c7024ba8aa4a6381cb311341c. Fixes #4561, a bug parsing with URLs inside emphasis. Closes #4792.
2018-07-24MediaWiki writer: Avoid extra blank line in tables with empty cells.John MacFarlane2-0/+19
Note that the old output is semantically identical, but the new output looks better. Closes #4794.
2018-07-23Org reader: fix parsers relying on parseFromStringAlbert Krewinkel2-4/+14
Emphasis was not parsed when it followed directly after some block types (e.g., lists). The org reader uses a wrapper for the `parseFromString` function to handle org-specific state. The last position of a character allowed before emphasis was reset incorrectly in this wrapper. Emphasized text was not recognized when placed directly behind a block which the reader parses using `parseFromString`. Fixes: #4784
2018-07-21MANUAL: Clarify when csquotes is used in LaTeX writer.John MacFarlane1-3/+4
Closes #4514.
2018-07-21MANUAL: Added commonmark to list of output formats where...John MacFarlane1-1/+1
`raw_tex` has an effect. See #4527.
2018-07-21RST reader: fix double-link bug.John MacFarlane2-1/+14
Link labels containing raw URLs were parsed as autolinks, but links within links are not allowed. Closes #4581.
2018-07-21Moved some beamer code in default.latex template.John MacFarlane1-37/+35
This change allows beamer themes to change the template and font (as Metropolis does). Closes #4450.
2018-07-19Make sure pandoc-windows-*.msi are deleted as intermediate files.John MacFarlane1-0/+2
2018-07-19Update man page, changelog, authors.John MacFarlane4-12/+33
2018-07-19Fix for bug in parsing `\include` in markdown.John MacFarlane2-1/+32
Starting in 2.2.2, everything after an `\input` (or `\include`) in a markdown file would be parsed as raw LaTeX. This commit fixes the issue and adds a regression test. Closes #4781.
2018-07-19rawLaTeXBlock: never retokenize macroDef.John MacFarlane1-1/+1
2018-07-19MANUAL: clarify gfm vs markdown_github (#4783)Mauro Bieg1-7/+7
2018-07-18Add missing rollingLinks option to revealjs template (#4778)Igor Khorlo1-0/+4
Fix (add) the missing option 'rollingLinks' in reveal.js template.
2018-07-18Use 'keywords' instead of 'tags' in YAML metadata example.John MacFarlane1-1/+1
Unlike `tags`, `keywords` is used in some of the writers and default templates. Closes #4779.
2018-07-18Bump version to 2.2.2.1.John MacFarlane1-1/+1
2018-07-18Fix regression finding templates in user data directory.John MacFarlane1-3/+1
Under version 2.2.1 and prior pandoc found latex templates in the templates directory under the data directory, but this no longer works in 2.2.2. MANUAL says: "If the template is not found, pandoc will search for it in the templates subdirectory of the user data directory (see `--data-dir`)." This commit fixes the regression, which stems from 07bce91. Closes #4777.
2018-07-15Update AUTHORS.John MacFarlane1-0/+5
2018-07-15Minor cabal file changes.John MacFarlane1-2/+2
Requested by 'stack upload.' Different format for minimum cabal version. Use of autogen-modules.
2018-07-15linux/Dockerfile: simplify and use new ghc 8.4.3.John MacFarlane1-35/+3
2018-07-15Update changelog.John MacFarlane1-1/+18
2018-07-15Make markdown and github writers respect the `emoji` extension.John MacFarlane3-0/+37
2018-07-15Wrap emojis in span nodes (#4759)Anders Waldenborg6-21/+56
Text.Pandoc.Emoji now exports `emojiToInline`, which returns a Span inline containing the emoji character and some attributes with metadata (class `emoji`, attribute `data-emoji` with emoji name). Previously, emojis (as supported in Markdown and CommonMark readers, e.g ":smile:") were simply translated into the corresponding unicode code point. By wrapping them in Span nodes, we make it possible to do special handling such as giving them a special font in HTML output. We also open up the possibility of treating them differently when the `--ascii` option is selected (though that is not part of this commit). Closes #4743.