pandoc - Conversion between markup formats

Age	Commit message (Collapse)	Author	Files	Lines
2021-09-28	Switch from pretty-simple to pretty-show for native output.	John MacFarlane	1	-22/+27
	Update tests. Reason: it turns out that the native output generated by pretty-simple isn't always readable by the native reader. According to https://github.com/cdepillabout/pretty-simple/issues/99 it is not a design goal of the library that the rendered values be readable using 'read'. This makes it unsuitable for our purposes. pretty-show is a bit slower and it uses 4-space indents (non-configurable), but it doesn't have this serious drawback.
2021-09-21	Use pretty-simple to format native output.	John MacFarlane	1	-15/+25
	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.)
2021-05-22	Handle relative lengths (e.g. `2*`) in HTML column widths.	John MacFarlane	1	-0/+29
	See <https://www.w3.org/TR/html4/types.html#h-6.6>. "A relative length has the form "i", where "i" is an integer. When allotting space among elements competing for that space, user agents allot pixel and percentage lengths first, then divide up remaining available space among relative lengths. Each relative length receives a portion of the available space that is proportional to the integer preceding the "". The value "" is equivalent to "1". Thus, if 60 pixels of space are available after the user agent allots pixel and percentage space, and the competing relative lengths are 1, 2, and 3, the 1 will be alloted 10 pixels, the 2* will be alloted 20 pixels, and the 3* will be alloted 30 pixels." Closes #4063.