<feed xmlns='http://www.w3.org/2005/Atom'>
<title>pandoc/test/rtf, branch master</title>
<subtitle>Conversion between markup formats</subtitle>
<id>https://git.pashev.ru/pandoc/atom?h=master</id>
<link rel='self' href='https://git.pashev.ru/pandoc/atom?h=master'/>
<link rel='alternate' type='text/html' href='https://git.pashev.ru/pandoc/'/>
<updated>2021-09-29T04:17:53Z</updated>
<entry>
<title>Switch from pretty-simple to pretty-show for native output.</title>
<updated>2021-09-29T04:17:53Z</updated>
<author>
<name>John MacFarlane</name>
<email>jgm@berkeley.edu</email>
</author>
<published>2021-09-29T04:17:53Z</published>
<link rel='alternate' type='text/html' href='https://git.pashev.ru/pandoc/commit/?id=0bdcf415e4eff83ad8e35c1d41c8a28e0bbd5da1'/>
<id>urn:sha1:0bdcf415e4eff83ad8e35c1d41c8a28e0bbd5da1</id>
<content type='text'>
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.
</content>
</entry>
<entry>
<title>Use pretty-simple to format native output.</title>
<updated>2021-09-21T19:37:42Z</updated>
<author>
<name>John MacFarlane</name>
<email>jgm@berkeley.edu</email>
</author>
<published>2021-09-19T19:09:51Z</published>
<link rel='alternate' type='text/html' href='https://git.pashev.ru/pandoc/commit/?id=c266734448544a118ed80e47deaa2590131c7f84'/>
<id>urn:sha1:c266734448544a118ed80e47deaa2590131c7f84</id>
<content type='text'>
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.)
</content>
</entry>
<entry>
<title>RTF reader: better handling of `\*` and bookmarks.</title>
<updated>2021-09-04T18:06:01Z</updated>
<author>
<name>John MacFarlane</name>
<email>jgm@berkeley.edu</email>
</author>
<published>2021-09-04T17:02:38Z</published>
<link rel='alternate' type='text/html' href='https://git.pashev.ru/pandoc/commit/?id=b185560a8ec1fd8a0b578de4d94ea72a3d3e2943'/>
<id>urn:sha1:b185560a8ec1fd8a0b578de4d94ea72a3d3e2943</id>
<content type='text'>
We now ensure that groups starting with `\*` never cause
text to be added to the document.

In addition, bookmarks now create a span between the start
and end of the bookmark, rather than an empty span.
</content>
</entry>
<entry>
<title>Add test for #7488.</title>
<updated>2021-08-10T18:11:33Z</updated>
<author>
<name>John MacFarlane</name>
<email>jgm@berkeley.edu</email>
</author>
<published>2021-08-10T18:11:33Z</published>
<link rel='alternate' type='text/html' href='https://git.pashev.ru/pandoc/commit/?id=7ca4233793f3ba42b2c79c3526a4ab2664fea2e2'/>
<id>urn:sha1:7ca4233793f3ba42b2c79c3526a4ab2664fea2e2</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Add RTF reader.</title>
<updated>2021-08-10T17:48:55Z</updated>
<author>
<name>John MacFarlane</name>
<email>jgm@berkeley.edu</email>
</author>
<published>2021-07-30T23:23:46Z</published>
<link rel='alternate' type='text/html' href='https://git.pashev.ru/pandoc/commit/?id=6543b05116ee58ef4de62f93dcafeb27617d83e6'/>
<id>urn:sha1:6543b05116ee58ef4de62f93dcafeb27617d83e6</id>
<content type='text'>
- `rtf` is now supported as an input format as well as output.
- New module Text.Pandoc.Readers.RTF (exporting `readRTF`). [API change]

Closes #3982.
</content>
</entry>
</feed>
