aboutsummaryrefslogtreecommitdiff
path: root/test/writer.jats_articleauthoring
diff options
context:
space:
mode:
authorJohn MacFarlane <jgm@berkeley.edu>2021-09-19 12:09:51 -0700
committerJohn MacFarlane <jgm@berkeley.edu>2021-09-21 12:37:42 -0700
commitc266734448544a118ed80e47deaa2590131c7f84 (patch)
treed5793b1dc732456894c96e8ee6829dab9d539388 /test/writer.jats_articleauthoring
parent5f7e7f539a02818d0a94309b15d648d51d1eaee6 (diff)
downloadpandoc-c266734448544a118ed80e47deaa2590131c7f84.tar.gz
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.)
Diffstat (limited to 'test/writer.jats_articleauthoring')
-rw-r--r--test/writer.jats_articleauthoring20
1 files changed, 9 insertions, 11 deletions
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.</p>
<sec id="paragraphs">
<title>Paragraphs</title>
<p>Here’s a regular paragraph.</p>
- <p>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.</p>
+ <p>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.</p>
<p>Here’s one with a bullet. * criminey.</p>
<p>There should be a hard line break
here.</p>
@@ -631,8 +631,7 @@ These should not be escaped: \$ \\ \&gt; \[ \{</preformat>
<p><strike>This is <italic>strikeout</italic>.</strike></p>
<p>Superscripts: a<sup>bc</sup>d a<sup><italic>hello</italic></sup>
a<sup>hello there</sup>.</p>
- <p>Subscripts: H<sub>2</sub>O, H<sub>23</sub>O,
- H<sub>many of them</sub>O.</p>
+ <p>Subscripts: H<sub>2</sub>O, H<sub>23</sub>O, H<sub>many of them</sub>O.</p>
<p>These should not be superscripts or subscripts, because of the unescaped
spaces: a^b c^d, a~b c~d.</p>
</sec>
@@ -764,8 +763,7 @@ These should not be escaped: \$ \\ \&gt; \[ \{</preformat>
</sec>
<sec id="reference">
<title>Reference</title>
- <p>Foo
- <ext-link ext-link-type="uri" xlink:href="/url/">bar</ext-link>.</p>
+ <p>Foo <ext-link ext-link-type="uri" xlink:href="/url/">bar</ext-link>.</p>
<p>With <ext-link ext-link-type="uri" xlink:href="/url/">embedded
[brackets]</ext-link>.</p>
<p><ext-link ext-link-type="uri" xlink:href="/url/">b</ext-link> by itself
@@ -836,8 +834,8 @@ These should not be escaped: \$ \\ \&gt; \[ \{</preformat>
<sec id="footnotes">
<title>Footnotes</title>
<p>Here is a footnote reference,<fn>
- <p>Here is the footnote. It can go anywhere after the footnote reference.
- It need not be placed at the end of the document.</p>
+ <p>Here is the footnote. It can go anywhere after the footnote reference. It
+ need not be placed at the end of the document.</p>
</fn> and another.<fn>
<p>Here’s the long note. This one contains multiple blocks.</p>
<p>Subsequent blocks are indented to show that they belong to the footnote
@@ -845,8 +843,8 @@ These should not be escaped: \$ \\ \&gt; \[ \{</preformat>
<p specific-use="wrapper">
<preformat> { &lt;code&gt; }</preformat>
</p>
- <p>If you want, you can indent every line, but you can also be lazy and
- just indent the first line of each block.</p>
+ <p>If you want, you can indent every line, but you can also be lazy and just
+ indent the first line of each block.</p>
</fn> This should <italic>not</italic> be a footnote reference, because it
contains a space.[^my note] Here is an inline note.<fn>
<p>This is <italic>easier</italic> to type. Inline notes may contain