pandoc - Conversion between markup formats

Age	Commit message (Collapse)	Author	Files	Lines
2021-09-21	Use pretty-simple to format native output.	John MacFarlane	1	-19/+19
	Previously we used our own homespun formatting. But this produces over-long lines that aren't ideal for diffs in tests. Easier to use something off-the-shelf and standard. Closes #7580. Performance is slower by about a factor of 10, but this isn't really a problem because native isn't suitable as a serialization format. (For serialization you should use json, because the reader is so much faster than native.)
2019-09-22	Make `plain` output plainer.	John MacFarlane	1	-89/+35
	Previously we used the following Project Gutenberg conventions for plain output: - extra space before and after level 1 and 2 headings - all-caps for strong emphasis `LIKE THIS` - underscores surrounding regular emphasis `_like this_` This commit makes `plain` output plainer. Strong and Emph inlines are rendered without special formatting. Headings are also rendered without special formatting, and with only one blank line following. To restore the former behavior, use `-t plain+gutenberg`. API change: Add `Ext_gutenberg` constructor to `Extension`. See #5741.
2019-02-25	Shared.compactify: Avoid mixed lists.	John MacFarlane	1	-0/+1
	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.
2017-05-25	Added `spaced_reference_links` extension.	John MacFarlane	1	-4/+0
	This is now the default for pandoc's Markdown. It allows whitespace between the two parts of a reference link: e.g. [a] [b] [b]: url This is now forbidden by default. Closes #2602.
2017-03-21	Plain writer: use _(..) or ^(..) for super/subscript...	John MacFarlane	1	-2/+2
	...unless unicode super/subscripted characters are available.
2017-02-04	Moved tests/ -> test/.	John MacFarlane	1	-0/+695