pandoc/test/command/3257.md

```
% pandoc -t native
(i<j)
^D
[ Para [ Str "(i<j)" ] ]
```

```
% pandoc -t native
i<j-1, j>k
^D
[ Para [ Str "i<j-1," , Space , Str "j>k" ] ]
```
HTML reader: Better sanity checks on raw HTML. This also affects the Markdown reader. Closes #3257. 2017-03-18 22:43:57 +01:00			```
			`% pandoc -t native`
			`(i<j)`
			`^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			`[ Para [ Str "(i<j)" ] ]`
HTML reader: Better sanity checks on raw HTML. This also affects the Markdown reader. Closes #3257. 2017-03-18 22:43:57 +01:00			```

			```
			`% pandoc -t native`
			`i<j-1, j>k`
			`^D`
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			`[ Para [ Str "i<j-1," , Space , Str "j>k" ] ]`
HTML reader: Better sanity checks on raw HTML. This also affects the Markdown reader. Closes #3257. 2017-03-18 22:43:57 +01:00			```