summaryrefslogtreecommitdiff
path: root/test/command
Commit message (Collapse)AuthorAge
* Markdown writer: Escape pipe characters when `pipe_tables` enabled.John MacFarlane2017-09-07
| | | | Closes #3887.
* 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
* RST reader: Fixed `..include::` directive.John MacFarlane2017-08-27
| | | | Closes #3880.
* LaTeX reader: improved support for \hyperlink, \hypertarget.John MacFarlane2017-08-25
| | | | Closes #2549.
* 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
* Changed command test for #2994 so it actually tests the writer.John MacFarlane2017-08-14
|
* 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.
* 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
|
* 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.
* LaTeX reader: Use `label` instead of `data-label` for label in caption.John MacFarlane2017-08-09
| | | | See d441e656db576f266c4866e65ff9e4705d376381, #3639.
* CommonMark writer: avoid excess blank lines at end of output.John MacFarlane2017-08-08
|
* Thread options through CommonMark reader.John MacFarlane2017-08-08
| | | | | | | This is more efficient than doing AST traversals for emojis and hard breaks. Also make behavior sensitive to `raw_html` extension.
* CommonMark writer: support `hard_line_breaks`, `smart`.John MacFarlane2017-08-08
| | | | Add tests.
* Markdown reader: fixed spurious parsing as citation as reference def.John MacFarlane2017-08-07
| | | | | We now disallow reference keys starting with `@` if the `citations` extension is enabled. Closes #3840.
* LaTeX reader: Support simple `\def` macros.John MacFarlane2017-08-07
| | | | | | | Note that we still don't support macros with fancy parameter delimiters, like \def\foo#1..#2{...}
* LaTeX reader: Support `\let`.John MacFarlane2017-08-07
| | | | | | | | 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.
* DokuWiki reader: better handling for code block in list item.John MacFarlane2017-08-02
| | | | Closes #3824.
* Small tweak in test (add --wrap=preserve).John MacFarlane2017-07-26
|
* HTML writer: render raw inline environments when --mathjax used.John MacFarlane2017-07-26
| | | | | | | | We previously did this only with raw blocks, on the assumption that math environments would always be raw blocks. This has changed since we now parse them as inline environments. Closes #3816.
* HTML writer: insert data- in front of unsupported attributes.John MacFarlane2017-07-25
| | | | | | | | | | Thus, a span with attribute 'foo' gets written to HTML5 with 'data-foo', so it is valid HTML5. HTML4 is not affected. This will allow us to use custom attributes in pandoc without producing invalid HTML.
* Merge branch 'textcolor-support' of https://github.com/schrieveslaach/pandoc ↵John MacFarlane2017-07-25
|\ | | | | | | into schrieveslaach-textcolor-support
| * Merge branch 'master' of https://github.com/jgm/pandoc into textcolor-supportMarc Schreiber2017-07-13
| |\
| * \ Merge branch 'master' into textcolor-supportschrieveslaach2017-06-12
| |\ \
| * | | Add \colorbox supportMarc Schreiber2017-06-01
| | | |
| * | | Add another test to make sure that textcolor parsing is working in the ↵Marc Schreiber2017-05-23
| | | | | | | | | | | | | | | | inside of a paragraph
| * | | Add suggestions of @jgm: parse bracketed stuff as inlinesMarc Schreiber2017-05-23
| | | |
| * | | \textcolor will be parse as span at the beginning of a paragraphMarc Schreiber2017-05-04
| | | |
| * | | \textcolor works as inline and block commandMarc Schreiber2017-05-03
| | | |
| * | | Add block version of \textcolorMarc Schreiber2017-05-03
| | | |
| * | | Add basic \textcolor support to LaTeX readerMarc Schreiber2017-05-02
| | | |
* | | | LaTeX reader: support etoolbox's ifstrequal.John MacFarlane2017-07-24
| | | |
* | | | Added a test case with `markdown-latex_macros`.John MacFarlane2017-07-24
| | | |
* | | | LaTeX reader: some improvements in macro parsing.John MacFarlane2017-07-24
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Fixed applyMacros so that it operates on the whole string, not just the first token! Don't remove macro definitions from the output, even if Ext_latex_macros is set, so that macros will be applied. Since they're only applied to math in Markdown, removing the macros can have bad effects. Even for math macros, keeping them should be harmless.
generated by cgit v1.2.3 (git 2.25.1) at 2024-06-16 00:07:26 +0000