<?xml version="1.0" encoding="utf-8"?>
<?xml-stylesheet type="text/xsl" href="../assets/xml/rss.xsl" media="all"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>KHE (Posts about pandoc)</title><link>https://east.fm/</link><description></description><atom:link href="https://east.fm/categories/pandoc.xml" rel="self" type="application/rss+xml"></atom:link><language>en</language><lastBuildDate>Fri, 26 Oct 2018 22:16:52 GMT</lastBuildDate><generator>Nikola (getnikola.com)</generator><docs>http://blogs.law.harvard.edu/tech/rss</docs><item><title>Using Pandoc with Problematic UTF-8 Files</title><link>https://east.fm/posts/pandoc-with-problematic-utf-8-files/index.html</link><dc:creator>Kenneth H. East</dc:creator><description>&lt;div&gt;&lt;p&gt;I recently used &lt;tt class="docutils literal"&gt;pandoc&lt;/tt&gt; to convert some &lt;tt class="docutils literal"&gt;html&lt;/tt&gt; files to &lt;tt class="docutils literal"&gt;reST&lt;/tt&gt;.
Initially, there were numerous errors about invalid characters. Here is the
brute-force solution I arrived at to get the job done while attempting to
reasonably convert offending characters into something reasonable.&lt;/p&gt;
&lt;p&gt;&lt;a href="https://east.fm/posts/pandoc-with-problematic-utf-8-files/index.html"&gt;Read more…&lt;/a&gt; (1 min remaining to read)&lt;/p&gt;&lt;/div&gt;</description><category>pandoc</category><category>utf-8</category><guid>https://east.fm/posts/pandoc-with-problematic-utf-8-files/index.html</guid><pubDate>Fri, 20 Jul 2012 05:00:00 GMT</pubDate></item></channel></rss>