aboutsummaryrefslogtreecommitdiff
AgeCommit message (Collapse)AuthorFilesLines
2019-09-28Replace some more fails with throwErrors.John MacFarlane3-4/+9
2019-09-28Use throwError instead of fail when appropriate.John MacFarlane3-6/+14
2019-09-28Use Prelude.fail to avoid ambiguity with fail from GHC.Base.John MacFarlane17-38/+38
2019-09-28MANUAL.txt: fixed some markdown errors.John MacFarlane1-7/+7
2019-09-28changelog.md: regularize date format.John MacFarlane1-117/+113
2019-09-28Markdownify changelog -> changelog.md.John MacFarlane2-2133/+774
2019-09-28Update changelog.John MacFarlane1-2/+560
2019-09-28Update AUTHORS.mdJohn MacFarlane1-0/+19
2019-09-27Require doctemplates 0.6.1.John MacFarlane1-1/+1
2019-09-27LogMessage: change UnknownExtension -> CouldNotDeduceFormatJohn MacFarlane3-6/+6
2019-09-25Used released pandoc-citeproc 0.16.3.John MacFarlane2-4/+2
2019-09-25Use latest skylighting.John MacFarlane2-2/+4
This addresses #5776 for now, though ultimately we need a new release of regex-pcre-builtin or some other solution.
2019-09-25GitHub ci - back to using ignore-paths.John MacFarlane1-30/+28
paths with ! doesn't seem to do it.
2019-09-25GitHub CI: use paths rather than paths-ignore, use branch to exclude rc/.John MacFarlane1-28/+33
2019-09-24odt: Add external option for native numberingNils Carlson5-7/+96
This adds an external options +native_numbering to the ODT writer enabling enumeration of figures and tables in ODT output.
2019-09-24Use latest texmath.John MacFarlane2-1/+2
2019-09-24LaTeX reader: Add 'tikzcd' to list of special environments.Eigil Rischel1-0/+1
This allows it to be processed by filters, in the same way that one can do for 'tikzpicture'
2019-09-24Allow latest Diff.John MacFarlane1-1/+1
2019-09-24Use pandoc-types 1.17.6.1John MacFarlane1-0/+1
2019-09-23Man writer: suppress non-absolute link URLs.John MacFarlane2-25/+25
Motivation: in a man page there's not much use for relative URLs, which you can't follow. Absolute URLs are still useful. We previously suppressed relative URLs starting with '#' (purely internal links), but it makes sense to go a bit farther. Closes #5770.
2019-09-23ConTeXt unit tests - tweak code property.John MacFarlane1-1/+1
Inline code will never have two consecutive newlines. We get a counterexample in this case https://pipelines.actions.githubusercontent.com/bMXCpShstkkHbFPgw9hBRMWw2w9plyzdVM8r7CRPFBHFvidaAG/5cf52d2d-3804-412d-ae65-4f8c059b0fb7/_apis/pipelines/1/runs/116/signedlogcontent/39?urlExpires=2019-09-23T17%3A38%3A05.8358735Z&urlSigningMethod=HMACV1&urlSignature=Qtd6vnzqgSwXpAkIyp9DJY4Kn7GJzYMR8UDkLR%2FsMQY%3D so for simplicity we just weed out code with newlines.
2019-09-23Fix linux ci.John MacFarlane1-1/+1
2019-09-23pandoc.cabal: repeat ghc-options in all stanzas.John MacFarlane1-4/+63
2019-09-22Fix tests in linux ci (GitHub).John MacFarlane1-1/+2
2019-09-22Update pandoc-citeproc commit.John MacFarlane2-2/+2
2019-09-22Improve test #5753John MacFarlane1-2/+2
2019-09-22Add HsYAML-aeson to stack.yaml.John MacFarlane1-0/+1
2019-09-22Fix cabal command in linux ci.John MacFarlane1-1/+1
2019-09-22Use latest pandoc-citeproc.John MacFarlane2-2/+2
2019-09-22Switch to lts-14 resolver and ghc 8.6.John MacFarlane1-9/+1
2019-09-22Require latest texmath.John MacFarlane1-1/+1
2019-09-22RST reader: Fixed parsing of indented blocks.John MacFarlane2-6/+24
We were requiring consistent indentation, but this isn't required by RST, as long as each nonblank line of the block has *some* indentation. Closes #5753.
2019-09-22[Docx Writer] Re-use Readers.Docx.Parse for StyleMap (#5766)Nikolay Yakimov6-412/+387
* [Docx Parser] Move style-parsing-specific code to a new module * [Docx Writer] Re-use Readers.Docx.Parse.Styles for StyleMap * [Docx Writer] Move Readers.Docx.StyleMap to Writers.Docx.StyleMap It's never used outside of writer code, so it makes more sense to scope it under writers really.
2019-09-22Make `plain` output plainer.John MacFarlane6-96/+64
Previously we used the following Project Gutenberg conventions for plain output: - extra space before and after level 1 and 2 headings - all-caps for strong emphasis `LIKE THIS` - underscores surrounding regular emphasis `_like this_` This commit makes `plain` output plainer. Strong and Emph inlines are rendered without special formatting. Headings are also rendered without special formatting, and with only one blank line following. To restore the former behavior, use `-t plain+gutenberg`. API change: Add `Ext_gutenberg` constructor to `Extension`. See #5741.
2019-09-22Use released doctemplatesJohn MacFarlane2-8/+1
2019-09-22Use HsYAML-0.2.0.0John MacFarlane5-19/+24
Most of this is due to @vijayphoenix (#5704), but it needed some revisions to integrate with current master, and to use the released HsYAML. Closes #5704.
2019-09-22Preliminary GitHub action for release-candidate building.John MacFarlane1-0/+96
2019-09-22ci action: use list of paths to ignore.John MacFarlane1-37/+31
2019-09-21Nightly - removed diagnostics.John MacFarlane1-3/+2
2019-09-21Actions ci - trigger on pull_request as well as push.John MacFarlane1-2/+1
2019-09-21Nightly - another attempt to fix windows.John MacFarlane1-1/+1
2019-09-21Merge branch 'lierdakil-docx-reader-styles'John MacFarlane17-312/+407
2019-09-21Update documentation wrt docx reader custom style namesNikolay Yakimov1-3/+3
2019-09-21[Docx Reader] Update testsNikolay Yakimov6-7/+7
Notice this commit updates lists.docx. The old test file contained references to "ListParagraph" style, which should never leak outside of pandoc, so I'm not sure what that was supposed to test for exactly.
2019-09-21[Docx Writer] Consistently use style names, not style idsNikolay Yakimov1-27/+25
Styles that this change affects: paragraph styles: Author, Abstract, Compact, Figure, Captioned Figure, Image Caption, First Paragraph, Source Code, Table Caption, Definition, Definition Term; character styles: Verbatim Char, token styles (those with names ending in Tok)
2019-09-21[Docx Writer] Code clean-upNikolay Yakimov1-40/+37
Reduce code duplication, remove redundant brackets
2019-09-21[Docx Reader] Use style names, not ids, for assigning semantic meaningNikolay Yakimov8-183/+306
Motivating issues: #5523, #5052, #5074 Style name comparisons are case-insensitive, since those are case-insensitive in Word. w:styleId will be used as style name if w:name is missing (this should only happen for malformed docx and is kept as a fallback to avoid failing altogether on malformed documents) Block quote detection code moved from Docx.Parser to Readers.Docx Code styles, i.e. "Source Code" and "Verbatim Char" now honor style inheritance Docx Reader now honours "Compact" style (used in Pandoc-generated docx). The side-effect is that "Compact" style no longer shows up in docx+styles output. Styles inherited from "Compact" will still show up. Removed obsolete list-item style from divsToKeep. That didn't really do anything for a while now. Add newtypes to differentiate between style names, ids, and different style types (that is, paragraph and character styles) Since docx style names can have spaces in them, and pandoc-markdown classes can't, anywhere when style name is used as a class name, spaces are replaced with ASCII dashes `-`. Get rid of extraneous intermediate types, carrying styleId information. Instead, styleId is saved with other style data. Use RunStyle for inline style definitions only (lacking styleId and styleName); for Character Styles use CharStyle type (which is basicaly RunStyle with styleId and StyleName bolted onto it).
2019-09-21[Docx Reader] Code clean-upNikolay Yakimov2-63/+39
Reduce code duplication, remove redundant brackets, use newtype instead of data where appropriate
2019-09-21Add cabal.project.local to .gitignoreNikolay Yakimov1-0/+1
2019-09-21Nightlies - another attempt to fix windows build.John MacFarlane1-3/+2
generated by cgit v1.2.3 (git 2.39.1) at 2024-12-15 09:42:35 +0000