From c266734448544a118ed80e47deaa2590131c7f84 Mon Sep 17 00:00:00 2001 From: John MacFarlane Date: Sun, 19 Sep 2021 12:09:51 -0700 Subject: Use pretty-simple to format native output. 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.) --- test/writer.jats_articleauthoring | 20 +++++++++----------- 1 file changed, 9 insertions(+), 11 deletions(-) (limited to 'test/writer.jats_articleauthoring') diff --git a/test/writer.jats_articleauthoring b/test/writer.jats_articleauthoring index 59485a114..c2bddccb6 100644 --- a/test/writer.jats_articleauthoring +++ b/test/writer.jats_articleauthoring @@ -57,9 +57,9 @@ Gruber’s markdown test suite.

Paragraphs

Here’s a regular paragraph.

-

In Markdown 1.0.0 and earlier. Version 8. This line turns into a list - item. Because a hard-wrapped line in the middle of a paragraph looked like a - list item.

+

In Markdown 1.0.0 and earlier. Version 8. This line turns into a list item. + Because a hard-wrapped line in the middle of a paragraph looked like a list + item.

Here’s one with a bullet. * criminey.

There should be a hard line break here.

@@ -631,8 +631,7 @@ These should not be escaped: \$ \\ \> \[ \{

This is strikeout.

Superscripts: abcd ahello ahello there.

-

Subscripts: H2O, H23O, - Hmany of themO.

+

Subscripts: H2O, H23O, Hmany of themO.

These should not be superscripts or subscripts, because of the unescaped spaces: a^b c^d, a~b c~d.

 @@ -764,8 +763,7 @@ These should not be escaped: \$ \\ \> \[ \{ Reference -

Foo - bar.

+

Foo bar.

With embedded [brackets].

b by itself @@ -836,8 +834,8 @@ These should not be escaped: \$ \\ \> \[ \{ Footnotes

Here is a footnote reference, -

Here is the footnote. It can go anywhere after the footnote reference. - It need not be placed at the end of the document.

+

Here is the footnote. It can go anywhere after the footnote reference. It + need not be placed at the end of the document.

and another.

Here’s the long note. This one contains multiple blocks.

Subsequent blocks are indented to show that they belong to the footnote @@ -845,8 +843,8 @@ These should not be escaped: \$ \\ \> \[ \{

{ <code> }

-

If you want, you can indent every line, but you can also be lazy and - just indent the first line of each block.

+

If you want, you can indent every line, but you can also be lazy and just + indent the first line of each block.

 This should not be a footnote reference, because it contains a space.[^my note] Here is an inline note.

This is easier to type. Inline notes may contain -- cgit v1.2.3