<?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 rest)</title><link>https://east.fm/</link><description></description><atom:link href="https://east.fm/categories/rest.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>Converting MS Word DOCX Document to reStructuredText</title><link>https://east.fm/posts/converting-ms-word-docx-document-to-restructuredtext/index.html</link><dc:creator>Kenneth H. East</dc:creator><description>&lt;div&gt;&lt;p&gt;A client has a substantial body of written work that began
life as MS Word documents.  They also created many derivative
documents in various formats (including HTML, PDF, Dreamweaver, MS
Front Page, etc.) for different use cases.  Our recommendation was
that, going forward, they should create content once, in a canonical
format, from which they could generate documents in whatever format
they need(HTML, PDF, etc.).  That subject is beyond the scope of this
note.  This note is focused on a quick and dirty method to access
their assets in MS Word format and convert them into something more
widely useful.&lt;/p&gt;
&lt;p&gt;&lt;a href="https://east.fm/posts/converting-ms-word-docx-document-to-restructuredtext/index.html"&gt;Read more…&lt;/a&gt; (1 min remaining to read)&lt;/p&gt;&lt;/div&gt;</description><category>rest</category><category>word</category><guid>https://east.fm/posts/converting-ms-word-docx-document-to-restructuredtext/index.html</guid><pubDate>Sat, 09 Jun 2012 05:00:00 GMT</pubDate></item></channel></rss>