aboutsummaryrefslogtreecommitdiff
path: root/test/docx
AgeCommit message (Collapse)AuthorFilesLines
2019-09-21[Docx Reader] Update testsNikolay Yakimov6-7/+7
Notice this commit updates lists.docx. The old test file contained references to "ListParagraph" style, which should never leak outside of pandoc, so I'm not sure what that was supposed to test for exactly.
2019-09-21[Docx Reader] Use style names, not ids, for assigning semantic meaningNikolay Yakimov4-0/+10
Motivating issues: #5523, #5052, #5074 Style name comparisons are case-insensitive, since those are case-insensitive in Word. w:styleId will be used as style name if w:name is missing (this should only happen for malformed docx and is kept as a fallback to avoid failing altogether on malformed documents) Block quote detection code moved from Docx.Parser to Readers.Docx Code styles, i.e. "Source Code" and "Verbatim Char" now honor style inheritance Docx Reader now honours "Compact" style (used in Pandoc-generated docx). The side-effect is that "Compact" style no longer shows up in docx+styles output. Styles inherited from "Compact" will still show up. Removed obsolete list-item style from divsToKeep. That didn't really do anything for a while now. Add newtypes to differentiate between style names, ids, and different style types (that is, paragraph and character styles) Since docx style names can have spaces in them, and pandoc-markdown classes can't, anywhere when style name is used as a class name, spaces are replaced with ASCII dashes `-`. Get rid of extraneous intermediate types, carrying styleId information. Instead, styleId is saved with other style data. Use RunStyle for inline style definitions only (lacking styleId and styleName); for Character Styles use CharStyle type (which is basicaly RunStyle with styleId and StyleName bolted onto it).
2019-09-20Preserve built-in styles in DOCX with custom style (#5670)Ben Steinberg3-0/+15
This commit prevents custom styles on divs and spans from overriding styles on certain elements inside them, like headings, blockquotes, and links. On those elements, the "native" style is required for the element to display correctly. This change also allows nesting of custom styles; in order to do so, it removes the default "Compact" style applied to Plain blocks, except when inside a table.
2019-07-19Change order of ilvl and numId in document.xml (#5647)Agustín Martín Barbero4-0/+0
Workaround for Word Online shortcomming. Fixes #5645 Also, make list para properties go first. This reordering of properties shouldn't be necessary but it seems Word Online does not understand the docx correctly otherwise.
2019-03-21Docx writer: Use w:br without attributes for line breaks.John MacFarlane2-0/+0
We previously added the attribute `type="textWrapping"`, but this causes problems on Word Online. Closes #5377.
2019-03-11docx writer: avoid extra copy of abstractNum and num elements...John MacFarlane27-0/+0
...in numbering.xml. This caused pandoc-produced docx files to be uneditable using Word Online. The problem was that recent versions of reference.docx include samples of various kinds of text, including lists. The numering elements for these were getting copied over to the new docx, where they clashed with the autogenerated elements produced by pandoc. This didn't confuse Desktop Word, but it did confuse Word Online. Closes #5358.
2019-02-18Docx reader tests: fix test file with trailing space.Jesse Rosenthal1-1/+1
This failed due to the fix of #5273.
2019-02-18Docx reader: add tests for trimming last inline.Jesse Rosenthal2-0/+2
2019-02-12Docx reader: Add test for reading sdts in footnotes.Jesse Rosenthal2-0/+1
2019-02-06Docx reader: Tests for alternate document.xmlJesse Rosenthal2-0/+2
2019-01-26Improve writing metadata for docx, pptx and odt (#5252)Agustín Martín Barbero4-0/+4
* docx writer: support custom properties. Solves the writer part of #3024. Also supports additional core properties: `subject`, `lang`, `category`, `description`. * odt writer: improve standard properties, including the following core properties: `generator` (Pandoc/VERSION), `description`, `subject`, `keywords`, `initial-creator` (from authors), `creation-date` (actual creation date). Also fix date. * pptx writer: support custom properties. Also supports additional core properties: `subject`, `category`, `description`. * Includes golden tests. * MANUAL: document metadata support for docx, odt, pptx writers
2018-12-10Docx: add test for lists with level overrides.Jesse Rosenthal2-0/+37
2018-11-20Docx writer: Fix bookmarks to headers with long titles.John MacFarlane1-0/+0
Word has a 40 character limit for bookmark names. In addition, bookmarks must begin with a letter. Since pandoc's auto-generated identifiers may not respect these constraints, some internal links did not work. With this change, pandoc uses a bookmark name based on the SHA1 hash of the identifier when the identifier isn't a legal bookmark name. Closes #5091.
2018-10-09Docx writer: added framework for custom properties.John MacFarlane26-0/+0
So far, we don't actually write any custom properties, but we have the infrastructure to add this. See #3034.
2018-05-08Support underline in docx writer.John MacFarlane1-0/+0
Updated golden test and confirmed validity of file. Closes #4633.
2018-04-25Remove nonfree ICC profiles from thumbnails in test docx files.John MacFarlane18-0/+0
Closes #4588.
2018-04-17Docx reader tests: Test for combining adjacent code blocks.Jesse Rosenthal2-0/+6
2018-04-05Changes to tests to accommodate changes in pandoc-types.John MacFarlane1-0/+3
In https://github.com/jgm/pandoc-types/pull/36 we changed the table builder to pad cells. This commit changes tests (and two readers) to accord with this behavior.
2018-03-13Docx reader: add tests for nested smart tags.Jesse Rosenthal2-0/+7
2018-02-28Docx reader: Handle nested sdt tags.Jesse Rosenthal2-0/+3
Previously we had only unwrapped one level of sdt tags. Now we recurse if we find them. Closes: #4415
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-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-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 Rosenthal2-0/+11
2018-02-15Docx reader: Pick table width from the longest row or headerdanse2-0/+13
This change is intended to preserve as much of the table content as possible Closes #4360
2018-01-27Docx writer tests: Add tests for custom stylesJesse Rosenthal3-0/+0
2018-01-27Docx writer tests: Use new golden frameworkJesse Rosenthal26-0/+7
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-16Docx reader: Add test for hyperlinks in instrText tagJesse Rosenthal2-0/+1
This is difficult to recreate with a modern version of Word, so I'm using the file submitted with the bug report. It would be preferable to find a smaller example with Latin characters, though, so as not to confuse the issue being tested.
2018-01-02Docx reader: Add tests for paragraph insertion/deletion.Jesse Rosenthal4-0/+7
2017-12-31Docx reader: tests for overlapping targets (anchor spans).Jesse Rosenthal2-0/+3
2017-12-31Docx Reader: Combine adjacent anchors.Jesse Rosenthal1-2/+2
There isn't any reason to have numberous anchors in the same place, since we can't maintain docx's non-nesting overlapping. So we reduce to a single anchor, and have all links pointing to one of the overlapping anchors point to that one. This changes the behavior from commit e90c714c7 slightly (use the first anchor instead of the last) so we change the expected test result. Note that because this produces a state that has to be set after every invocation of `parPartToInlines`, we make the main function into a primed subfunction `parPartToInlines'`, and make `parPartToInlines` a wrapper around that.
2017-12-30Docx reader: tests for removing unused anchors.Jesse Rosenthal2-0/+3
2017-12-30Docx reader: Read multiple children of w:sdtContents`Jesse Rosenthal1-1/+6
Previously we had only read the first child of an sdtContents tag. Now we replace sdt with all children of the sdtContents tag. This changes the expected test result of our nested_anchors test, since now we read docx's generated TOCs.
2017-12-27Docx reader: add tests for structured document tags unwrapping.Jesse Rosenthal2-0/+10
2017-12-13Docx writer: Add tests for list continuation.Jesse Rosenthal4-0/+15
2017-12-04Add `empty_paragraphs` extension.John MacFarlane3-18/+9
* Deprecate `--strip-empty-paragraphs` option. Instead we now use an `empty_paragraphs` extension that can be enabled on the reader or writer. By default, disabled. * Add `Ext_empty_paragraphs` constructor to `Extension`. * Revert "Docx reader: don't strip out empty paragraphs." This reverts commit d6c58eb836f033a48955796de4d9ffb3b30e297b. * Implement `empty_paragraphs` extension in docx reader and writer, opendocument writer, html reader and writer. * Add tests for `empty_paragraphs` extension.
2017-12-02Docx reader: don't strip out empty paragraphs.John MacFarlane3-9/+18
We now have the `--strip-empty-paragraphs` option for that, if you want it. Closes #2252. Updated docx reader tests. We use stripEmptyParagraphs to avoid changing too many tests. We should add new tests for empty paragraphs.
2017-10-27Removed old adjacent_links test for docx reader.John MacFarlane2-1/+0
See #2270 for background -- this test blocked the consistent underline change and was hard to revise, so for now we are removing it.
2017-10-27Consistent underline for Readers (#2270)hftf1-1/+1
* Added underlineSpan builder function. This can be easily updated if needed. The purpose is for Readers to transform underlines consistently. * Docx Reader: Use underlineSpan and update test * Org Reader: Use underlineSpan and add test * Textile Reader: Use underlineSpan and add test case * Txt2Tags Reader: Use underlineSpan and update test * HTML Reader: Use underlineSpan and add test case
2017-08-06Docx reader: Add tests for avoiding zero-level header.Jesse Rosenthal2-0/+25
2017-02-04Moved tests/ -> test/.John MacFarlane98-0/+273