<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Rants &amp; Ponderings on Perlkönig</title>
    <link>/categories/rants-ponderings/</link>
    <description>Recent content in Rants &amp; Ponderings on Perlkönig</description>
    <generator>Hugo -- gohugo.io</generator>
    <copyright>Copyright © 2006-{year} Aaron Dalton. All Rights Reserved.</copyright>
    <lastBuildDate>Fri, 15 Jun 2012 00:00:00 +0000</lastBuildDate><atom:link href="/categories/rants-ponderings/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Editing/Publishing Rant and Mission</title>
      <link>/posts/editingpublishing-rant-and-mission/</link>
      <pubDate>Fri, 15 Jun 2012 00:00:00 +0000</pubDate>
      
      <guid>/posts/editingpublishing-rant-and-mission/</guid>
      <description>Just to clarify, this rant is intended for people interested in professional document production.
My new life’s mission is to convince the publishing world to move to a plain-text-based, XML workflow. Here’s the dirty little secret: InDesign(and even, *sighs*, QuarkXpress) is no harder to learn than Word. In many ways it’s far easier. The problem is that Word seems at first glance to be powerful enough for real publishing needs, but as soon as you actually sit down and try to compose anything longer or more complex than a letter to mom, it sinks in how limited it is.</description>
    </item>
    
  </channel>
</rss>
