<?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 for TechComm Toolbox</title>
	<atom:link href="http://techcommtoolbox.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://techcommtoolbox.com</link>
	<description>Lists tools every technical communicator should have in their toolbox</description>
	<lastBuildDate>Mon, 06 Apr 2009 15:10:44 +0000</lastBuildDate>
	
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>Comment on Doc-To-Help 2009 by Doc-To-Help &#124; TechComm Toolbox</title>
		<link>http://techcommtoolbox.com/home/doc-to-help-2009/comment-page-1/#comment-33</link>
		<dc:creator>Doc-To-Help &#124; TechComm Toolbox</dc:creator>
		<pubDate>Mon, 06 Apr 2009 15:10:44 +0000</pubDate>
		<guid isPermaLink="false">http://techcommtoolbox.com/?page_id=1137#comment-33</guid>
		<description>[...] Doc-To-Help (click to visit our page on TechComm Toolbox)   You can follow any responses to this entry through [...]</description>
		<content:encoded><![CDATA[<p>[...] Doc-To-Help (click to visit our page on TechComm Toolbox)   You can follow any responses to this entry through [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on FAR HTML by FAR HTML &#124; TechComm Toolbox</title>
		<link>http://techcommtoolbox.com/home/far-html/comment-page-1/#comment-32</link>
		<dc:creator>FAR HTML &#124; TechComm Toolbox</dc:creator>
		<pubDate>Tue, 31 Mar 2009 23:39:55 +0000</pubDate>
		<guid isPermaLink="false">http://techcommtoolbox.com/?page_id=1115#comment-32</guid>
		<description>[...] FAR(click to visit our page on TechComm Toolbox)    You can follow any responses to this entry through [...]</description>
		<content:encoded><![CDATA[<p>[...] FAR(click to visit our page on TechComm Toolbox)    You can follow any responses to this entry through [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on HelpNDoc by HelpNDoc &#124; TechComm Toolbox</title>
		<link>http://techcommtoolbox.com/home/helpndoc/comment-page-1/#comment-31</link>
		<dc:creator>HelpNDoc &#124; TechComm Toolbox</dc:creator>
		<pubDate>Tue, 31 Mar 2009 23:15:50 +0000</pubDate>
		<guid isPermaLink="false">http://techcommtoolbox.com/?page_id=1109#comment-31</guid>
		<description>[...] Software HelpNDoc (click to visit our page on TechComm Toolbox)   You can follow any responses to this entry through [...]</description>
		<content:encoded><![CDATA[<p>[...] Software HelpNDoc (click to visit our page on TechComm Toolbox)   You can follow any responses to this entry through [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on HelpConsole 2008 by HelpConsole 2008 &#124; TechComm Toolbox</title>
		<link>http://techcommtoolbox.com/home/helpconsole-2008/comment-page-1/#comment-29</link>
		<dc:creator>HelpConsole 2008 &#124; TechComm Toolbox</dc:creator>
		<pubDate>Wed, 25 Mar 2009 18:49:43 +0000</pubDate>
		<guid isPermaLink="false">http://techcommtoolbox.com/?page_id=1101#comment-29</guid>
		<description>[...] Ease Software Inc. HelpConsole 2008   You can follow any responses to this entry through the RSS 2.0 feed.  You can leave a response, [...]</description>
		<content:encoded><![CDATA[<p>[...] Ease Software Inc. HelpConsole 2008   You can follow any responses to this entry through the RSS 2.0 feed.  You can leave a response, [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Dr. Explain by Dr. Explain &#124; TechComm Toolbox</title>
		<link>http://techcommtoolbox.com/home/dr-explain/comment-page-1/#comment-28</link>
		<dc:creator>Dr. Explain &#124; TechComm Toolbox</dc:creator>
		<pubDate>Wed, 25 Mar 2009 14:55:15 +0000</pubDate>
		<guid isPermaLink="false">http://techcommtoolbox.com/?page_id=1087#comment-28</guid>
		<description>[...] Byte Systems, LLC Dr. Explain   You can follow any responses to this entry through the RSS 2.0 feed.  You can leave a response, [...]</description>
		<content:encoded><![CDATA[<p>[...] Byte Systems, LLC Dr. Explain   You can follow any responses to this entry through the RSS 2.0 feed.  You can leave a response, [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on XMetaL by Sheila Loring</title>
		<link>http://techcommtoolbox.com/xmetal/comment-page-1/#comment-26</link>
		<dc:creator>Sheila Loring</dc:creator>
		<pubDate>Tue, 03 Mar 2009 20:39:07 +0000</pubDate>
		<guid isPermaLink="false">http://techcommtoolbox.com/?p=508#comment-26</guid>
		<description>Pros: 
XMetaL&#039;s WYSIWYG view is the best I&#039;ve found for the average author.
Inserting links to topics and graphics is easy thanks to a Browse dialog box, which Oxygen and some other editors don&#039;t have. 
You can drag and drop HTML from a browser into a document to convert it to XML.
Spell checker AND thesaurus!
Four views of a document are available -- Code (or Plain Text view), WYSIWYG (or Normal view), Tags On, and Page Preview.
Document is validated on Save.
Change tracking.
Icons in map editor indicate whether file is topic, reference, task, or concept so you don&#039;t have to open the file to see.
Creating conrefs is pretty easy.
You can choose which domains to display.
Element IDs can be auto-assigned (however, they&#039;re very long strings).

Cons:
Map editor is clunky. I want to drag and drop topics to reorder them, not use arrow buttons. (This applies to version 5.1)
The code view needs a pretty print option. It&#039;s very difficult to read the code.
You can set up certain parameters to format the output (like headers/footers and CSS or parser used), but these parameters don&#039;t appear to be documented. If they ARE documented, the documentation should be easier to find.
Implementing your own modified DITA Open Toolkit (DITA OT) could be easier. You have to layer your changes over XMetaL&#039;s DITA OT files instead of just pointing the program to your own DITA OT folder. This makes updating the DITA OT inconvenient.</description>
		<content:encoded><![CDATA[<p>Pros:<br />
XMetaL&#8217;s WYSIWYG view is the best I&#8217;ve found for the average author.<br />
Inserting links to topics and graphics is easy thanks to a Browse dialog box, which Oxygen and some other editors don&#8217;t have.<br />
You can drag and drop HTML from a browser into a document to convert it to XML.<br />
Spell checker AND thesaurus!<br />
Four views of a document are available &#8212; Code (or Plain Text view), WYSIWYG (or Normal view), Tags On, and Page Preview.<br />
Document is validated on Save.<br />
Change tracking.<br />
Icons in map editor indicate whether file is topic, reference, task, or concept so you don&#8217;t have to open the file to see.<br />
Creating conrefs is pretty easy.<br />
You can choose which domains to display.<br />
Element IDs can be auto-assigned (however, they&#8217;re very long strings).</p>
<p>Cons:<br />
Map editor is clunky. I want to drag and drop topics to reorder them, not use arrow buttons. (This applies to version 5.1)<br />
The code view needs a pretty print option. It&#8217;s very difficult to read the code.<br />
You can set up certain parameters to format the output (like headers/footers and CSS or parser used), but these parameters don&#8217;t appear to be documented. If they ARE documented, the documentation should be easier to find.<br />
Implementing your own modified DITA Open Toolkit (DITA OT) could be easier. You have to layer your changes over XMetaL&#8217;s DITA OT files instead of just pointing the program to your own DITA OT folder. This makes updating the DITA OT inconvenient.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on FrameMaker by Bill Swallow</title>
		<link>http://techcommtoolbox.com/framemaker/comment-page-1/#comment-25</link>
		<dc:creator>Bill Swallow</dc:creator>
		<pubDate>Tue, 03 Mar 2009 16:12:45 +0000</pubDate>
		<guid isPermaLink="false">http://techcommtoolbox.com/?p=244#comment-25</guid>
		<description>FrameMaker is one of my favorite print-oriented technical documentation tools, and a solid tool for single-sourcing where solid printed or PDF documentation is needed. Many people tend to look sideways at it when they first start using it, for it functions a bit differently than other print authoring tools. Many other tools focus on layout and design, where FrameMaker allows you to automate the layout via text frames on its master pages and focus on the core of technical writing: content.

What I like most about FrameMaker is how easy it is to create multi-purposed content from one linear content source. The approach is old-school; author content in chapters or blocks of related information, using headings to break the content up - a practice that is as old as book writing itself. But, it is very easy to leverage this approach to authoring well-chunked topic-based content as well.

The trick to making this seemingly linear authoring tool work in a single-source fashion is to make smart use of the many dynamic functions it provides. By leveraging multiple master pages, conditional text, variables, cross-references, and reference page elements, you can set up your content to work as a book, a Help system, a user guide, a training guide, or have it ready for multiple language translation.

FrameMaker isn&#039;t known as the most cutting edge or technically sexy tool out there, but the old saying holds true: if it ain&#039;t broke, don&#039;t fix it. I&#039;ve been successful with FrameMaker for over a decade, and don&#039;t see its usefulness disappearing any time soon.</description>
		<content:encoded><![CDATA[<p>FrameMaker is one of my favorite print-oriented technical documentation tools, and a solid tool for single-sourcing where solid printed or PDF documentation is needed. Many people tend to look sideways at it when they first start using it, for it functions a bit differently than other print authoring tools. Many other tools focus on layout and design, where FrameMaker allows you to automate the layout via text frames on its master pages and focus on the core of technical writing: content.</p>
<p>What I like most about FrameMaker is how easy it is to create multi-purposed content from one linear content source. The approach is old-school; author content in chapters or blocks of related information, using headings to break the content up &#8211; a practice that is as old as book writing itself. But, it is very easy to leverage this approach to authoring well-chunked topic-based content as well.</p>
<p>The trick to making this seemingly linear authoring tool work in a single-source fashion is to make smart use of the many dynamic functions it provides. By leveraging multiple master pages, conditional text, variables, cross-references, and reference page elements, you can set up your content to work as a book, a Help system, a user guide, a training guide, or have it ready for multiple language translation.</p>
<p>FrameMaker isn&#8217;t known as the most cutting edge or technically sexy tool out there, but the old saying holds true: if it ain&#8217;t broke, don&#8217;t fix it. I&#8217;ve been successful with FrameMaker for over a decade, and don&#8217;t see its usefulness disappearing any time soon.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Twitter by Rahel Bailie</title>
		<link>http://techcommtoolbox.com/twitter/comment-page-1/#comment-23</link>
		<dc:creator>Rahel Bailie</dc:creator>
		<pubDate>Wed, 21 Jan 2009 16:33:23 +0000</pubDate>
		<guid isPermaLink="false">http://techcommtoolbox.com/?p=474#comment-23</guid>
		<description>I think microblogging and related sites should be in a completely different category than sites such as TechComm eServer, which I think of as more of a knowledge base site.</description>
		<content:encoded><![CDATA[<p>I think microblogging and related sites should be in a completely different category than sites such as TechComm eServer, which I think of as more of a knowledge base site.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on WebWorks ePublisher by Alan J. Porter</title>
		<link>http://techcommtoolbox.com/webworks-epublisher/comment-page-1/#comment-11</link>
		<dc:creator>Alan J. Porter</dc:creator>
		<pubDate>Sun, 11 Jan 2009 16:33:16 +0000</pubDate>
		<guid isPermaLink="false">http://techcommtoolbox.com/?p=320#comment-11</guid>
		<description>Thanks for listing WebWorks ePublisher on your excellent site. This is a great resource for Technical Communicators. 

Thanks</description>
		<content:encoded><![CDATA[<p>Thanks for listing WebWorks ePublisher on your excellent site. This is a great resource for Technical Communicators. </p>
<p>Thanks</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Bill Swallow by Bill Swallow &#124; TechComm Toolbox</title>
		<link>http://techcommtoolbox.com/home/bill-swallow/comment-page-1/#comment-10</link>
		<dc:creator>Bill Swallow &#124; TechComm Toolbox</dc:creator>
		<pubDate>Sun, 11 Jan 2009 16:32:36 +0000</pubDate>
		<guid isPermaLink="false">http://techcommtoolbox.com/?page_id=987#comment-10</guid>
		<description>[...] Bill Swallow   You can follow any responses to this entry through the RSS 2.0 feed.  You can leave a response, or trackback from your own site.  Tags: Bill Swallow [...]</description>
		<content:encoded><![CDATA[<p>[...] Bill Swallow   You can follow any responses to this entry through the RSS 2.0 feed.  You can leave a response, or trackback from your own site.  Tags: Bill Swallow [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
