aboutsummaryrefslogtreecommitdiff
path: root/test
AgeCommit message (Collapse)AuthorFilesLines
2017-08-21Small improvement to #3855 - move lang attribute up.John MacFarlane1-2/+1
So we don't have a dangling line with the closing `>` when `lang` is not set.
2017-08-21docbook5 template: use lang and subtitle variables (#3855)Jens Getreu1-1/+2
2017-08-21Muse reader: add definition list support (#3860)Alexander1-0/+52
2017-08-20Use pandoc-types 1.17.1. Tests updated for new simpleTable behavior...John MacFarlane5-19/+94
with empty headers.
2017-08-20LaTeX reader: Set identifiers on Spans used for \label.John MacFarlane1-1/+1
2017-08-19Markdown reader: use CommonMark rules for list item nesting.John MacFarlane4-14/+60
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.
2017-08-18Markdown reader: fixed parsing of fenced code after list...John MacFarlane1-0/+13
...when there is no intervening blank line. Closes #3733.
2017-08-18LaTeX reader: implement \newtoggle, \iftoggle, \toggletrue|falseJohn MacFarlane1-0/+26
from etoolbox. Closes #3853.
2017-08-17RST reader/writer: support unknown interpreted text roles...John MacFarlane2-1/+15
...by parsing them as Span with "role" attributes. This way they can be manipulated in the AST. Closes #3407.
2017-08-17HTML reader: support column alignments.John MacFarlane1-0/+52
These can be set either with a `width` attribute or with `text-width` in a `style` attribute. Closes #1881.
2017-08-16LaTeX reader: use Link instead of Span for `\ref`.John MacFarlane1-6/+6
This makes more sense semantically and avoids unnecessary Span [Link] nestings when references are resolved.
2017-08-16LaTeX reader: add Support for `glossaries` and `acronym` package (#3589)schrieveslaach1-0/+45
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.
2017-08-16Fixed command test #2994 on Windows.John MacFarlane1-1/+1
2017-08-14Implement multicolumn support for slide formats.John MacFarlane8-0/+98
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
2017-08-14Update tests for changes to LaTeX template.John MacFarlane4-8/+16
2017-08-14Test fixes so we can find data files.John MacFarlane3-7/+7
In old tests & command tests, we now set the environment variable pandoc_datadir. In lua tests, we set the datadir explicitly.
2017-08-14Changed command test for #2994 so it actually tests the writer.John MacFarlane2-1/+4
2017-08-13Fixed command tests to set local path.John MacFarlane1-5/+5
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.
2017-08-13Put content of \ref, \label commands into span… (#3639)schrieveslaach1-0/+54
* Put content of `\ref` and `\label` commands into Span elements so they can be used in filters. * Add support for `\eqref`
2017-08-13CommonMark writer: prefer pipe tables to HTML tables...John MacFarlane1-0/+11
...even if it means losing relative column width information. See #3734.
2017-08-13Markdown writer: Use pipe tables if `raw_html` disabled...John MacFarlane1-0/+39
and `pipe_tables` enabled, even if the table has relative width information. Closes #3734.
2017-08-13Use hslua >= 0.7, update Lua codeAlbert Krewinkel1-17/+14
2017-08-12Docx writer: pass through comments.John MacFarlane2-0/+7
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.
2017-08-12Escape MetaString values (as added with --metadata flag).John MacFarlane1-0/+13
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.
2017-08-12LaTeX reader: Fixed space after \figurename etc.John MacFarlane1-8/+16
2017-08-12Fixed data-dir on translations tests.John MacFarlane1-3/+3
2017-08-11More translation tests.John MacFarlane1-0/+8
2017-08-11Added simple test for translations.John MacFarlane1-0/+13
2017-08-11Command tests; print stderr when a test fails.John MacFarlane1-1/+4
2017-08-10Fixed writer tests not to use writerUserDataDir.John MacFarlane1-3/+3
2017-08-10RST reader: implement csv-table directive.John MacFarlane2-0/+59
Most attributes are supported, including `:file:` and `:url:`. A (probably insufficient) test case has been added. Closes #3533.
2017-08-09Org reader: use org-language attribute rather than data-org-language.John MacFarlane1-9/+9
2017-08-09Org reader: use tag-name attribute instead of data-tag-name.John MacFarlane1-1/+1
2017-08-09LaTeX reader: Use `label` instead of `data-label` for label in caption.John MacFarlane1-1/+1
See d441e656db576f266c4866e65ff9e4705d376381, #3639.
2017-08-09HTML reader: parse <main> like <div role=main>. (#3791)bucklereed1-0/+15
* HTML reader: parse <main> like <div role=main>. * <main> closes <p> and behaves like a block element generally
2017-08-08Muse writer: update test results (#3845)Alexander1-3/+6
2017-08-08Muse writer: insert two blanklines between lists of the same type (#3844)Alexander1-0/+73
2017-08-08CommonMark writer: avoid excess blank lines at end of output.John MacFarlane1-8/+0
2017-08-08Thread options through CommonMark reader.John MacFarlane1-0/+8
This is more efficient than doing AST traversals for emojis and hard breaks. Also make behavior sensitive to `raw_html` extension.
2017-08-08CommonMark writer: support `hard_line_breaks`, `smart`.John MacFarlane1-0/+103
Add tests.
2017-08-07Markdown reader: fixed spurious parsing as citation as reference def.John MacFarlane1-0/+15
We now disallow reference keys starting with `@` if the `citations` extension is enabled. Closes #3840.
2017-08-07LaTeX reader: Support simple `\def` macros.John MacFarlane1-0/+28
Note that we still don't support macros with fancy parameter delimiters, like \def\foo#1..#2{...}
2017-08-07LaTeX reader: Support `\let`.John MacFarlane1-0/+23
Also, fix regular macros so they're expanded at the point of use, and NOT also the point of definition. `\let` macros, by contrast, are expanded at the point of definition. Added an `ExpansionPoint` field to `Macro` to track this difference.
2017-08-06Muse reader: debug indented paragraph support (#3839)Alexander1-6/+29
Take only first line indentation into account and do not start new paragraph on indentation change.
2017-08-06Docx reader: Add tests for avoiding zero-level header.Jesse Rosenthal3-0/+29
2017-08-06Muse reader: debug list and list item separation rules (#3837)Alexander1-0/+89
2017-08-05LaTeX reader: plainbreak, fancybreak et al from the memoir class (#3833)bucklereed1-0/+26
2017-08-03Muse reader: do not allow headers in blockquotes (#3831)Alexander Krotov1-1/+7
2017-08-02DokuWiki reader: better handling for code block in list item.John MacFarlane1-0/+14
Closes #3824.
2017-07-30Markdown writer: better escaping of `<` and `>`.John MacFarlane1-4/+4
If `all_symbols_escapable` is set, we backslash escape these. Otherwise we use entities as before.