summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAge
* Muse reader: do not consume whitespace while looking for closing end tagAlexander Krotov2018-03-02
| | | | Fix for a bug caught by round-trip test.
* Org writer: fix a typo s/prettyfy/prettify/Alexander Krotov2018-03-02
|
* Muse reader: convert alphabetical list markers to decimal in round-trip testAlexander Krotov2018-03-02
| | | | | | Alphabetical lists are an addition of Text::Amuse. They are not present in Emacs Muse and can be ambiguous when list starts with "i.", "c." etc.
* Docx reader: Handle nested sdt tags.Jesse Rosenthal2018-02-28
| | | | | | | Previously we had only unwrapped one level of sdt tags. Now we recurse if we find them. Closes: #4415
* Muse reader: add test for verse tag with one empty lineAlexander Krotov2018-02-28
|
* Muse writer: change verse markupAlexander Krotov2018-02-28
| | | | Use "> " instead of <verse> tag
* Muse writer: remove empty strings during inline normalizationAlexander Krotov2018-02-28
|
* Muse reader: allow <quote> and other tags to be indentedAlexander Krotov2018-02-28
|
* Update tagsoup to 0.14.6Alexander Krotov2018-02-28
|
* Set fixed minor version for hsluaAlbert Krewinkel2018-02-27
| | | | | The ToLuaStack instance for Set is orphaned. The PVP requires the minor version to be fixed in this case.
* Powerpoint writer: use `trim` from SharedJesse Rosenthal2018-02-27
| | | | Instead of writing my own.
* Powerpoint writer: Use table stylesJesse Rosenthal2018-02-27
| | | | | | This will use the default table style in the reference-doc file. As a result they will be easier when using in a template, and match the color scheme.
* Powerpoint writer: add test for table and list syntaxJesse Rosenthal2018-02-27
| | | | | | | These were never added when the tests were first created. Output files checked in MS PowerPoint 2013 (Windows 10, VBox). No corruption, and output as expected.
* Powerpoint writer: Remove empty slidesJesse Rosenthal2018-02-27
| | | | | | | | | | | | Make sure there are no empty slides in the pptx output. Because of the way that slides were split, these could be accidentally produced by comments after images. When animations are added, there will be a way to add an empty slide with either incremental lists or pauses. Test outputs checked with MS PowerPoint (Office 2013, Windows 10, VBox). Both files have expected output and are not corrupted.
* Update tagsoup to 0.14.5Alexander Krotov2018-02-27
|
* Update tagsoup to 0.14.4Alexander Krotov2018-02-27
| | | | Fixes #4282
* LaTeX reader: make --trace work.John MacFarlane2018-02-26
|
* Org reader tests: move citation tests to separate moduleAlbert Krewinkel2018-02-26
|
* Allow exceptions 0.9.John MacFarlane2018-02-26
|
* Removed ghc-prof-options.John MacFarlane2018-02-25
| | | | | | As of cabal 1.24, sensible defaults are used. See https://www.haskell.org/cabal/users-guide/developing-packages.html#pkg-field-ghc-prof-options.
* doc/org.md: Add Org-mode documentation (very first draft)Albert Krewinkel2018-02-25
|
* Tests/Lua: fix tests on windowsAlbert Krewinkel2018-02-25
|
* doc/lua-filters.md: document global vars set for filtersAlbert Krewinkel2018-02-24
|
* Lua: register script name in global variableAlbert Krewinkel2018-02-24
| | | | | | | | The name of the Lua script which is executed is made available in the global Lua variable `PANDOC_SCRIPT_FILE`, both for Lua filters and custom writers. Closes: #4393
* Muse reader: allow single colon in definition list termAlexander Krotov2018-02-24
|
* Docx reader: code cleanup.Jesse Rosenthal2018-02-23
| | | | Make the code in `runStyleToTransform` a bit more consistent.
* Docx reader: simplify custom-style reading code.Jesse Rosenthal2018-02-23
|
* Docx reader: Don't look up dependant run styles if +styles is enabled.Jesse Rosenthal2018-02-23
| | | | | | It makes more sense not to interpret -- otherwise using the original document as the reference-doc would produce two of everything: the interpreted version and the uninterpreted style version.
* Muse writer: don't indent nested definition listsAlexander Krotov2018-02-23
|
* Docx writer: trim trailing whitespace.Jesse Rosenthal2018-02-23
|
* Docx test: adjust test for fix of buglaptop1\Andrew2018-02-23
| | | | | | | | This commit adjusts the test cases for the Docx writer after the fix of #3930. - Adjusted test cases with inline images. The inline images now have the correct sizing, title and description. - Modified the test case to include an image multiple times with different sizing each time. - Tested on Windows 8.1 with Word 2007 (12.0.6705.5000) The files are not corrupted and display exactly what is expected.
* Docx writer: fix #3930laptop1\Andrew2018-02-23
| | | | | | Fixes an issuue regarding image sizing if the same image is included more than once. Previously, a record was kept, indexed by image source, which would include the XML for that image. For every image element in the document, this record was checked, and if the image was the same as previous examples, the same XML would be included twice. The information in this XML incudes the image description, title text, and size on the page, thus all images from the same source would always be sized the same, and have the same description. This commit fixes this by generating unique XML every time, but keeping the image ID and path if it is the same image.
* Muse reader: improve verse parsingAlexander Krotov2018-02-23
| | | | | Now verse marked up with ">" (in contrast to <verse> tag) can be placed inside lists.
* Export improved sepBy1 from Text.Pandoc.ParsingAlexander Krotov2018-02-23
|
* Require aeson-pretty 0.8.5. Closes #4394.John MacFarlane2018-02-22
| | | | `confTrailingNewline` is introduced in this version.
* MANUAL.txt: Document incremental and nonincremental divs.Jesse Rosenthal2018-02-22
| | | | | Blockquoted lists are still described, but fenced divs are presented in preference.
* Presentations: Use divs to set incremental/non-incrementalJesse Rosenthal2018-02-22
| | | | | | | | | | | | | | | | | | | | | | | Currently, html and beamer presentations use a list-inside-blockquote convention for setting incremental and all-at-once presentation of lists (or reversing the command-line default). This allows the user to set this on a per-case basis with divs, named `incremental` and `nonincremental` respectively, as in: ::: incremental - snap - crackle - pop ::: Note that the former list-inside-blockquote convention still works so as not to break any existing presentations. Closes: #4381
* Docx reader: Move pandoc inline styling inside custom-style spanJesse Rosenthal2018-02-22
| | | | | | | | Previously Emph, Strong, etc were outside the custom-style span. This moves them inside in order to make it easier to write filters that act on the formatting in these contents. Tests and MANUAL example are changed to match.
* Docx reader: Avoid repeated spans in custom styles.Jesse Rosenthal2018-02-22
| | | | | | The previous commit had a bug where custom-style spans would be read with every recurrsion. This fixes that, and changes the example given in the manual.
* MANUAL: add documentation on custom styles.Jesse Rosenthal2018-02-22
| | | | | | Discuss workflow of using input document as reference.docx. We also split the "Custom styles" section into two parts: input and output.
* Docx reader tests: test custom style extension.Jesse Rosenthal2018-02-22
|
* Docx reader: read custom stylesJesse Rosenthal2018-02-22
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This will read all paragraph and character classes as divs and spans, respectively. Dependent styles will still be resolved, but will be wrapped with appropriate style tags. It is controlled by the `+styles` extension (`-f docx+styles`). This can be used in conjunction with the `custom-style` feature in the docx writer for a pandoc-docx editing workflow. Users can convert from an input docx, reading the custom-styles, and then use that same input docx file as a reference-doc for producing an output docx file. Styles will be maintained across the conversion, even if pandoc doesn't understand them. Without the extension: $ pandoc test/docx/custom-style-reference.docx -f docx -t markdown This is some text. This is text with an *emphasized* text style. And this is text with a **strengthened** text style. > Here is a styled paragraph that inherits from Block Text. With the extension: $ pandoc test/docx/custom-style-reference.docx -f docx+styles -t markdown ::: {custom-style="FirstParagraph"} This is some text. ::: ::: {custom-style="BodyText"} This is text with an *[[emphasized]{custom-style="Emphatic"}]{custom-style="Emphatic"}* text style. And this is text with a **[[strengthened]{custom-style="Strengthened"}]{custom-style="Strengthened"}** text style. ::: ::: {custom-style="MyBlockStyle"} Closes: #1843
* Extensions: Add Ext_stylesJesse Rosenthal2018-02-22
| | | | | | This will be used in the docx reader (defaulting to off) to read pargraph and character styles not understood by pandoc (as divs and spans, respectively).
* LaTeX writer: Put hypertarget inside figure environment.John MacFarlane2018-02-21
| | | | | | | | | Previously it surrounded the figure. This works around a problem with the endfloat package and makes pandoc's output compatible with it. Closes #4388.
* LaTeX writer: Fix image height with percentage.John MacFarlane2018-02-21
| | | | | | | This previously caused the image to be resized to a percentage of textwidth, rather than textheight. Closes #4389.
* Org reader: allow changing emphasis syntaxAlbert Krewinkel2018-02-21
| | | | | | | | | | | | | | | | The characters allowed before and after emphasis can be configured via `#+pandoc-emphasis-pre` and `#+pandoc-emphasis-post`, respectively. This allows to change which strings are recognized as emphasized text on a per-document or even per-paragraph basis. The allowed characters must be given as (Haskell) string. #+pandoc-emphasis-pre: "-\t ('\"{" #+pandoc-emphasis-post: "-\t\n .,:!?;'\")}[" If the argument cannot be read as a string, the default value is restored. Closes: #4378
* Muse reader: replace setState with updateState where possibleAlexander Krotov2018-02-21
|
* MANUAL.txt: fix typo.Jesse Rosenthal2018-02-20
|
* MANUAL.txt: A bit of clarification on speaker notes.Jesse Rosenthal2018-02-20
| | | | Make it clear that pressing `s` is just for reveal.js.
* MANUAL.txt: Add instructions for using pptx reference-docsJesse Rosenthal2018-02-20
|