<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Export on The Lone C++ Coder's Blog</title><link>https://www.lonecpluspluscoder.com/tags/export/</link><description>Recent content in Export on The Lone C++ Coder's Blog</description><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Wed, 25 Aug 2021 21:00:00 -0500</lastBuildDate><atom:link href="https://www.lonecpluspluscoder.com/tags/export/index.xml" rel="self" type="application/rss+xml"/><item><title>TIL that org-mode has an exporter for ODT</title><link>https://www.lonecpluspluscoder.com/2021/08/25/til-org-mode-odt-exporter/</link><pubDate>Wed, 25 Aug 2021 21:00:00 -0500</pubDate><author>Timo Geusch</author><guid>https://www.lonecpluspluscoder.com/2021/08/25/til-org-mode-odt-exporter/</guid><description>&lt;p>I&amp;rsquo;m by no means an Emacs &lt;a href="https://orgmode.org">org-mode&lt;/a> power user - in fact, anything but - but I do use org-mode a lot for note taking and also when I need an outliner to try and arrange ideas in a suitable manner. It excels at both, and usually does what I need including exporting to HTML. Exporting to HTML covers about 90% of my use cases. As much as I&amp;rsquo;d like to, LaTeX does not feature in my needs, but I needed to export an org-mode file for use with Microsoft Word. While there is no exporter directing into docx format, Microsoft Word can read ODT (OpenDocument Text) and guess what, org-mode does include an exporter for ODT. Problem solved, and I hope this information helps if you&amp;rsquo;re running into the same problem.&lt;/p></description></item><item><title>Cleaning up UTF-8 character entities when exporting from WordPress to Jekyll</title><link>https://www.lonecpluspluscoder.com/2017/08/27/getting-rid-of-utf-8-character-entities-when-exporting-to-jekyll/</link><pubDate>Sun, 27 Aug 2017 12:00:00 +0000</pubDate><author>Timo Geusch</author><guid>https://www.lonecpluspluscoder.com/2017/08/27/getting-rid-of-utf-8-character-entities-when-exporting-to-jekyll/</guid><description>&lt;p>I&amp;rsquo;ve been experimenting with converting this blog to &lt;a href="http://jekyllrb.com/">Jekyll&lt;/a> or another static blog generator. I&amp;rsquo;m sticking with Jekyll at the moment due to its ease of use and its plugin environment. The main idea behind this is to reduce the resource consumption and hopefully also speed up the delivery of the blog. In fact, there is a &lt;a href="http://static.lonecpluspluscoder.com/">static version of the blog&lt;/a> available right now, even though it&amp;rsquo;s kinda pre-alpha and not always up to date. The Jekyll version also doesn&amp;rsquo;t have the comments set up yet nor does it have a theme I like, so it&amp;rsquo;s still very much work in slow progress.&lt;/p>
&lt;p>To export the contents from WordPress to Jekyll I use the surprisingly named &lt;a href="https://wordpress.org/plugins/jekyll-exporter/">WordPress to Jekyll exporter&lt;/a> plugin. This plugin dumps the whole WordPress data including pictures into a zip file in a format that is mostly markdown grokked by Jekyll. It doesn&amp;rsquo;t convert all the links to markdown, so the generated files need some manual cleanup. One problem I keep running into is that the exporter dumps out certain UTF-8 character entities as their numerical code. Unfortunately when processing the data with Jekyll afterwards, those UTF-8 entities get turned into strings that are displayed as is. Please note I&amp;rsquo;m not complaining about this functionality, I&amp;rsquo;d rather have this information preserved so I can rework it later on. So I wrote a script to help with this task.&lt;/p></description></item></channel></rss>