summaryrefslogtreecommitdiff
path: root/test
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.
* 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
|
* 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.
* Org reader tests: move citation tests to separate moduleAlbert Krewinkel2018-02-26
|
* Tests/Lua: fix tests on windowsAlbert Krewinkel2018-02-25
|
* 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: 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 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.
* Muse reader: improve verse parsingAlexander Krotov2018-02-23
| | | | | Now verse marked up with ">" (in contrast to <verse> tag) can be placed inside lists.
* 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.
* Docx reader tests: test custom style extension.Jesse Rosenthal2018-02-22
|
* 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
* Powerpoint writer tests: Test everything with template as wellJesse Rosenthal2018-02-19
| | | | | | | | | | | | | | 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.
* Powerpoint writer: Update.golden tests.Jesse Rosenthal2018-02-19
| | | | Checked with Office 2013. No corruption and output as expected.
* Move manyUntil to Text.Pandoc.Parsing and use it in Txt2Tags readerAlexander Krotov2018-02-19
|
* Powerpoint writer: Add tests for speaker notes.Jesse Rosenthal2018-02-18
|
* Powerpoint writer: update golden test filesJesse Rosenthal2018-02-18
| | | | | | | | 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.
* LaTeX reader: Fixed comments inside citations. Closes #4374.John MacFarlane2018-02-17
|
* TEI writer: Use 'xml:id', not 'id' attribute.John MacFarlane2018-02-16
| | | | Closes #4371.
* Muse reader: prioritize lists with roman numerals over alphabetical listsAlexander Krotov2018-02-16
| | | | | This is to make sure "i." starts a roman numbered list, instead of a list with letter "i" (followed by "j", "k", ...").
* Docx reader: Pick table width from the longest row or headerdanse2018-02-15
| | | | | | | This change is intended to preserve as much of the table content as possible Closes #4360
* Muse reader: fix directive parsingAlexander Krotov2018-02-15
| | | | This fixes bugs introduced in commit 4bfab8f04c105f111d8d4e1c3ed7f7b5c75dbd19.
* Muse writer: use unicode quotes for quoted textAlexander Krotov2018-02-15
|
* AsciiDoc writer: do not output implicit heading IDsAlexander Krotov2018-02-13
| | | | | | Convert to asciidoc-auto_identifiers for old behaviour. Fixes #4363
* Muse reader: parse definition lists with multiple descriptionsAlexander Krotov2018-02-13
|
* Muse reader: refactor to avoid reparsingAlexander Krotov2018-02-12
| | | | | | | | | 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.
* Muse reader: paragraph indentation does not indicate nested quoteAlexander Krotov2018-02-12
| | | | | | | | | | 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.
* Muse reader: test empty quote tagAlexander Krotov2018-02-11
|
* Muse reader: require that block tags are on separate linesAlexander Krotov2018-02-11
| | | | | | | | 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.
* Updated rst writer test for template change.John MacFarlane2018-02-08
|
* Muse reader: test that two blank lines after verse can separate list itemsAlexander Krotov2018-02-05
| | | | | Unlike paragraph and <quote> tag parsers, verse parser consumes newline. For this reason only three or more blank lines can separate list items.
* Muse reader: test that lists can be separated with two blanklines after ↵Alexander Krotov2018-02-05
| | | | | | blockquote Existing tests only checked this for paragraphs.
* Muse writer: write image width specified in percent in Text::Amuse modeAlexander Krotov2018-02-03
|
* Muse writer: don't wrap displayMath into <verse>Alexander Krotov2018-01-30
| | | | | | <verse> is a block tag and displayMath is an inline element. Writing <verse> around displayMath could result in nested <verse> tags.
* Muse writer: escape nonbreaking space ("~~")Alexander Krotov2018-01-29
|
* Muse reader: fix parsing of trailing whitespaceAlexander Krotov2018-01-28
| | | | | Newline after whitespace now results in softbreak instead of space.
* Docx writer tests: correct test name.Jesse Rosenthal2018-01-27
|
* Docx writer tests: Add tests for custom stylesJesse Rosenthal2018-01-27
|
* Docx writer tests: Use new golden frameworkJesse Rosenthal2018-01-27
| | | | | | | | | | | | | | 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.