pandoc/test/command/3407.md

```
% pandoc -f native -t rst
[Para [Code ("",["interpreted-text"],[("role","foo")]) "text"]]
^D
:foo:`text`
```

```
% pandoc -f rst -t native
:foo:`text`
^D
[ Para
    [ Code
        ( "" , [ "interpreted-text" ] , [ ( "role" , "foo" ) ] )
        "text"
    ]
]
```
RST reader/writer: support unknown interpreted text roles... ...by parsing them as Span with "role" attributes. This way they can be manipulated in the AST. Closes #3407. 2017-08-18 01:01:44 +02:00			```
			`% pandoc -f native -t rst`
RST reader: improve parsing of inline interpreted text roles. * Use a Span with class "title-reference" for the default title-reference role. * Use B.text to split up contents into Spaces, SoftBreaks, and Strs for title-reference. * Use Code with class "interpreted-text" instead of Span and Str for unknown roles. (The RST writer has also been modified to round-trip this properly.) * Disallow blank lines in interpreted text. * Backslash-escape now works in interpreted text. * Backticks followed by alphanumerics no longer end interpreted text. Closes #4811. 2018-08-05 18:15:06 +02:00			`[Para [Code ("",["interpreted-text"],[("role","foo")]) "text"]]`
RST reader/writer: support unknown interpreted text roles... ...by parsing them as Span with "role" attributes. This way they can be manipulated in the AST. Closes #3407. 2017-08-18 01:01:44 +02:00			`^D`
			:foo:`text`
			```

			```
			`% pandoc -f rst -t native`
			:foo:`text`
			`^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`
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			`[ Code`
			`( "" , [ "interpreted-text" ] , [ ( "role" , "foo" ) ] )`
			`"text"`
			`]`
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			`]`
RST reader/writer: support unknown interpreted text roles... ...by parsing them as Span with "role" attributes. This way they can be manipulated in the AST. Closes #3407. 2017-08-18 01:01:44 +02:00			```