<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Building a new technical documentation tool chain</title>
	<atom:link href="http://www.stevestreeting.com/2010/03/07/building-a-new-technical-documentation-tool-chain/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.stevestreeting.com/2010/03/07/building-a-new-technical-documentation-tool-chain/</link>
	<description>Man bites Ogre</description>
	<lastBuildDate>Fri, 10 Feb 2012 05:35:41 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.4</generator>
	<item>
		<title>By: Steve</title>
		<link>http://www.stevestreeting.com/2010/03/07/building-a-new-technical-documentation-tool-chain/comment-page-1/#comment-287406</link>
		<dc:creator>Steve</dc:creator>
		<pubDate>Sat, 06 Nov 2010 10:58:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.stevestreeting.com/?p=2592#comment-287406</guid>
		<description>Thanks Francis, it&#039;s interesting to see the Pygment route which I never got around to exploring.</description>
		<content:encoded><![CDATA[<p>Thanks Francis, it&#8217;s interesting to see the Pygment route which I never got around to exploring.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Francis Shanahan</title>
		<link>http://www.stevestreeting.com/2010/03/07/building-a-new-technical-documentation-tool-chain/comment-page-1/#comment-287258</link>
		<dc:creator>Francis Shanahan</dc:creator>
		<pubDate>Fri, 05 Nov 2010 18:21:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.stevestreeting.com/?p=2592#comment-287258</guid>
		<description>Thanks Steve, this helped a lot. I documented my setup with Graphviz and Pygment for my own future reference and some updated versions of other software here: 

http://francisshanahan.com/index.php/2010/setup-asciidoc-fop-pygment-on-windows/

Thanks again, 
fs</description>
		<content:encoded><![CDATA[<p>Thanks Steve, this helped a lot. I documented my setup with Graphviz and Pygment for my own future reference and some updated versions of other software here: </p>
<p><a href="http://francisshanahan.com/index.php/2010/setup-asciidoc-fop-pygment-on-windows/" rel="nofollow">http://francisshanahan.com/index.php/2010/setup-asciidoc-fop-pygment-on-windows/</a></p>
<p>Thanks again,<br />
fs</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steve</title>
		<link>http://www.stevestreeting.com/2010/03/07/building-a-new-technical-documentation-tool-chain/comment-page-1/#comment-269097</link>
		<dc:creator>Steve</dc:creator>
		<pubDate>Tue, 16 Mar 2010 10:14:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.stevestreeting.com/?p=2592#comment-269097</guid>
		<description>No, but the output looks quite nice. Still, I do still like the ability to go via DocBook.</description>
		<content:encoded><![CDATA[<p>No, but the output looks quite nice. Still, I do still like the ability to go via DocBook.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andy</title>
		<link>http://www.stevestreeting.com/2010/03/07/building-a-new-technical-documentation-tool-chain/comment-page-1/#comment-269072</link>
		<dc:creator>Andy</dc:creator>
		<pubDate>Tue, 16 Mar 2010 02:03:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.stevestreeting.com/?p=2592#comment-269072</guid>
		<description>Did you happen to look at Sphinx at all (http://sphinx.pocoo.org/) ??</description>
		<content:encoded><![CDATA[<p>Did you happen to look at Sphinx at all (<a href="http://sphinx.pocoo.org/" rel="nofollow">http://sphinx.pocoo.org/</a>) ??</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steve</title>
		<link>http://www.stevestreeting.com/2010/03/07/building-a-new-technical-documentation-tool-chain/comment-page-1/#comment-268580</link>
		<dc:creator>Steve</dc:creator>
		<pubDate>Tue, 09 Mar 2010 10:16:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.stevestreeting.com/?p=2592#comment-268580</guid>
		<description>I hadn&#039;t seen quickbook before, was quite hard to find even in Google unless you knew it was in Boost. Looking at it, I prefer AsciiDoc; the syntax is a bit nicer and AsciiDoc appears to be more regularly maintained.</description>
		<content:encoded><![CDATA[<p>I hadn&#8217;t seen quickbook before, was quite hard to find even in Google unless you knew it was in Boost. Looking at it, I prefer AsciiDoc; the syntax is a bit nicer and AsciiDoc appears to be more regularly maintained.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: OvermindDL1</title>
		<link>http://www.stevestreeting.com/2010/03/07/building-a-new-technical-documentation-tool-chain/comment-page-1/#comment-268567</link>
		<dc:creator>OvermindDL1</dc:creator>
		<pubDate>Tue, 09 Mar 2010 02:46:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.stevestreeting.com/?p=2592#comment-268567</guid>
		<description>Oh, and yes Quick/BoostBook uses a Wiki-style syntax for the initial formatting, *FAR* easier to use then XML obviously.</description>
		<content:encoded><![CDATA[<p>Oh, and yes Quick/BoostBook uses a Wiki-style syntax for the initial formatting, *FAR* easier to use then XML obviously.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: OvermindDL1</title>
		<link>http://www.stevestreeting.com/2010/03/07/building-a-new-technical-documentation-tool-chain/comment-page-1/#comment-268566</link>
		<dc:creator>OvermindDL1</dc:creator>
		<pubDate>Tue, 09 Mar 2010 02:39:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.stevestreeting.com/?p=2592#comment-268566</guid>
		<description>I am curious, have you not looked at quickbook?  It is based on docbook with lots of bug fixes, a heavy emphasis on C++, doxygen integration, PDF/HTML/others output, etc...  It is part of Boost (which you are already using in OGRE), and boost has a subproject called boostbook (specialized boost formatting and such for a universal look-n-feel for all projects in boost) that you can easily rip from.  They encourage its use.  Have you not looked it?

Boost.ASIO docs use just about every possible feature if you want a good example.</description>
		<content:encoded><![CDATA[<p>I am curious, have you not looked at quickbook?  It is based on docbook with lots of bug fixes, a heavy emphasis on C++, doxygen integration, PDF/HTML/others output, etc&#8230;  It is part of Boost (which you are already using in OGRE), and boost has a subproject called boostbook (specialized boost formatting and such for a universal look-n-feel for all projects in boost) that you can easily rip from.  They encourage its use.  Have you not looked it?</p>
<p>Boost.ASIO docs use just about every possible feature if you want a good example.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steve</title>
		<link>http://www.stevestreeting.com/2010/03/07/building-a-new-technical-documentation-tool-chain/comment-page-1/#comment-268538</link>
		<dc:creator>Steve</dc:creator>
		<pubDate>Mon, 08 Mar 2010 16:01:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.stevestreeting.com/?p=2592#comment-268538</guid>
		<description>@Nicholas: yeah, the stylesheet link was buried a little there. I&#039;ve edited that section and hopefully made it more useful.

@Stodge: no problem!

I successfully followed my own instructions here to get the same tool chain working on Mac OS X (I just added a couple of clarifications such as using &#039;:&#039; instead of &#039;;&#039; to separate classpath entries). It works like a charm! I have no reason to believe it wouldn&#039;t work the same on Linux too.</description>
		<content:encoded><![CDATA[<p>@Nicholas: yeah, the stylesheet link was buried a little there. I&#8217;ve edited that section and hopefully made it more useful.</p>
<p>@Stodge: no problem!</p>
<p>I successfully followed my own instructions here to get the same tool chain working on Mac OS X (I just added a couple of clarifications such as using &#8216;:&#8217; instead of &#8216;;&#8217; to separate classpath entries). It works like a charm! I have no reason to believe it wouldn&#8217;t work the same on Linux too.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stodge</title>
		<link>http://www.stevestreeting.com/2010/03/07/building-a-new-technical-documentation-tool-chain/comment-page-1/#comment-268537</link>
		<dc:creator>Stodge</dc:creator>
		<pubDate>Mon, 08 Mar 2010 15:42:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.stevestreeting.com/?p=2592#comment-268537</guid>
		<description>Awesome - thanks for this. May be useful to us at work...</description>
		<content:encoded><![CDATA[<p>Awesome &#8211; thanks for this. May be useful to us at work&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nicholas</title>
		<link>http://www.stevestreeting.com/2010/03/07/building-a-new-technical-documentation-tool-chain/comment-page-1/#comment-268478</link>
		<dc:creator>Nicholas</dc:creator>
		<pubDate>Sun, 07 Mar 2010 17:27:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.stevestreeting.com/?p=2592#comment-268478</guid>
		<description>I get it.. style (as in bold/italic, etc.) is applied by importing the docbook transforms (aka stylesheets) into a custom transform (fo_steve.xsl). I zapped over your fo_steve.xsl.txt link!</description>
		<content:encoded><![CDATA[<p>I get it.. style (as in bold/italic, etc.) is applied by importing the docbook transforms (aka stylesheets) into a custom transform (fo_steve.xsl). I zapped over your fo_steve.xsl.txt link!</p>
]]></content:encoded>
	</item>
</channel>
</rss>

