Conversion between markup formats https://git.pashev.ru/pandoc/atom?h=master 2021-03-15T17:37:35Z 2021-03-15T17:37:35Z John MacFarlane jgm@berkeley.edu 2021-03-15T17:37:35Z urn:sha1:24191a2a278c0dec30bacd66b78cbb8cc8d91324 2021-02-17T00:55:20Z John MacFarlane jgm@berkeley.edu 2021-02-15T06:29:21Z urn:sha1:967e7f5fb990b29de48b37be1db40fb149a8cf55 ..and add new definitions isomorphic to xml-light's, but with Text instead of String. This allows us to keep most of the code in existing readers that use xml-light, but avoid lots of unnecessary allocation. We also add versions of the functions from xml-light's Text.XML.Light.Output and Text.XML.Light.Proc that operate on our modified XML types, and functions that convert xml-light types to our types (since some of our dependencies, like texmath, use xml-light). Update golden tests for docx and pptx. OOXML test: Use `showContent` instead of `ppContent` in `displayDiff`. Docx: Do a manual traversal to unwrap sdt and smartTag. This is faster, and needed to pass the tests. Benchmarks: A = prior to 8ca191604dcd13af27c11d2da225da646ebce6fc (Feb 8) B = as of 8ca191604dcd13af27c11d2da225da646ebce6fc (Feb 8) C = this commit | Reader | A | B | C | | ------- | ----- | ------ | ----- | | docbook | 18 ms | 12 ms | 10 ms | | opml | 65 ms | 62 ms | 35 ms | | jats | 15 ms | 11 ms | 9 ms | | docx | 72 ms | 69 ms | 44 ms | | odt | 78 ms | 41 ms | 28 ms | | epub | 64 ms | 61 ms | 56 ms | | fb2 | 14 ms | 5 ms | 4 ms | 2020-11-07T18:38:03Z Albert Krewinkel albert@zeitkraut.de 2020-11-07T18:38:03Z urn:sha1:527346cc7e2bc874092be2f6793001860e10a719 * Remove unused LANGUAGE pragmata * Apply HLint suggestions * Configure HLint to ignore some warnings * Lint code when committing to master 2020-10-14T20:26:51Z Albert Krewinkel albert@zeitkraut.de 2020-10-14T19:32:51Z urn:sha1:90af1384433b1f537fa51f1018539d4d401ec73b Typos reported by https://fossies.org/linux/test/pandoc-master.tar.gz/codespell.html See: #6738 2020-09-13T14:48:14Z Christian Despres 50160106+despresc@users.noreply.github.com 2020-09-13T14:48:14Z urn:sha1:cae155b095e5182cc1b342b21f7430e40afe7ba8 * Fix hlint suggestions, update hlint.yaml Most suggestions were redundant brackets. Some required LambdaCase. The .hlint.yaml file had a small typo, and didn't ignore camelCase suggestions in certain modules. 2020-03-15T16:45:44Z Albert Krewinkel albert@zeitkraut.de 2020-03-15T16:45:44Z urn:sha1:a5fa55969f1b4afc0ca3e38be50b69c65d43a460 * Use implicit Prelude The previous behavior was introduced as a fix for #4464. It seems that this change alone did not fix the issue, and `stack ghci` and `cabal repl` only work with GHC 8.4.1 or newer, as no custom Prelude is loaded for these versions. Given this, it seems cleaner to revert to the implicit Prelude. * PandocMonad: remove outdated check for base version Only base versions 4.9 and later are supported, the check for `MIN_VERSION_base(4,8,0)` is therefore unnecessary. * Always use custom prelude Previously, the custom prelude was used only with older GHC versions, as a workaround for problems with ghci. The ghci problems are resolved by replacing package `base` with `base-noprelude`, allowing for consistent use of the custom prelude across all GHC versions. 2020-02-07T17:08:22Z John MacFarlane jgm@berkeley.edu 2020-02-07T16:32:47Z urn:sha1:4c3db9273fc8e92c2c23d4455a6ab178472be06d 2020-02-07T09:17:24Z Albert Krewinkel albert@zeitkraut.de 2020-02-07T09:15:57Z urn:sha1:6cd77d4c638012be63d66882403804aa28feb6ed All warnings are either fixed or, if more appropriate, HLint is configured to ignore them. HLint suggestions remain. * Ignore "Use camelCase" warnings in Lua and legacy code * Fix or ignore remaining HLint warnings * Remove redundant brackets * Remove redundant `return`s * Remove redundant as-pattern * Fuse mapM_/map * Use `.` to shorten code * Remove redundant `fmap` * Remove unused LANGUAGE pragmas * Hoist `not` in Text.Pandoc.App * Use fewer imports for `Text.DocTemplates` * Remove redundant `do`s * Remove redundant `$`s * Jira reader: remove unnecessary parentheses 2020-02-06T01:22:53Z Joseph C. Sible josephcsible@users.noreply.github.com 2020-02-06T01:22:53Z urn:sha1:30c8980883921e0672c36db2ad77ab31c147190c There's no need to use `catMaybes`, `uncurry`, `bool`, etc., just to get elements where the second element of a tuple is True. 2020-02-05T06:38:49Z Joseph C. Sible josephcsible@users.noreply.github.com 2020-02-05T06:38:49Z urn:sha1:b018028ee9f733d5c6907e4ef362794e75b8c38c Data.Bool already provides a bool function identical to this one.