aboutsummaryrefslogtreecommitdiff
path: root/test
AgeCommit message (Collapse)AuthorFilesLines
2018-02-25Tests/Lua: fix tests on windowsAlbert Krewinkel1-1/+1
2018-02-24Lua: register script name in global variableAlbert Krewinkel2-0/+9
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
2018-02-24Muse reader: allow single colon in definition list termAlexander Krotov1-0/+3
2018-02-23Docx reader: Don't look up dependant run styles if +styles is enabled.Jesse Rosenthal1-1/+1
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.
2018-02-23Muse writer: don't indent nested definition listsAlexander Krotov1-2/+2
2018-02-23Docx test: adjust test for fix of buglaptop1\Andrew3-5/+8
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.
2018-02-23Muse reader: improve verse parsingAlexander Krotov1-0/+11
Now verse marked up with ">" (in contrast to <verse> tag) can be placed inside lists.
2018-02-22Docx reader: Move pandoc inline styling inside custom-style spanJesse Rosenthal1-1/+1
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.
2018-02-22Docx reader: Avoid repeated spans in custom styles.Jesse Rosenthal1-1/+1
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.
2018-02-22Docx reader tests: test custom style extension.Jesse Rosenthal3-0/+22
2018-02-21Org reader: allow changing emphasis syntaxAlbert Krewinkel1-1/+19
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
2018-02-19Powerpoint writer tests: Test everything with template as wellJesse Rosenthal11-48/+72
Modify the PowerPoint tests to run all the tests with template (--reference-doc) as well. Because there are so many interlocking pieces, bugs can pop up in weird places when using templates, since it changes how the writer builds its output file. For example, I recently discovered a bug in which speaker notes worked fine and templating worked fine elsewhere, but templating with speaker notes produced a file that would crash MS PowerPoint. That particular bug was fixed, but this will forces us to check for that with each new change.
2018-02-19Powerpoint writer: Update.golden tests.Jesse Rosenthal9-0/+0
Checked with Office 2013. No corruption and output as expected.
2018-02-19Move manyUntil to Text.Pandoc.Parsing and use it in Txt2Tags readerAlexander Krotov1-1/+4
2018-02-18Powerpoint writer: Add tests for speaker notes.Jesse Rosenthal3-0/+22
2018-02-18Powerpoint writer: update golden test filesJesse Rosenthal8-0/+0
Since the template changed, some small elements of these test files changed as well. All of these were checked with Powerpoint 2013 on Windows 10 (VirtualBox). All had expected outcomes and no corruption.
2018-02-17LaTeX reader: Fixed comments inside citations. Closes #4374.John MacFarlane1-0/+7
2018-02-16TEI writer: Use 'xml:id', not 'id' attribute.John MacFarlane1-31/+31
Closes #4371.
2018-02-16Muse reader: prioritize lists with roman numerals over alphabetical listsAlexander Krotov1-0/+12
This is to make sure "i." starts a roman numbered list, instead of a list with letter "i" (followed by "j", "k", ...").
2018-02-15Docx reader: Pick table width from the longest row or headerdanse3-0/+17
This change is intended to preserve as much of the table content as possible Closes #4360
2018-02-15Muse reader: fix directive parsingAlexander Krotov1-0/+15
This fixes bugs introduced in commit 4bfab8f04c105f111d8d4e1c3ed7f7b5c75dbd19.
2018-02-15Muse writer: use unicode quotes for quoted textAlexander Krotov2-12/+12
2018-02-13AsciiDoc writer: do not output implicit heading IDsAlexander Krotov1-31/+0
Convert to asciidoc-auto_identifiers for old behaviour. Fixes #4363
2018-02-13Muse reader: parse definition lists with multiple descriptionsAlexander Krotov1-7/+20
2018-02-12Muse reader: refactor to avoid reparsingAlexander Krotov1-1/+40
Lists are parsed in linear instead of exponential time now. Contents of block tags, such as <quote>, is parsed directly, without storing it in a string and parsing with parseFromString. Fixed a bug: headers did not terminate lists.
2018-02-12Muse reader: paragraph indentation does not indicate nested quoteAlexander Krotov1-0/+6
Muse allows indentation to indicate quotation or alignment, but only on the top level, not within a <quote> or list. This patch also simplifies the code by removing museInQuote and museInList fields from the state structure. Headers and indented paragraphs are attempted to be parsed only at the topmost level, instead of aborting parsing with guards.
2018-02-11Muse reader: test empty quote tagAlexander Krotov1-0/+5
2018-02-11Muse reader: require that block tags are on separate linesAlexander Krotov1-19/+26
Text::Amuse already explicitly requires it anyway. Supporting block tags on the same line as contents makes it hard to combine closing tag parsers with indentation parsers. Being able to combine parsers is required for no-reparsing refactoring of Muse reader.
2018-02-08Updated rst writer test for template change.John MacFarlane1-4/+0
2018-02-05Muse reader: test that two blank lines after verse can separate list itemsAlexander Krotov1-0/+21
Unlike paragraph and <quote> tag parsers, verse parser consumes newline. For this reason only three or more blank lines can separate list items.
2018-02-05Muse reader: test that lists can be separated with two blanklines after ↵Alexander Krotov1-0/+27
blockquote Existing tests only checked this for paragraphs.
2018-02-03Muse writer: write image width specified in percent in Text::Amuse modeAlexander Krotov1-0/+3
2018-01-30Muse writer: don't wrap displayMath into <verse>Alexander Krotov2-2/+2
<verse> is a block tag and displayMath is an inline element. Writing <verse> around displayMath could result in nested <verse> tags.
2018-01-29Muse writer: escape nonbreaking space ("~~")Alexander Krotov1-0/+1
2018-01-28Muse reader: fix parsing of trailing whitespaceAlexander Krotov1-0/+6
Newline after whitespace now results in softbreak instead of space.
2018-01-27Docx writer tests: correct test name.Jesse Rosenthal1-1/+1
2018-01-27Docx writer tests: Add tests for custom stylesJesse Rosenthal4-0/+10
2018-01-27Docx writer tests: Use new golden frameworkJesse Rosenthal27-127/+120
These are based off the reader tests, with some removed (where the reader output was identical, based on different docx inputs). There are still more to be added. In particular, tests for custom-styles need to be added. All golden docx files have been checked in MS Word 2013 (windows). There is no corruption. There is questionable output in the `tables` test: the three tables seemed to be joined. This will be addressed in a future commit, and the golden docx file will be changed.
2018-01-25Tests: Abstract powerpoint tests out to OOXML tests.Jesse Rosenthal2-175/+188
There is very little pptx-specific in these tests, so we abstract out the basic testing function so it can be used for docx as well. This should allow us to catch some errors in the docx writer that slipped by the roundtrip testing.
2018-01-25ConTeXt writer: new section syntax and --section-divs (#4295)Henri Menke4-39/+66
Fixes #2609. This PR introduces the new-style section headings: `\section[my-header]{My Header}` -> `\section[title={My Header},reference={my-header}]`. On top of this, the ConTeXt writer now supports the `--section-divs` option to write sections in the fenced style, with `\startsection` and `\stopsection`.
2018-01-24Muse reader: fix matching of closing inline tagsAlexander Krotov1-0/+3
2018-01-23Powerpoint writer tests: hlint cleanups.Jesse Rosenthal1-14/+12
2018-01-23ConTeXt writer: xtables: correct wrong usage of captionHenri Menke2-4/+4
2018-01-22Powerpoint writer tests: add tests for two-column layout and imagesJesse Rosenthal5-0/+24
Powerpoint output checked in MS PowerPoint 2013 (Windows)
2018-01-22Powerpoint writer: Add further testsJesse Rosenthal5-0/+17
Tests added for: - table of contents - endnotes - endnotes with table of contents Powerpoint output checked in MS PowerPoint 2013 (Windows)
2018-01-22Powerpoint writer tests: simplify updating functionJesse Rosenthal1-7/+1
We had previously re-read the native file and converted it to Powerpoint. But we have already done that in constructing the test archive. So now we just convert the archive back to a bytestring and write it to disk.
2018-01-22Powerpoint tests: Convert to golden testsJesse Rosenthal1-136/+147
This will allow us to rebuild the pptx files in the test dir more easily if we make a change in the writer.
2018-01-22Muse writer: join code with different attributes during normalizationAlexander Krotov1-0/+1
2018-01-22Muse writer: indent lists inside DivAlexander Krotov1-1/+3
2018-01-21Powerpoint writer tests: New test framework for pptx.Jesse Rosenthal6-157/+196
Previously we had tested certain properties of the output PowerPoint slides. Corruption, though, comes as the result of a numebr of interrelated issues in the output pptx archive. This is a new approach, which compares the output of the Powerpoint writer with files that we know to (a) not be corrupt, and (b) to show the desired output behavior (details below). This commit introduces three tests using the new framework. More will follow. The test procedure: given a native file and a pptx file, we generate a pptx archive from the native file, and then test: 1. Whether the same files are in the two archives 2. Whether each of the contained xml files is the same. (We skip time entries in `docProps/core.xml`, since these are derived from IO. We just check to make sure that they're there in the same way in both files.) 3. Whether each of the media files is the same. Note that steps 2 and 3, though they compare multiple files, are one test each, since the number of files depends on the input file (if there is a failure, it will only report the first failed file comparison in the test failure).