pandoc/test/command/5360.md

```
% pandoc -t native
::: {.foo}
<table>
 <tr>
  <td>hi</td>
 </tr>
</table>
:::
^D
[ Div
    ( "" , [ "foo" ] , [] )
    [ RawBlock (Format "html") "<table>"
    , RawBlock (Format "html") "<tr>"
    , RawBlock (Format "html") "<td>"
    , Plain [ Str "hi" ]
    , RawBlock (Format "html") "</td>"
    , RawBlock (Format "html") "</tr>"
    , RawBlock (Format "html") "</table>"
    ]
]
```
Fix parsing bug affected indented code after raw HTML. Closes #6009, #5360. 2019-12-27 20:46:22 +01:00			```
			`% pandoc -t native`
			`::: {.foo}`
			`<table>`
			`<tr>`
			`<td>hi</td>`
			`</tr>`
			`</table>`
			`:::`
			`^D`
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.) 2021-09-19 21:09:51 +02:00			`[ Div`
Switch from pretty-simple to pretty-show for native output. 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-29 06:17:53 +02:00			`( "" , [ "foo" ] , [] )`
			`[ RawBlock (Format "html") "<table>"`
			`, RawBlock (Format "html") "<tr>"`
			`, RawBlock (Format "html") "<td>"`
			`, Plain [ Str "hi" ]`
			`, RawBlock (Format "html") "</td>"`
			`, RawBlock (Format "html") "</tr>"`
			`, RawBlock (Format "html") "</table>"`
			`]`
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.) 2021-09-19 21:09:51 +02:00			`]`
Fix parsing bug affected indented code after raw HTML. Closes #6009, #5360. 2019-12-27 20:46:22 +01:00			```