<feed xmlns='http://www.w3.org/2005/Atom'>
<title>pandoc/test/writer.markdown, 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-21T19:37:42Z</updated>
<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>Markdown writer: default to using ATX headings.</title>
<updated>2020-11-15T05:33:32Z</updated>
<author>
<name>Aner Lucero</name>
<email>4rgento@gmail.com</email>
</author>
<published>2020-11-14T23:09:44Z</published>
<link rel='alternate' type='text/html' href='https://git.pashev.ru/pandoc/commit/?id=f63b76e1698b0d7eba6b43ef45faaeee2b01b9ca'/>
<id>urn:sha1:f63b76e1698b0d7eba6b43ef45faaeee2b01b9ca</id>
<content type='text'>
Previously we used Setext (underlined) headings by default.
The default is now ATX (`##` style).

* Add the `--markdown-headings=atx|setext` option.
* Deprecate `--atx-headers`.
* Add constructor 'ATXHeadingInLHS` constructor to `LogMessage` [API change].
* Support `markdown-headings` in defaults files.
* Document new options in MANUAL.

Closes #6662.
</content>
</entry>
<entry>
<title>Be less aggressive about using quotes for YAML values.</title>
<updated>2020-10-08T17:54:53Z</updated>
<author>
<name>John MacFarlane</name>
<email>jgm@berkeley.edu</email>
</author>
<published>2020-10-08T17:54:16Z</published>
<link rel='alternate' type='text/html' href='https://git.pashev.ru/pandoc/commit/?id=641849b70a851c45ce3d3fb438eeee7fd813d070'/>
<id>urn:sha1:641849b70a851c45ce3d3fb438eeee7fd813d070</id>
<content type='text'>
We need quotes if `[` or `{` or `'` is at the beginning of
the line, but not otherwise.
</content>
</entry>
<entry>
<title>Use double quotes for YAML metadata.</title>
<updated>2020-10-08T06:05:51Z</updated>
<author>
<name>John MacFarlane</name>
<email>jgm@berkeley.edu</email>
</author>
<published>2020-10-08T06:03:14Z</published>
<link rel='alternate' type='text/html' href='https://git.pashev.ru/pandoc/commit/?id=1be0f0fba8d860b960e79442a891fce6b1aca192'/>
<id>urn:sha1:1be0f0fba8d860b960e79442a891fce6b1aca192</id>
<content type='text'>
Closes #6727.
</content>
</entry>
<entry>
<title>Markdown writer: avoid unnecessary escapes before intraword `_`</title>
<updated>2020-04-18T05:42:21Z</updated>
<author>
<name>John MacFarlane</name>
<email>jgm@berkeley.edu</email>
</author>
<published>2020-04-18T05:42:21Z</published>
<link rel='alternate' type='text/html' href='https://git.pashev.ru/pandoc/commit/?id=9a809d4d01f1a9cba4401e98d95cccf8a0ec7e75'/>
<id>urn:sha1:9a809d4d01f1a9cba4401e98d95cccf8a0ec7e75</id>
<content type='text'>
when `intraword_underscores` extension is enabled.
Closes #6296.
</content>
</entry>
<entry>
<title>Markdown writer: prefer using raw_attribute when enabled.</title>
<updated>2019-07-19T05:31:03Z</updated>
<author>
<name>John MacFarlane</name>
<email>jgm@berkeley.edu</email>
</author>
<published>2019-07-19T05:30:05Z</published>
<link rel='alternate' type='text/html' href='https://git.pashev.ru/pandoc/commit/?id=28cad165179378369fcf4d25656ea28357026baa'/>
<id>urn:sha1:28cad165179378369fcf4d25656ea28357026baa</id>
<content type='text'>
The `raw_attribute` will be used to mark raw bits, even HTML
and LaTeX, and even when `raw_html` and `raw_tex` are enabled,
as they are by default.

To get the old behavior, disable `raw_attribute` in the writer.

Closes #4311.
</content>
</entry>
<entry>
<title>Shared.compactify: Avoid mixed lists.</title>
<updated>2019-02-26T01:33:54Z</updated>
<author>
<name>John MacFarlane</name>
<email>jgm@berkeley.edu</email>
</author>
<published>2019-02-23T22:40:06Z</published>
<link rel='alternate' type='text/html' href='https://git.pashev.ru/pandoc/commit/?id=ba05e1ea02d5227796f12dea2404285300021de6'/>
<id>urn:sha1:ba05e1ea02d5227796f12dea2404285300021de6</id>
<content type='text'>
This improves on the original fix to #5285 by preventing
other mixed lists (lists with a mix of Plain and Para
elements) that were allowed given the original fix.
</content>
</entry>
<entry>
<title>Markdown writer: ensure blank between raw block and normal content.</title>
<updated>2018-10-15T00:12:06Z</updated>
<author>
<name>John MacFarlane</name>
<email>jgm@berkeley.edu</email>
</author>
<published>2018-10-15T00:12:06Z</published>
<link rel='alternate' type='text/html' href='https://git.pashev.ru/pandoc/commit/?id=88faa45f1d294690ad97b7f45a75c89c65227cf1'/>
<id>urn:sha1:88faa45f1d294690ad97b7f45a75c89c65227cf1</id>
<content type='text'>
Otherwise a raw block can prevent a paragraph from being
recognized as such.

Closes #4629.
</content>
</entry>
<entry>
<title>Markdown writer: better escaping of `&lt;` and `&gt;`.</title>
<updated>2017-07-30T20:45:22Z</updated>
<author>
<name>John MacFarlane</name>
<email>jgm@berkeley.edu</email>
</author>
<published>2017-07-30T20:45:22Z</published>
<link rel='alternate' type='text/html' href='https://git.pashev.ru/pandoc/commit/?id=b8afec05e0ce85ab811bf55d4948be768ad363e2'/>
<id>urn:sha1:b8afec05e0ce85ab811bf55d4948be768ad363e2</id>
<content type='text'>
If `all_symbols_escapable` is set, we backslash escape these.
Otherwise we use entities as before.
</content>
</entry>
<entry>
<title>Added `spaced_reference_links` extension.</title>
<updated>2017-05-25T10:57:31Z</updated>
<author>
<name>John MacFarlane</name>
<email>jgm@berkeley.edu</email>
</author>
<published>2017-05-25T10:50:43Z</published>
<link rel='alternate' type='text/html' href='https://git.pashev.ru/pandoc/commit/?id=708973a33a0ce425bb21a5ffa06fbdab465d3fb8'/>
<id>urn:sha1:708973a33a0ce425bb21a5ffa06fbdab465d3fb8</id>
<content type='text'>
This is now the default for pandoc's Markdown.
It allows whitespace between the two parts of a
reference link:  e.g.

    [a] [b]

    [b]: url

This is now forbidden by default.

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