aboutsummaryrefslogtreecommitdiff
AgeCommit message (Collapse)AuthorFilesLines
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
2015-02-26Org reader: Add test for image linksHans-Peter Deifel1-0/+4
Tests for image links with non-image targets, as introduced in commit 2ca5101.
2015-02-25HTML writer: include raw latex blocks if --mathjax specified.John MacFarlane1-1/+8
Closes #1938.
2015-02-25Markdown writer: don't emit span tags if plain or raw HTML disabled.John MacFarlane1-5/+8
2015-02-25Define isRight since it's only in recent versions of Data.Either.John MacFarlane1-1/+4
2015-02-25Markdown writer: Avoid introducing spurious list items through wrapping.John MacFarlane6-19/+56
Closes #1946.
2015-02-25LaTeX writer: recognize book documentclass if set in metadata.John MacFarlane1-8/+10
This sets `--chapters` implicitly if the documentclass in metadata is a book documentclass. Previously this was done only if a book documentclass was set in a variable. Closes #1971.
2015-02-25Markdown reader: check for tex macros after indented code.John MacFarlane1-3/+3
Closes #1973.
2015-02-25Org reader: Allow image links with non-image targetsHans-Peter Deifel1-1/+1
Org-Mode's own html exporter converts the following org link: [[http://example.com][https://www.haskell.org/static/img/logo.png]] to <a href="http://example.com"> <img src="https://www.haskell.org/static/img/logo.png" alt="logo.png" /> </a> but pandoc generates: <a href="http://example.com"> <a href="https://www.haskell.org/static/img/logo.png" class="uri"> https://www.haskell.org/static/img/logo.png </a> </a> which is useless. With this patch, it generates: <a href="http://example.com"> <img src="https://www.haskell.org/static/img/logo.png" alt="" /> </a>
2015-02-25Docbook writer: don't print empty id attributes.John MacFarlane1-1/+2
Thanks to Steve Horne for reporting.
2015-02-24Remove accidentally added fileNikolay Yakimov1-44/+0
2015-02-24Comment out unused functions to make CI happyNikolay Yakimov1-8/+8
2015-02-24Treat some ambiguous styles as custom for nowNikolay Yakimov2-11/+54
* Author * Abstract * Compact * ImageCaption * TableCaption * DefinitionTerm * Definition * FirstParagraph
2015-02-23Do not lookup custom stylesNikolay Yakimov1-9/+13
2015-02-23Also skip SourceCode style if existsNikolay Yakimov1-9/+12
2015-02-22If --no-highlight is set, remove *Tok styles.Nikolay Yakimov1-2/+10
2015-02-22Prototype fix for #1872Nikolay Yakimov1-4/+7
2015-02-21Initial stab at more involved fix for #1607Nikolay Yakimov1-64/+86
This patch attempts to build a style name -> style id mapping based on styles.xml from reference doc, and changes pStyle and rStyle to accept style name as a parameter instead of styleId. There is a fallback mechanic that removes spaces from style name and returns it as style id, but it likely won't help much. Style names are matched lower-case, since headings and `footnote text` have lowercase names.
2015-02-21Docx reader: Minor cleanup.Jesse Rosenthal1-3/+4
The previous commits had some code repetition. This just makes it a bit easier to read.
2015-02-21Docx reader: add test for verbatim in sub/superscript.Jesse Rosenthal3-0/+12
2015-02-21Docx reader: allow sub/superscript verbatims.Jesse Rosenthal1-1/+6
Verbatim usually shuts off all other run styles, but we don't want it to shut off sub/superscript.
2015-02-20Merge pull request #1964 from mpickering/latexfixMatthew Pickering1-3/+4
LaTeX Writer: Don't use listings in headers
2015-02-20LaTeX Writer: Don't use listings in headersMatthew Pickering1-3/+4
Fixes #1963
2015-02-19Docx reader: Add tests for new list style parsing.Jesse Rosenthal3-0/+10
2015-02-19Docx reader: Allow numbering in the style file.Jesse Rosenthal1-21/+33
This allows inherited styles with numbering (lists). It works like this: 1. check to see if the style has numbering info. 2. if the paragraph has explicit numbering info in the doc that takes precedence. 3. if not we use the numbering info in the style, if it's there. 4. otherwise normal paragraph. We no longer assume it's not a numbering element if it doesn't have an explicit level---we just set that level to 1. (In the style files, the examples I've seen don't have that explicit level.)
generated by cgit v1.2.3 (git 2.39.1) at 2024-11-14 13:27:16 +0000