<?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"
	>
<channel>
	<title>Comments on: Six Reasons to love Flare</title>
	<atom:link href="http://blog.paulpehrson.com/2007/06/18/six-resons-to-love-flare/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.paulpehrson.com/2007/06/18/six-resons-to-love-flare/</link>
	<description>Paul Pehrson's technical writing blog</description>
	<pubDate>Thu, 28 Aug 2008 06:30:24 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6</generator>
		<item>
		<title>By: Douglas K. Beagley</title>
		<link>http://blog.paulpehrson.com/2007/06/18/six-resons-to-love-flare/#comment-56303</link>
		<dc:creator>Douglas K. Beagley</dc:creator>
		<pubDate>Tue, 06 May 2008 15:25:06 +0000</pubDate>
		<guid isPermaLink="false">http://blog.paulpehrson.com/2007/06/18/six-resons-to-love-flare/#comment-56303</guid>
		<description>Hi,
Your post is wonderful, and it points to many things I am looking for in a program. Right now, I write all of my documentation in vi, complete with DocBook tags, and then compile it into PDF and HTML outputs. But I don't have the kind of control I want over design and layout.

We need to produce attractive PDF manuals, HTML versions of the same, help files, and training videos. So I've been investigating ATCS and MadCap's offerings. I would appreciate any resources or suggestions you have that might help me make the best decision. I am nervous about the MadCap suite for its youth and lack of broad acceptance, and nervous about ATCS for its impression of bloatware and questionable standards support. I do like its DITA push, however.

Anyway... keep writing awesome posts!</description>
		<content:encoded><![CDATA[<p>Hi,<br />
Your post is wonderful, and it points to many things I am looking for in a program. Right now, I write all of my documentation in vi, complete with DocBook tags, and then compile it into PDF and HTML outputs. But I don&#8217;t have the kind of control I want over design and layout.</p>
<p>We need to produce attractive PDF manuals, HTML versions of the same, help files, and training videos. So I&#8217;ve been investigating ATCS and MadCap&#8217;s offerings. I would appreciate any resources or suggestions you have that might help me make the best decision. I am nervous about the MadCap suite for its youth and lack of broad acceptance, and nervous about ATCS for its impression of bloatware and questionable standards support. I do like its DITA push, however.</p>
<p>Anyway&#8230; keep writing awesome posts!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ITauthor &#187; Blog Archive &#187; Flare pros and cons</title>
		<link>http://blog.paulpehrson.com/2007/06/18/six-resons-to-love-flare/#comment-54434</link>
		<dc:creator>ITauthor &#187; Blog Archive &#187; Flare pros and cons</dc:creator>
		<pubDate>Sat, 08 Mar 2008 22:39:13 +0000</pubDate>
		<guid isPermaLink="false">http://blog.paulpehrson.com/2007/06/18/six-resons-to-love-flare/#comment-54434</guid>
		<description>[...] Six Reasons to Love Flare [...]</description>
		<content:encoded><![CDATA[<p>[...] Six Reasons to Love Flare [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Madcap Flare, Madcap Software, and Online Help -- Podcast Interview with Paul Pehrson, MVP in Madcap Flare Forums &#124; I'd Rather Be Writing</title>
		<link>http://blog.paulpehrson.com/2007/06/18/six-resons-to-love-flare/#comment-49888</link>
		<dc:creator>Madcap Flare, Madcap Software, and Online Help -- Podcast Interview with Paul Pehrson, MVP in Madcap Flare Forums &#124; I'd Rather Be Writing</dc:creator>
		<pubDate>Tue, 22 Jan 2008 13:45:27 +0000</pubDate>
		<guid isPermaLink="false">http://blog.paulpehrson.com/2007/06/18/six-resons-to-love-flare/#comment-49888</guid>
		<description>[...] Six Reasons to Love Flare [...]</description>
		<content:encoded><![CDATA[<p>[...] Six Reasons to Love Flare [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Judy</title>
		<link>http://blog.paulpehrson.com/2007/06/18/six-resons-to-love-flare/#comment-41677</link>
		<dc:creator>Judy</dc:creator>
		<pubDate>Fri, 19 Oct 2007 18:46:53 +0000</pubDate>
		<guid isPermaLink="false">http://blog.paulpehrson.com/2007/06/18/six-resons-to-love-flare/#comment-41677</guid>
		<description>Question about Flare... 
Is there a way to add a generic "previous topic" and "next topic" hyperlink to a master page? 

(Previously, we ran our FM docs thru Webworks, which added a previous and next buton to the top and bottom of each page. These were, of course, connected to the previous and next topics.)</description>
		<content:encoded><![CDATA[<p>Question about Flare&#8230;<br />
Is there a way to add a generic &#8220;previous topic&#8221; and &#8220;next topic&#8221; hyperlink to a master page? </p>
<p>(Previously, we ran our FM docs thru Webworks, which added a previous and next buton to the top and bottom of each page. These were, of course, connected to the previous and next topics.)</p>
]]></content:encoded>
	</item>
</channel>
</rss>
