summaryrefslogtreecommitdiff
path: root/src/Text/Pandoc/Writers
Commit message (Collapse)AuthorAge
* Revert "EPUB writer: stylesheet changes. Closes #2040."John MacFarlane2015-05-09
| | | | | | | | | | This reverts commit 1c2951dfd9ee72e5270cb974a06098adb9178f89. See #2040. The semantics was too squishy. `--css` takes a URL, but for EPUB we need files that we can read. I prefer keeping the old system for now, with `--epub-stylesheet`.
* EPUB writer: stylesheet changes. Closes #2040.John MacFarlane2015-05-08
| | | | | | | | | | | | * Allow `--css` to be used to specify stylesheets. * Deprecated `--epub-stylesheet` and made it a synoynym of `--css`. * If a code block with class "css" is given as contents of the `stylesheet` metadata field, use its literal code as contents of the epub stylesheet. Otherwise, treat it as a filename and read the file. * Note: `--css` and `stylesheet` in metadata are not compatible. `stylesheet` takes precedence.
* Deal with deprecation warning in Custom.John MacFarlane2015-05-05
|
* LaTeX writer: Add a `\label` in `\hyperdef` for Div, Span.John MacFarlane2015-05-02
| | | | Otherwise links don't work.
* EPUB writer: Use plain writer for metadata dc: fields.John MacFarlane2015-05-01
| | | | | | | This gives better results when we have, e.g. multiple paragraphs. Note that tags aren't allowed in these fields. Closes #2121.
* EPUB writer: Remove linear=no from cover itemref.John MacFarlane2015-04-26
| | | | Closes #1609.
* Merge pull request #2112 from lierdakil/issue2101John MacFarlane2015-04-26
|\ | | | | Custom Writer: Set foreign encoding to UTF-8
| * Custom Writer: Set foreign encoding to UTF-8Nikolay Yakimov2015-04-26
| | | | | | | | | | | | | | Closes #2101, #1634 Also factored out ByteString, since it's only used as an intermediate representation.
* | Updated copyright notices to -2015. Closes #2111.John MacFarlane2015-04-26
|/
* Custom writer: use UTF-8 aware bytestring conversion.John MacFarlane2015-04-21
| | | | This might help with #2101.
* Markdown writer: improved escaping.John MacFarlane2015-04-18
| | | | | | | | `<` should not be escaped as `\<`, for compatibility with original Markdown. We now escape `<` and `>` with entities. Also, we now backslash-escape square brackets. Closes #2086.
* Merge branch 'latex-tightlist' of https://github.com/jlduran/pandoc into ↵John MacFarlane2015-04-17
|\ | | | | | | | | | | | | jlduran-latex-tightlist Conflicts: data/templates
| * LaTeX writer: Use a declaration for tight listsJose Luis Duran2014-09-01
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Currently, pandoc has hard-coded the following in order to make tight lists in LaTeX: ```hs text "\\itemsep1pt\\parskip0pt\\parsep0pt" ``` Which is fine, but does not allow customizations. For example, the `memoir` class already has a `\tightlist` declaration for this purpose: ```tex \newcommand{\tightlist}{% \setlength{\itemsep}{0pt}\setlength{\parskip}{0pt}} ``` I'm proposing to use a similar solution: ```diff @@ In Writers/LaTeX.hs: -then text "\\itemsep1pt\\parskip0pt\\parsep0pt" +then text "\\tightlist" @@ In templates/default.latex: +\newcommand{\tightlist}{% + \setlength{\itemsep}{1pt}\setlength{\parskip}{0pt}\setlength{\parsep}{0pt}} ``` This allows us to customize the tightness to our needs. Backward Compatibility If a person is using a custom LaTeX template (not based upon the `memoir` class), the `\tightlist` declaration must be added.
* | Merge pull request #2079 from lierdakil/rst-normalize-headingsJohn MacFarlane2015-04-17
|\ \ | | | | | | RST Writer: Normalize headings to sequential levels
| * | RST Writer: treat headings in block quotes, etc as rubricsNikolay Yakimov2015-04-16
| | |
| * | RST Writer: Normalize headings to sequential levelsNikolay Yakimov2015-04-13
| | | | | | | | | | | | This is pretty much required by docutils.
* | | Docx Writer: Take TOC title from toc-title metadata fieldNikolay Yakimov2015-04-14
|/ /
* | Fixed toc depth in RST writer.John MacFarlane2015-04-12
| | | | | | | | | | | | Previously the depth was being rendered as a floating point number with a decimal point. Thanks to Nick Yakimov for noticing this.
* | ODT Writer: Figure captionsNikolay Yakimov2015-04-12
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Works pretty much the same as Word writer. Following styles are used for figures: Figure -- for figure with empty caption FigureWithCaption (based on Figure) -- for figure with caption FigureCaption (based on Caption) -- for figure captions Also, TableCaption (based on Caption) is used for table captions. We need FigureWithCaption to set keepWithNext, in order to keep caption with figure.
* | RST writer: better handling of raw latex inline.John MacFarlane2015-04-07
| | | | | | | | | | | | | | We use `` :raw-latex:`...` `` and add a definition for this role to the template. Closes #1961.
* | EPUB writer: Take TOC title from toc-title metadata field.John MacFarlane2015-04-02
| |
* | Added "noProof" to docx syntax highlighting SourceCode style.John MacFarlane2015-04-01
| |
* | Merge pull request #2035 from lierdakil/issue2031John MacFarlane2015-03-30
|\ \ | | | | | | Docx Writer/Reference: Add keepNext to objects w/ captions
| * | Docx Writer: Add a style to figure imagesNikolay Yakimov2015-03-29
| | | | | | | | | | | | | | | | | | | | | Figures with empty captions use style "Figure" Figures with nonempty captions use style "Figure with Caption", which is based on "Figure", and additionally has keepNext set.
* | | Added CommonMark writer.John MacFarlane2015-03-29
| | | | | | | | | | | | | | | Added `Text.Pandoc.Writers.CommonMark`, exporting `writeCommonMark`.
* | | Merge pull request #2038 from lierdakil/docx-hyphen-settingsJohn MacFarlane2015-03-29
|\ \ \ | | | | | | | | Docx Writer: Copy hyphenation settings from reference.docx
| * | | Docx Writer: Copy hyphenation settings from reference.docxNikolay Yakimov2015-03-29
| |/ /
* | | Merge pull request #2037 from lierdakil/issue458John MacFarlane2015-03-29
|\ \ \ | | | | | | | | Docx Writer: support for --toc option
| * | | Docx Writer: Place toc after abstract, rather than beforeNikolay Yakimov2015-03-29
| | | |
| * | | Docx Writer: Initial support for --toc option (issue #458)Nikolay Yakimov2015-03-29
| |/ / | | | | | | | | | Creates a "dirty" TOC at the beginning of document, before abstract
* / / Docx Writer: Filter out illegal XML charactersMatthew Pickering2015-03-29
|/ / | | | | | | Fixes #1992
* | Markdown writer: fixes for GHC 7.10.John MacFarlane2015-03-19
| |
* | Merge pull request #1968 from lierdakil/issue1607John MacFarlane2015-03-16
|\ \ | | | | | | Fixes for multiple docx writer style bugs.
| * | Docx Writer: set firstRow information in tablesNikolay Yakimov2015-03-08
| | |
| * | Code cleanupNikolay Yakimov2015-03-03
| | |
| * | Started moving StyleMap out of writer codeNikolay Yakimov2015-03-01
| | |
| * | Update Docx writer for 1cb601d reference.docxNikolay Yakimov2015-03-01
| | |
| * | Comment out unused functions to make CI happyNikolay Yakimov2015-02-24
| | |
| * | Treat some ambiguous styles as custom for nowNikolay Yakimov2015-02-24
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * Author * Abstract * Compact * ImageCaption * TableCaption * DefinitionTerm * Definition * FirstParagraph
| * | Do not lookup custom stylesNikolay Yakimov2015-02-23
| | |
| * | Also skip SourceCode style if existsNikolay Yakimov2015-02-23
| | |
| * | If --no-highlight is set, remove *Tok styles.Nikolay Yakimov2015-02-22
| | |
| * | Prototype fix for #1872Nikolay Yakimov2015-02-22
| | |
| * | Initial stab at more involved fix for #1607Nikolay Yakimov2015-02-21
| | | | | | | | | | | | | | | | | | 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.
* | | AsciiDoc writer: avoid wrapping after list marker.John MacFarlane2015-03-15
| | | | | | | | | | | | Closes #1858.
* | | AsciiDoc writer: insert some needed blank lines.John MacFarlane2015-03-15
| | | | | | | | | | | | Closes #1860.
* | | Merge pull request #1989 from zudov/shortcut_ref_link_prJohn MacFarlane2015-03-15
|\ \ \ | | | | | | | | Support shortcut reference links in markdown writer
| * | | Support shortcut reference links in markdown writerKonstantin Zudov2015-03-10
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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`).
* | | | Really fix #1394.John MacFarlane2015-03-14
| | | | | | | | | | | | | | | | | | | | | | | | 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.
* | | | Fixed pipe tables -- headerless tables are not allowed.John MacFarlane2015-03-07
|/ / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.