aboutsummaryrefslogtreecommitdiff
path: root/test/command
AgeCommit message (Collapse)AuthorFilesLines
2019-05-28Remove command test for #5517.John MacFarlane1-32/+0
We need a better test that works cross-platform. Until then, removing this. Closes #5528.
2019-05-28HTML writer: emit empty alt tag in figures (#5518)Mauro Bieg3-5/+5
The same text is already in the <figcaption> and screen-readers would read it twice, see #4737
2019-05-28Add test for relative file: URI to #5517.John MacFarlane1-0/+6
2019-05-28Fix handling of `file:` URL scheme in `downloadOrRead` (#5522)Mauro Bieg1-0/+26
Move up the pattern match to be reachable, closes #5517. Previously `file:/` URLs were handled wrongly and pandoc attempted to make HTTP requests, which failed.
2019-05-25HTML reader: trim definition list termsAlexander Krotov1-0/+17
2019-05-22Markdown writer: Ensure the code fence is long enough.John MacFarlane1-0/+14
Previously too few backticks were used when the code block contained an indented line of backticks. (Ditto tildes.) Cloess #5519.
2019-05-21Markdown writer: Handle labels with integer namesJesse Rosenthal1-0/+18
Previously if labels had integer names, it could produce a conflict with auto-labeled reference links. Now we test for a conflict and find the next available integer. Note that this involves adding a new state variable `stPrevRefs` to keep track of refs used in other document parts when using `--reference-location=block|section` Closes #5495
2019-05-12Org writer: always indent src blocks content by 2 spacesAlbert Krewinkel1-6/+6
Emacs always uses two spaces when indenting the content of src blocks, e.g., when exiting a `C-c '` edit-buffer. Pandoc used to indent contents by the space-equivalent of one tab, but now always uses two spaces, too. Closes: #5440
2019-05-01Fix footnote in image caption.John MacFarlane1-0/+12
Regression! The fix for #4683 broke this case.
2019-04-30HTML: prevent gratuitious emojification on iOS.John MacFarlane1-1/+1
iOS chooses to render a number of Unicode entities, including '↩', as big colorful emoji. This can be defeated by appending Unicode VARIATION SELECTOR-15'/'VARIATION SELECTOR-16'. So we now append this character when escaping strings, for both '↩' and '↔'. If other characters prove problematic, they can simply be added to needsVariationSelector. Closes #5469.
2019-04-15RST writer: treat Span as transparent.John MacFarlane1-0/+6
Previously an Emph inside a Span was being treated as nested markup and ignored. With this patch, the Span is just ignored. Closes #5446.
2019-04-02Update command test #5416 to make it windows friendlyJohn MacFarlane1-2/+4
2019-04-01Dokuwiki Reader fix: parse single curly brace (#5417)Mauro Bieg1-0/+11
fixes #5416
2019-03-29LaTeX writer: Avoid inadvertently creating ?` or !` ligatures.John MacFarlane1-0/+14
These are upside down ? and !, resp. Closes #5407.
2019-03-28Markdown reader: fenced div takes priority over setext header.John MacFarlane1-0/+9
For ::: {.cell} --- :::
2019-03-22LaTeX writer: Fix footnotes in table caption and cells.John MacFarlane1-0/+44
This fixes a bug wherein footnotes appeared in the wrong order, and with duplicate numbers, when in table captions and cells. We now use regular `\footnote` commands, even in the table caption and the minipages containing cells. Apparently longtable knows how to handle this. Closes #5367.
2019-03-18Improved fix to #5340 and added test.John MacFarlane1-0/+14
2019-03-17Properly escape attributes in Markdown writer.John MacFarlane1-0/+7
Closes #5369.
2019-03-17Add test case for #5368.John MacFarlane1-0/+23
2019-03-02Use XDG data directory for user data directory.John MacFarlane1-1/+1
Instead of `$HOME/.pandoc`, the default user data directory is now `$XDG_DATA_HOME/pandoc`, where `XDG_DATA_HOME` defaults to `$HOME/.local/share` but can be overridden by setting the environment variable. If this directory is missing, then `$HOME/.pandoc` is searched instead, for backwards compatibility. However, we recommend moving local pandoc data files from `$HOME/.pandoc` to `$HOME/.local/share/pandoc`. On Windows the default user data directory remains the same. Closes #3582.
2019-02-25Shared.compactify: Avoid mixed lists.John MacFarlane1-0/+17
This improves on the original fix to #5285 by preventing other mixed lists (lists with a mix of Plain and Para elements) that were allowed given the original fix.
2019-02-23JATS reader: fix parsing of figures.John MacFarlane1-0/+24
This ensures that a figure containing a single image is parsed as a pandoc "implicit figure" (i.e., a Para with a single Image whose title attribute begins with `fig:`). More complex figures will still be parsed as divs. Closes #5321.
2019-02-15Markdown reader: fix bug parsing fenced code blocks.John MacFarlane1-0/+24
Previously parsing would break if the code block contained a string of backticks of sufficient length followed by something other than end of line. Closes #5304.
2019-02-08Improve tight/loose list handling.John MacFarlane1-0/+15
Closes #5285. Previously the algorithm allowed list items with a mix of Para and Plain, which is never wanted. compactify in T.P.Shared has been modified so that, if a list's items contain (at the top level) Para elements (aside from perhaps at the very end), ALL Plains are converted to Paras.
2019-02-04Markdown reader: add newline when parsing blocks in YAML.John MacFarlane1-0/+12
Otherwise last block gets parsed as a Plain rather than a Para. This is a regression in pandoc 2.x. This patch restores pandoc 1.19 behavior. Closes #5271.
2019-02-02Update test for last commit.John MacFarlane1-3/+3
2019-02-01LaTeX writer: avoid `{}` after control sequences when escaping.John MacFarlane2-4/+3
`\ldots{}.` doesn't behave as well as `\ldots.` with the latex ellipsis package. This patch causes pandoc to avoid emitting the `{}` when it is not necessary. Now `\ldots` and other control sequences used in escaping will be followed by either a `{}`, a space, or nothing, depending on context. Thanks to Elliott Slaughter for the suggestion.
2019-01-31LaTeX reader: don't let `\egroup` match `{`.John MacFarlane1-0/+12
`braced` now actually requires nested braces. Otherwise some legitimate command and environment definitions can break (see test/command/tex-group.md).
2019-01-22LaTeX reader: support `\endinput`. Closes #5233.John MacFarlane1-0/+9
2019-01-21HTML and markdown: treat textarea as a verbatim environment.John MacFarlane1-0/+12
We don't want to parse its contents as Markdown or HTML. Closes #5241.
2019-01-09RST reader: change treatment of `number-lines` directives. (#5207)Brian Leung2-0/+11
Directives of this type without numeric inputs should not have a `startFrom` attribute; with a blank value, the writers can produce extra whitespace.
2019-01-08Removed superfluous sourceCode class on code blocks.John MacFarlane1-1/+1
* These were added by the RST reader and, for literate Haskell, by the Markdown and LaTeX readers. There is no point to this class, and it is not applied consistently by all readers. See #5047. * Reverse order of `literate` and `haskell` classes on code blocks when parsing literate Haskell. Better if `haskell` comes first.
2019-01-02Implement task lists (#5139)Mauro Bieg2-0/+142
Closes #3051
2019-01-02Commonmark writer: fix handling of SoftBreak with `hard_line_breaks`.John MacFarlane1-0/+7
This should be rendered as a space. Closes #5195.
2018-12-31Simplify/fix reading of `--metadata` values on command line.John MacFarlane1-0/+12
Previously we used HsYAML's decodeStrict to recognize boolean values (treating everything else as a string). This caused problems relating to hvr/HsYAML#7. We now just check for the recognized boolean values `true|True|TRUE|false|False|FALSE`, and avoid using HsYAML. Closes #5177.
2018-12-28Org writer: preserve line-numbering for example and code blocks.leungbk1-0/+41
2018-12-05RST writer: don't wrap simple table header lines.John MacFarlane1-0/+18
Closes #5128.
2018-12-04Strip out illegal XML characters in escapeXMLString.John MacFarlane1-0/+9
Closes #5119.
2018-12-03Markdown writer: include needed whitespace after HTML figure.John MacFarlane1-0/+13
We use HTML for a figure in markdown dialects that can't represent it natively. Closes #5121.
2018-11-25Added test for #5053.John MacFarlane1-0/+14
Note that the fix for #5099 also fixes #5053, a pandoc 2.4 regression in parsing underscore emphasis after symbols.
2018-11-25Fix parsing of citations and quotes after parentheses.John MacFarlane3-13/+15
Starting with pandoc 2.4, citations and quoted inlines were no longer recognized after parentheses. This is because of commit 9b0bd4ec6f5c9125efb3e36232e6d1f6ac08a728, which is reverted here. The point of that commit was to allow relocation of soft line breaks to before an abbreviation, so that a nonbreaking space could be added after the abbreviation. Now we simply leave the soft line break in place, even though this means that we won't get a nonbreaking space after "Mr." at the end of a line (and in LaTeX this may result in a longer intersentential space). Those who care about this issue should take care not to end lines with an abbreviation, or to insert nonbreaking spaces manually. Closes #5099.
2018-11-16HTML reader: allow tfoot before body rows.John MacFarlane1-0/+16
Closes #5079.
2018-11-15HTML reader: parse `<small>` as a Span with class "small".John MacFarlane1-0/+7
Closes #5080.
2018-11-15Asciidoc writer: Render Spans using `[#id .class]#contents#`.John MacFarlane1-0/+6
See #5080.
2018-11-13Fix test case for #5014.John MacFarlane1-1/+3
2018-11-13HTML reader: allow thead containing a row with td rather than th.John MacFarlane1-0/+17
See #5014. Note that this doesn't address the original issue in #5014, only an unrelated side-issue.
2018-11-12LaTeX writer: don't emit `[<+->]` unless beamer output,John MacFarlane1-0/+14
even if `writerIncremental` is True. See #5072.
2018-11-11Exactly match GitHub's identifier generating algorithm.John MacFarlane1-0/+4
See #5057.
2018-11-11Text.Pandoc.Shared: add parameter to uniqueIdent, inlineListToIdentifier.John MacFarlane1-4/+4
The parameter is Extensions. This allows these functions to be sensitive to the settings of `Ext_gfm_auto_identifiers` and `Ext_ascii_identifiers`. This allows us to use `uniqueIdent` in the CommonMark reader, replacing some custom code. It also means that `gfm_auto_identifiers` can now be used in all formats. Semantically, `gfm_auto_identifiers` is now a modifier of `auto_identifiers`; for identifiers to be set, `auto_identifiers` must be turned on, and then the type of identifier produced depends on `gfm_auto_identifiers` and `ascii_identifiers` are set. Closes #5057.
2018-11-06Add command test for #5050.John MacFarlane1-0/+7
generated by cgit v1.2.3 (git 2.39.1) at 2024-12-02 17:06:26 +0000