aboutsummaryrefslogtreecommitdiff
AgeCommit message (Collapse)AuthorFilesLines
2015-03-22Factor out "returnState" into Parsing moduleMatthew Pickering3-16/+7
2015-03-22HLint changesMatthew Pickering1-82/+76
2015-03-22Remove F Monad from Markdown readerMatthew Pickering1-313/+306
2015-03-22Generalise signature of addWarningMatthew Pickering1-1/+1
2015-03-22Add check to see whether in a footnote to ParserState (to avoid circular ↵Matthew Pickering1-2/+4
footnotes)
2015-03-22Remove F monad from ParsingMatthew Pickering2-26/+3
2015-03-22Changed parseWithWarnings to the more general returnWarnings parser transformerMatthew Pickering2-7/+6
2015-03-22Remove F monad from Org Reader.Matthew Pickering1-239/+227
2015-03-22Added generalize function which can be used to lift specialised parsers.Matthew Pickering1-0/+4
Monad m => Parsec s st a -> Parsec T s st m a
2015-03-19Markdown writer: fixes for GHC 7.10.John MacFarlane1-3/+3
2015-03-19Bumped upper bounds for filepath, QuickCheck.John MacFarlane1-9/+9
Bumped lower bounds for highlighting-kate, texmath.
2015-03-19Merge pull request #2013 from ShabbyX/masterJohn MacFarlane2-11/+16
Derive from Data and Typeable for libpandoc
2015-03-19Derive from Data and Typeable for libpandocShahbaz Youssefi2-11/+16
This commit derives a few types from Data and Typeable used by libpandoc. Requires corresponding pull-request for Highlighting-Kate: https://github.com/jgm/highlighting-kate/pull/64 Signed-off-by: Shahbaz Youssefi <ShabbyX@gmail.com>
2015-03-17Fixed a compiler warning.John MacFarlane1-1/+1
2015-03-17Added CommonMark reader using cmark (libcmark bindings).John MacFarlane5-18/+150
- Added commonmark as an input format. - Added `Text.Pandoc.Readers.CommonMark.readCommonMark`. - For now, we use the markdown writer to generate benchmark text for the CommonMark reader. We can change this when we get a writer.
2015-03-17Bump criterion version bound.John MacFarlane1-1/+1
2015-03-16Merge pull request #1968 from lierdakil/issue1607John MacFarlane16-100/+401
Fixes for multiple docx writer style bugs.
2015-03-16Merge pull request #2008 from tomleese/fix-github-phrasingJohn MacFarlane4-5/+5
Replace occurrences of 'Github' with 'GitHub'
2015-03-16Replace occurrences of 'Github' with 'GitHub'Tom Leese4-5/+5
The website is called 'GitHub' afterall.
2015-03-15AsciiDoc writer: avoid wrapping after list marker.John MacFarlane2-3/+3
Closes #1858.
2015-03-15AsciiDoc writer: insert some needed blank lines.John MacFarlane2-1/+6
Closes #1860.
2015-03-15Moved and rewrote documentation for `shortcut_reference_links` ext.John MacFarlane1-7/+11
2015-03-15Merge pull request #1989 from zudov/shortcut_ref_link_prJohn MacFarlane5-31/+158
Support shortcut reference links in markdown writer
2015-03-14Really fix #1394.John MacFarlane1-5/+6
This closes #1394, which actually wasn't fixed by the earlier commit. This ensures that lists in speaker notes don't add "fragment" classes, which can cause additional keypresses to be needed to advance a slide.
2015-03-14Properly gobble spaces after \\.John MacFarlane1-10/+12
Closes #2007.
2015-03-14LaTeX reader: allow block content in \title{}.John MacFarlane1-1/+3
Closes #2001.
2015-03-10Support shortcut reference links in markdown writerKonstantin Zudov5-31/+158
Issue #1977 Most markdown processors support the [shortcut format] for reference links. Pandoc's markdown reader parsed this shortcuts unoptionally. Pandoc's markdown writer (with --reference-links option) never shortcutted links. This commit adds an extension `shortcut_reference_links`. The extension is enabled by default for those markdown flavors that support reading shortcut reference links, namely: - pandoc - strict pandoc - github flavoured - PHPmarkdown If extension is enabled, reader parses the shortcuts in the same way as it preveously did. Otherwise it would parse them as normal text. If extension is enabled, writer outputs shortcut reference links unless doing so would cause problems (see test cases in `tests/Tests/Writers/Markdown.hs`).
2015-03-09Merge pull request #2000 from bosmacs/org-smartJohn MacFarlane2-8/+74
Org reader: add support for smart punctuation
2015-03-09Org reader: add support for smart punctuationCraig S. Bosma2-8/+74
2015-03-08Merge pull request #1999 from synsem/latex-reader-tablesJohn MacFarlane2-2/+41
LaTeX reader: minor table parsing improvements
2015-03-08LaTeX reader: allow non-empty colsep in tablesMathias Schenner2-1/+6
The `tabular` environment allows non-empty column separators with the "@{...}" syntax. Previously, pandoc would fail to parse tables if a non-empty colsep was present. With this commit, these separators are still ignored, but the table gets parsed. A test case is included.
2015-03-08LaTeX reader: allow valign argument in tablesMathias Schenner2-1/+4
The `tabular` environment takes an optional parameter for vertical alignment. Previously, pandoc would fail to parse tables if this parameter was present. With this commit, the parameter is still ignored, but the table gets parsed. A test case is included.
2015-03-08LaTeX reader: add some test cases for simple tablesMathias Schenner1-0/+31
2015-03-07LaTeX reader: ignore options in `\lstinline`.John MacFarlane1-1/+1
Rather than raising a parse error. Closes #1997.
2015-03-08Docx Writer: Tables testNikolay Yakimov1-6/+6
2015-03-08Docx Writer: set firstRow information in tablesNikolay Yakimov1-2/+7
2015-03-08Lists testNikolay Yakimov2-4/+21
2015-03-07MediaWiki writer: spaces to underscores in wikilink URL.John MacFarlane1-2/+8
This mimics MediaWiki itself. Closes #1982.
2015-03-07Fixed pipe tables -- headerless tables are not allowed.John MacFarlane4-9/+14
GFM and PHP Markdown Extra pipe tables require headers. Previously pandoc allowed pipe tables not to include headers, and produced headerless pipe tables in Markdown output, but this was based on a misconception about pipe table syntax. This commit fixes this. Note: If you have been using headerless pipe tables, this may cause existing tables to break. Closes #1996.
2015-03-07Merge pull request #1976 from wcaleb/json-help-messageJohn MacFarlane1-5/+7
Clarify JSON input and output in usage message
2015-03-07Merge pull request #1988 from sumitsahrawat/issue-969John MacFarlane4-8/+29
Fix issue #969, #1779 by providing --latex-engine-opt
2015-03-04Fix issue #969, #1779 by providing --latex-engine-optSumit Sahrawat4-8/+29
2015-03-03Initial tests for writerNikolay Yakimov9-0/+145
2015-03-03Code cleanupNikolay Yakimov2-26/+22
2015-03-02Merge pull request #1980 from RyanGlScott/masterMatthew Pickering1-2/+2
Bump blaze-html and blaze-markup upper version bounds
2015-03-01Started moving StyleMap out of writer codeNikolay Yakimov5-67/+165
2015-03-01Update Docx writer for 1cb601d reference.docxNikolay Yakimov1-13/+14
2015-03-01Update reference.docxNikolay Yakimov1-0/+0
Following styles are set as custom: * Author * Abstract * Compact * Image Caption * Table Caption * Definition Term * Definition * First Paragraph Following styles are renamed to correspond with Word Normal.dotm * Block Quote -> Block Text * Link -> Hyperlink * Footnote Ref -> Footnote Reference Following styles added: * Caption Following styles' inheritance changed: * Image Caption <- Caption * Table Caption <- Caption
2015-02-28Bump blaze-html and blaze-markup upper version boundsRyanGlScott1-2/+2
2015-02-27Clarify JSON input and output in usage messageCaleb McDaniel1-5/+7
generated by cgit v1.2.3 (git 2.39.1) at 2024-12-19 12:43:39 +0000