summaryrefslogtreecommitdiff
path: root/test
Commit message (Collapse)AuthorAge
* LaTeX template: load polyglossia after header-includes.John MacFarlane2017-09-07
| | | | | | It needs to be loaded as late as possible. Closes #3898.
* Markdown writer: Escape pipe characters when `pipe_tables` enabled.John MacFarlane2017-09-07
| | | | Closes #3887.
* Muse reader: Allow finishing header with EOF (#3897)Alexander2017-09-06
|
* Muse reader: require at least one space char after * in header (#3895)Alexander2017-09-05
|
* Muse reader: parse <div> tag (#3888)Alexander2017-09-04
|
* Org writer: stop using raw HTML to wrap divsAlbert Krewinkel2017-09-01
| | | | | | | | | | | | Div's are difficult to translate into org syntax, as there are multiple div-like structures (drawers, special blocks, greater blocks) which all have their advantages and disadvantages. Previously pandoc would use raw HTML to preserve the full div information; this was rarely useful and resulted in visual clutter. Div-rendering was changed to discard the div's classes and key-value pairs if there is no natural way to translate the div into an org structure. Closes: #3771
* Muse reader: parse verse markup (#3882)Alexander2017-08-29
|
* RST reader: handle blank lines correctly in line blocks (#3881)Alexander2017-08-28
| | | | | | Previously pandoc would sometimes combine two line blocks separated by blanks, and ignore trailing blank lines within the line block. Test is checked to be consisted with http://rst.ninjs.org/
* RST reader: Fixed `..include::` directive.John MacFarlane2017-08-27
| | | | Closes #3880.
* LaTeX reader: improved support for \hyperlink, \hypertarget.John MacFarlane2017-08-25
| | | | Closes #2549.
* Muse reader: parse <verse> tag (#3872)Alexander2017-08-25
|
* LaTeX reader: RN and Rn, from biblatex (#3854)bucklereed2017-08-24
|
* Muse reader: avoid crashes on multiparagraph inline tags (#3866)Alexander2017-08-22
| | | Test checks that behavior is consistent with Amusewiki
* Muse reader: do not allow closing tags with EOF (#3863)Alexander2017-08-22
| | | This behavior is compatible to Amusewiki
* Text.Pandoc.Lua: support Inline and Block catch-allsAlbert Krewinkel2017-08-22
| | | | | | | Try function `Inline`/`Block` if no other filter function of the respective type matches an element. Closes: #3859
* Text.Pandoc.Lua: respect metatable when getting filtersAlbert Krewinkel2017-08-22
| | | | | | | | | | | | | | | | This change makes it possible to define a catch-all function using lua's metatable lookup functionality. function catch_all(el) … end return { setmetatable({}, {__index = function(_) return catch_all end}) } A further effect of this change is that the map with filter functions now only contains functions corresponding to AST element constructors.
* Small improvement to #3855 - move lang attribute up.John MacFarlane2017-08-21
| | | | | So we don't have a dangling line with the closing `>` when `lang` is not set.
* docbook5 template: use lang and subtitle variables (#3855)Jens Getreu2017-08-21
|
* Muse reader: add definition list support (#3860)Alexander2017-08-21
|
* Use pandoc-types 1.17.1. Tests updated for new simpleTable behavior...John MacFarlane2017-08-20
| | | | with empty headers.
* LaTeX reader: Set identifiers on Spans used for \label.John MacFarlane2017-08-20
|
* Markdown reader: use CommonMark rules for list item nesting.John MacFarlane2017-08-19
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Closes #3511. Previously pandoc used the four-space rule: continuation paragraphs, sublists, and other block level content had to be indented 4 spaces. Now the indentation required is determined by the first line of the list item: to be included in the list item, blocks must be indented to the level of the first non-space content after the list marker. Exception: if are 5 or more spaces after the list marker, then the content is interpreted as an indented code block, and continuation paragraphs must be indented two spaces beyond the end of the list marker. See the CommonMark spec for more details and examples. Documents that adhere to the four-space rule should, in most cases, be parsed the same way by the new rules. Here are some examples of texts that will be parsed differently: - a - b will be parsed as a list item with a sublist; under the four-space rule, it would be a list with two items. - a code Here we have an indented code block under the list item, even though it is only indented six spaces from the margin, because it is four spaces past the point where a continuation paragraph could begin. With the four-space rule, this would be a regular paragraph rather than a code block. - a code Here the code block will start with two spaces, whereas under the four-space rule, it would start with `code`. With the four-space rule, indented code under a list item always must be indented eight spaces from the margin, while the new rules require only that it be indented four spaces from the beginning of the first non-space text after the list marker (here, `a`). This change was motivated by a slew of bug reports from people who expected lists to work differently (#3125, #2367, #2575, #2210, #1990, #1137, #744, #172, #137, #128) and by the growing prevalance of CommonMark (now used by GitHub, for example). Users who want to use the old rules can select the `four_space_rule` extension. * Added `four_space_rule` extension. * Added `Ext_four_space_rule` to `Extensions`. * `Parsing` now exports `gobbleAtMostSpaces`, and the type of `gobbleSpaces` has been changed so that a `ReaderOptions` parameter is not needed.
* Markdown reader: fixed parsing of fenced code after list...John MacFarlane2017-08-18
| | | | | | ...when there is no intervening blank line. Closes #3733.
* LaTeX reader: implement \newtoggle, \iftoggle, \toggletrue|falseJohn MacFarlane2017-08-18
| | | | | | from etoolbox. Closes #3853.
* RST reader/writer: support unknown interpreted text roles...John MacFarlane2017-08-17
| | | | | | | ...by parsing them as Span with "role" attributes. This way they can be manipulated in the AST. Closes #3407.
* HTML reader: support column alignments.John MacFarlane2017-08-17
| | | | | | | These can be set either with a `width` attribute or with `text-width` in a `style` attribute. Closes #1881.
* LaTeX reader: use Link instead of Span for `\ref`.John MacFarlane2017-08-16
| | | | | This makes more sense semantically and avoids unnecessary Span [Link] nestings when references are resolved.
* LaTeX reader: add Support for `glossaries` and `acronym` package (#3589)schrieveslaach2017-08-16
| | | | | Acronyms are not resolved by the reader, but acronym and glossary information is put into attributes on Spans so that they can be processed in filters.
* Fixed command test #2994 on Windows.John MacFarlane2017-08-16
|
* Implement multicolumn support for slide formats.John MacFarlane2017-08-14
| | | | | | | | | | | | | | | | | | | | | | The structure expected is: <div class="columns"> <div class="column" width="40%"> contents... </div> <div class="column" width="60%"> contents... </div> </div> Support has been added for beamer and all HTML slide formats. Closes #1710. Note: later we could add a more elegant way to create this structure in Markdown than to use raw HTML div elements. This would come for free with a "native div syntax" (#168). Or we could devise something specific to slides
* Update tests for changes to LaTeX template.John MacFarlane2017-08-14
|
* Test fixes so we can find data files.John MacFarlane2017-08-14
| | | | | | | In old tests & command tests, we now set the environment variable pandoc_datadir. In lua tests, we set the datadir explicitly.
* Changed command test for #2994 so it actually tests the writer.John MacFarlane2017-08-14
|
* Fixed command tests to set local path.John MacFarlane2017-08-13
| | | | | | Previously we just tacked on a directory to the command line, but that didn't work when we e.g. used a pipe for round tripping, with two invocations of pandoc.
* Put content of \ref, \label commands into span… (#3639)schrieveslaach2017-08-13
| | | | | * Put content of `\ref` and `\label` commands into Span elements so they can be used in filters. * Add support for `\eqref`
* CommonMark writer: prefer pipe tables to HTML tables...John MacFarlane2017-08-13
| | | | | ...even if it means losing relative column width information. See #3734.
* Markdown writer: Use pipe tables if `raw_html` disabled...John MacFarlane2017-08-13
| | | | | | | and `pipe_tables` enabled, even if the table has relative width information. Closes #3734.
* Use hslua >= 0.7, update Lua codeAlbert Krewinkel2017-08-13
|
* Docx writer: pass through comments.John MacFarlane2017-08-12
| | | | | | | | | | | | | | We assume that comments are defined as parsed by the docx reader: I want <span class="comment-start" id="0" author="Jesse Rosenthal" date="2016-05-09T16:13:00Z">I left a comment.</span>some text to have a comment <span class="comment-end" id="0"></span>on it. We assume also that the id attributes are unique and properly matched between comment-start and comment-end. Closes #2994.
* Escape MetaString values (as added with --metadata flag).John MacFarlane2017-08-12
| | | | | | | | | | | | | | | | | Previously they would be transmitted to the template without any escaping. Note that `--M title='*foo*'` yields a different result from --- title: *foo* --- In the latter case, we have emphasis; in the former case, just a string with literal asterisks (which will be escaped in formats, like Markdown, that require it). Closes #3792.
* LaTeX reader: Fixed space after \figurename etc.John MacFarlane2017-08-12
|
* Fixed data-dir on translations tests.John MacFarlane2017-08-12
|
* More translation tests.John MacFarlane2017-08-11
|
* Added simple test for translations.John MacFarlane2017-08-11
|
* Command tests; print stderr when a test fails.John MacFarlane2017-08-11
|
* Fixed writer tests not to use writerUserDataDir.John MacFarlane2017-08-10
|
* RST reader: implement csv-table directive.John MacFarlane2017-08-10
| | | | | | | Most attributes are supported, including `:file:` and `:url:`. A (probably insufficient) test case has been added. Closes #3533.
* Org reader: use org-language attribute rather than data-org-language.John MacFarlane2017-08-09
|
* Org reader: use tag-name attribute instead of data-tag-name.John MacFarlane2017-08-09
|
* LaTeX reader: Use `label` instead of `data-label` for label in caption.John MacFarlane2017-08-09
| | | | See d441e656db576f266c4866e65ff9e4705d376381, #3639.