aboutsummaryrefslogtreecommitdiff
AgeCommit message (Collapse)AuthorFilesLines
2021-06-11Update issue templatesJohn MacFarlane2-0/+58
2021-06-11Fancier issue templates.John MacFarlane4-11/+76
Based on Doom Emacs's templates.
2021-06-10Bump to 2.14.0.2, update chaneglog and manual.John MacFarlane4-14/+122
2021-06-10Fix MediaBag regressions.John MacFarlane4-48/+47
With the 2.14 release `--extract-media` stopped working as before; there could be mismatches between the paths in the rendered document and the extracted media. This patch makes several changes (while keeping the same API). The `mediaPath` in 2.14 was always constructed from the SHA1 hash of the media contents. Now, we preserve the original path unless it's an absolute path or contains `..` segments (in that case we use a path based on the SHA1 hash of the contents). When constructing a path from the SHA1 hash, we always use the original extension, if there is one. Otherwise we look up an appropriate extension for the mime type. `mediaDirectory` and `mediaItems` now use the `mediaPath`, rather than the mediabag key, for the first component of the tuple. This makes more sense, I think, and fits with the documentation of these functions; eventually, though, we should rework the API so that `mediaItems` returns both the keys and the MediaItems. Rewriting of source paths in `extractMedia` has been fixed. `fillMediaBag` has been modified so that it doesn't modify image paths (that was part of the problem in #7345). We now do path normalization (e.g. `\` separators on Windows) only in writing the media; the paths are left unchanged in the image links (sensibly, since they might be URLs and not file paths). These changes should restore the original behavior from before 2.14. Closes #7345.
2021-06-10T.P.MIME, extensionFromMimeType: add a few special cases.John MacFarlane1-0/+10
When we do a reverse lookup in the MIME table, we just get the last match, so when the same mime type is associated with several different extensions, we sometimes got weird results, e.g. `.vs` for `text/plain`. These special cases help us get the most standard extensions for mime types like `text/plain`.
2021-06-10Docx writer: fix handling of empty table headersAlbert Krewinkel1-2/+2
A table header which does not contain any cells is now treated as an empty header. Fixes: #7369
2021-06-10Lua utils: fix handling of table headers in `from_simple_table`Albert Krewinkel1-1/+1
Passing an empty list of header cells now results in an empty table header. Fixes: #7369
2021-06-08Citeproc: avoid duplicate classes and attributes on refs div.John MacFarlane1-2/+2
2021-06-08using-the-pandoc-api.md: switch from String to TextAlbert Krewinkel1-9/+9
Fixed examples that would no longer compile with current library versions, as the API now uses Text instead of String in most places.
2021-06-07Mention GladTeX for EPUB exportSebastian Humenda2-7/+13
This updates the manual and the web site about the GladTeX usage.
2021-06-07CONTRIBUTING.md: update modules overviewAlbert Krewinkel1-5/+6
2021-06-05LaTeX writer: Fix regression in table header position.John MacFarlane6-18/+79
In recent versions the table headers were no longer bottom-aligned (if more than one line). This patch fixes that by using minipages for table headers in non-simple tables. Closes #7347.
2021-06-05CommonMark writer: do not use simple class for fenced-divsJan Tojnar1-3/+6
In https://github.com/jgm/pandoc/pull/7242, we introduced a simple attribute style for for code blocks and fenced divs with a single class but turns out the CommonMark extension does not support it for fenced divs. https://github.com/jgm/commonmark-hs/blob/master/commonmark-extensions/test/fenced_divs.md
2021-06-05CommonMark writer: do not throw away attributes when Ext_attributes is enabledJan Tojnar2-13/+17
Ext_attributes covers at least the following: - Ext_fenced_code_attributes - Ext_header_attributes - Ext_inline_code_attributes - Ext_link_attributes
2021-06-05Markdown writer: re-use functions from InlineJan Tojnar2-29/+4
Instead of duplicating linkAttributes and attrsToMarkdown, let’s just use those from the Inline module.
2021-06-05Require citeproc 0.4.0.1.John MacFarlane2-2/+2
This fixes a bug which led to doubled "et al." in some (rare) circumstances.
2021-06-05DocBook reader: Add support for danger elementJan Tojnar1-1/+2
Added in DocBook 5.2: - https://github.com/docbook/docbook/pull/64 - https://tdg.docbook.org/tdg/5.2/danger.html
2021-06-05DocBook writer: Remove non-existent admonitionsJan Tojnar2-8/+7
attention, error and hint are actually just reStructuredText specific. danger was too until introduced in DocBook 5.2: https://github.com/docbook/docbook/issues/55
2021-06-03T.P.Class.IO: normalise path in writeMedia.John MacFarlane1-3/+2
This ensures that we get `\` separators on Windows.
2021-06-02MANUAL: more details and a useful link for YAML syntax.John MacFarlane1-0/+7
2021-06-02Text.Pandoc.PDF: only print relevant part of environment on `--verbose`.John MacFarlane1-2/+14
2021-06-02Fix regression in 2.14 for generation of PDFs with SVGs.John MacFarlane1-1/+2
Closes #7344.
2021-06-01HTML writer: Don't omit width attribute on div.John MacFarlane1-3/+4
Closes #7342.
2021-06-01Markdown reader: fix pipe table regression in 2.11.4.John MacFarlane2-11/+3
Previously pipe tables with empty headers (that is, a header line with all empty cells) would be rendered as headerless tables. This broke in 2.11.4. The fix here is to produce an AST with an empty table head when a pipe table has all empty header cells. Closes #7343.
2021-06-01LaTeX reader: don't allow optional * on symbol control sequences.John MacFarlane2-2/+10
Generally we allow optional starred variants of LaTeX commands (since many allow them, and if we don't accept these explicitly, ignoring the star usually gives acceptable results). But we don't want to do this for `\(*\)` and similar cases. Closes #7340.
2021-05-31Move tarball diet item from 2.14.0.1 to 2.14 in changelog.John MacFarlane1-2/+2
This was actually part of the 2.14 release.
2021-05-31Bump to 2.14.0.1; update changelog and man page.John MacFarlane4-3/+24
2021-05-31Fix regression with commonmark/gfm yaml metdata block parsing.John MacFarlane2-5/+16
A regression in 2.14 led to the document body being omitted after YAML metadata in some cases. This is now fixed. Closes #7339.
2021-05-31Small tweak to 2.14 changelog.John MacFarlane1-2/+4
2021-05-30HTML reader: fix column width regression.John MacFarlane1-1/+1
Column widths specified with a style attribute were off by a factor of 100 in 2.14. Closes #7334.
2021-05-30Have LoadedResource use relative paths.John MacFarlane2-5/+5
The immediate reason for this is to allow the test output of #3752 to work on both windows and linux.
2021-05-30Docx writer: fix regression on captions.John MacFarlane1-1/+3
The "Table Caption" style was no longer getting applied. (It was overwritten by "Compact.") Closes #7328.
2021-05-29Use commonmark-extensions 0.2.1.2John MacFarlane2-2/+2
2021-05-29Markdown reader: in rebasePaths, check for both Windows and PosixJohn MacFarlane1-4/+5
absolute paths. Previously Windows pandoc was treating `/foo/bar.jpg` as non-absolute.
2021-05-29In rebasePath, check for absolute paths two ways.John MacFarlane1-1/+4
isAbsolute from FilePath doesn't return True on Windows for paths beginning with `/`, so we check that separately.
2021-05-29Fix test #3752 (1) for Windows.John MacFarlane1-1/+1
2021-05-29Further test image size reductions.John MacFarlane2-1/+1
2021-05-29Replace biblatex-exmaples.bib with shorter averroes.bib in tests.John MacFarlane4-1676/+97
2021-05-29Further test image size reductions.John MacFarlane2-0/+0
2021-05-29Reduce size of image in fb2 image test.John MacFarlane1-0/+0
2021-05-29Reduce size of cover image in test epub.John MacFarlane2-1/+1
2021-05-29Modify pptx tests to take a whole lot less space.John MacFarlane22-0/+0
- Replace a 300K image in the reference pptx with a 2K one. - Updated all the *_templated.pptx files based on the new reference pptx. - These changes should reduce the size of the tarball by roughly 7 MB! See haskell/hackage-server#935
2021-05-28Add nuew to AUTHORS.John MacFarlane1-0/+1
2021-05-28Date on changelog.John MacFarlane1-1/+1
2021-05-28Update AUTHORS and fixed some typos in changelog.John MacFarlane2-25/+36
2021-05-28Update manual.John MacFarlane2-5/+44
2021-05-28Update changelog.John MacFarlane1-7/+72
2021-05-28Support `rebase_relative_paths` for commonmark based formats.John MacFarlane3-1/+20
(Including `gfm`.)
2021-05-28Use latest commonmark.John MacFarlane2-3/+6
2021-05-28Docx reader: Support new table features.Emily Bourke15-68/+487
* Column spans * Row spans - The spec says that if the `val` attribute is ommitted, its value should be assumed to be `continue`, and that its values are restricted to {`restart`, `continue`}. If the value has any other value, I think it seems reasonable to default it to `continue`. It might cause problems if the spec is extended in the future by adding a third possible value, in which case this would probably give incorrect behaviour, and wouldn't error. * Allow multiple header rows * Include table description in simple caption - The table description element is like alt text for a table (along with the table caption element). It seems like we should include this somewhere, but I’m not 100% sure how – I’m pairing it with the simple caption for the moment. (Should it maybe go in the block caption instead?) * Detect table captions - Check for caption paragraph style /and/ either the simple or complex table field. This means the caption detection fails for captions which don’t contain a field, as in an example doc I added as a test. However, I think it’s better to be too conservative: a missed table caption will still show up as a paragraph next to the table, whereas if I incorrectly classify something else as a table caption it could cause havoc by pairing it up with a table it’s not at all related to, or dropping it entirely. * Update tests and add new ones Partially fixes: #6316