aboutsummaryrefslogtreecommitdiff
path: root/test/command
AgeCommit message (Collapse)AuthorFilesLines
2017-12-04Add `empty_paragraphs` extension.John MacFarlane3-8/+99
* 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-03Test for #4113.John MacFarlane1-0/+12
Closes #4113.
2017-12-01LaTeX writer: allow specifying just width or height for image size.John MacFarlane1-1/+1
Previously both needed to be specified (unless the image was being resized to be smaller than its original size). If height but not width is specified, we now set width to textwidth (and similarly if width but not height is specified). Since we have keepaspectratio, this yields the desired result.
2017-12-01Revert "LaTeX writer: Add keepaspectratio to includegraphics..."John MacFarlane1-1/+1
This reverts commit 171187a4527497701b3c77bd56cea2d770d4e3b0.
2017-11-30LaTeX writer: Add keepaspectratio to includegraphics...John MacFarlane1-1/+1
...if only one of height/width is given.
2017-11-29Support beamer `\alert` in LaTeX reader. Closes #4091.John MacFarlane1-0/+6
2017-11-14Text.Pandoc.Parsing.uri: allow `&` and `=` as word characters.John MacFarlane1-0/+9
This fixes a bug where pandoc would stop parsing a URI with an empty attribute: for example, `&a=&b=` wolud stop at `a`. (The uri parser tries to guess which punctuation characters are part of the URI and which might be punctuation after it.) Closes #4068.
2017-11-13LaTeX reader: allow optional arguments on `\footnote`.John MacFarlane1-0/+6
Closes #4062.
2017-11-13Markdown writer: fix bug with doubled footnotes in grid tables.John MacFarlane1-0/+14
Closes #4061.
2017-11-12LaTeX reader: support column specs like `*{2}{r}`.John MacFarlane1-1/+14
This is equivalent to `rr`. We now expand it like a macro. Closes #4056.
2017-11-12LaTeX reader: allow optional args for parbox.John MacFarlane1-0/+11
See #4056.
2017-11-11Fixed YAML metadata with "chomp" (`|-`).John MacFarlane1-0/+12
Previously if a YAML block under `|-` contained a blank line, pandoc would not parse it as metadata.
2017-11-09Allow fenced code blocks to be indented 1-3 spaces.John MacFarlane1-0/+20
This brings our handling of them into alignment with CommonMark's. Closes #??.
2017-11-08Fix regression with --metadata.John MacFarlane1-0/+14
It should replace a metadata value set in the document itself, rather than creating a list including a new value. Closes #4054.
2017-11-04Fix strikethrough in gfm writer.John MacFarlane1-0/+6
Previously we got a crash, because we were trying to print a native cmark STRIKETHROUGH node, and the commonmark writer in cmark-github doesn't support this. Work around this by using a raw node to add the strikethrough delimiters. Closes #4038.
2017-11-02Improved support for columns in HTML.John MacFarlane1-3/+3
* Move as much as possible to the CSS in the template. * Ensure that all the HTML-based templates (including epub) contain the CSS for columns. * Columns default to 50% width unless they are given a width attribute. Closes #4028.
2017-11-02Fixed revealjs slide column width issues.John MacFarlane1-5/+3
* Remove "width" attribute which is not allowed on div. * Remove space between `<div class="column">` elements, since this prevents columns whose widths sum to 100% (the space takes up space). Closes #4028.
2017-11-01Really fix #3989.John MacFarlane1-1/+1
The previous fix only worked in certain cases. Other cases with `>` in an HTML attribute broke.
2017-11-01Updated command test for #3989.John MacFarlane1-5/+3
We didn't fix it completely before.
2017-10-31Fixed regression in parsing of HTML comments in markdown...John MacFarlane1-0/+8
and other non-HTML formats (`Text.Pandoc.Readers.HTML.htmlTag`). The parser stopped at the first `>` character, even if it wasn't the end of the comment. Closes #4019.
2017-10-31Add Millimeter constructor to Dimension in ImageSize.John MacFarlane1-0/+8
Minor API change. Now sizes given in 'mm' are no longer converted to 'cm'. Closes #4012.
2017-10-31LaTeX reader: handle `%` comment right after command.John MacFarlane2-0/+54
For example \emph% {hi}
2017-10-31Markdown reader: make sure fenced div closers work in lists.John MacFarlane1-1/+0
Previously the following failed: ::: {.class} 1. one 2. two ::: and you needed a blank line before the closing `:::`.
2017-10-31Make `fenced_divs` affect the Markdown writer.John MacFarlane1-3/+2
If `fenced_divs` is enabled, fenced divs will be used.
2017-10-30Added failing command test for #4007.John MacFarlane1-0/+23
2017-10-24Fenced divs: ensure that paragraph at end doesn't become Plain.John MacFarlane1-1/+14
Added test case.
2017-10-23Back to using [WARNING] and [INFO] to mark messages.John MacFarlane3-5/+5
2017-10-23Implemented fenced Divs.John MacFarlane1-0/+30
+ Added Ext_fenced_divs to Extensions (default for pandoc Markdown). + Document fenced_divs extension in manual. + Implemented fenced code divs in Markdown reader. + Added test. Closes #168.
2017-10-23HTML reader: `htmlTag` improvements.John MacFarlane1-0/+9
We previously failed on cases where an attribute contained a `>` character. This patch fixes the bug. Closes #3989.
2017-10-23More pleasing presentation of warnings and info messages.John MacFarlane3-5/+5
!! warning -- info
2017-10-23Fixed test for change in log level.John MacFarlane1-3/+0
2017-10-22LaTeX Reader: support \lettrinemb211-0/+9
2017-10-19LaTeX reader: support `\expandafter`.John MacFarlane1-0/+29
Closes #3983.
2017-10-16Revised command test 3971 to work with Windows.John MacFarlane1-2/+2
2017-10-16Improved handling of include files in LaTeX reader.John MacFarlane2-0/+11
Previously `\include` wouldn't work if the included file contained, e.g., a begin without a matching end. We've changed the Tok type so that it stores a full SourcePos, rather than just a line and column. So tokens keeep track of the file they came from. This allows us to use a simpler method for includes, which doesn't require parsing the included document as a whole. Closes #3971.
2017-10-16RST writer: correctly handle inline code containing backticks.John MacFarlane1-0/+6
(Use a :literal: role.) Closes #3974.
2017-10-16RST writer: don't backslash-escape word-internal punctuation.John MacFarlane1-0/+6
Closes #3978.
2017-10-11ConTeXt writer: Use identifiers for chapters.John MacFarlane1-0/+9
Closes #3968.
2017-10-08Add test - closes #3958.John MacFarlane1-0/+20
2017-10-02Markdown reader: Fixed bug with indented code following raw LaTeX.John MacFarlane1-0/+11
Closes #3947.
2017-09-27RST writer: add header anchors when header has non-standard id.John MacFarlane1-0/+13
Closes #3937.
2017-09-17Added `--strip-comments` option, `readerStripComments` in `ReaderOptions`.John MacFarlane1-0/+14
* Options: Added readerStripComments to ReaderOptions. * Added `--strip-comments` command-line option. * Made `htmlTag` from the HTML reader sensitive to this feature. This affects Markdown and Textile input. Closes #2552.
2017-09-12Textile reader: allow 'pre' code in list item.John MacFarlane1-0/+11
Closes #3916.
2017-09-07Markdown writer: Escape pipe characters when `pipe_tables` enabled.John MacFarlane1-1/+1
Closes #3887.
2017-09-01Org writer: stop using raw HTML to wrap divsAlbert Krewinkel1-0/+14
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
2017-08-27RST reader: Fixed `..include::` directive.John MacFarlane2-0/+7
Closes #3880.
2017-08-25LaTeX reader: improved support for \hyperlink, \hypertarget.John MacFarlane1-0/+38
Closes #2549.
2017-08-20Use pandoc-types 1.17.1. Tests updated for new simpleTable behavior...John MacFarlane2-2/+6
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 MacFarlane2-1/+47
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.
generated by cgit v1.2.3 (git 2.39.1) at 2024-12-14 15:07:29 +0000