<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
	<title>Articles&gt;Editing&gt;Software</title>	<link>http://tc.eserver.org/dir/Articles/Editing/Software</link>
	<description>A listing of the most recently indexed works about Articles and Editing and Software in the field of technical communication.</description>
	<language>en-us</language>
	<copyright>Copyright (c) 2005-08 by the EServer. All rights reserved.</copyright>
	<managingEditor>tclib-editorial@eserver.org (TC Library Editorial Board)</managingEditor>
	<webMaster>webmaster@eserver.org (Geoffrey Sauer)</webMaster>
	<image>
		<url>http://tc.eserver.org/images/newlogo.gif</url>
		<title>Articles&gt;Editing&gt;Software</title>
		<link>http://tc.eserver.org/dir/Articles/Editing/Software</link>
	</image>
	<item>
		<title>Editing Guidelines for Software Documentation</title>
		<link>http://tc.eserver.org/30814.html</link>
		<guid>http://tc.eserver.org/30814.html</guid>
		<description>Software documentation can be difficult to review, so it helps to have some editing guidelines to keep you focused. Let&apos;s face it; software documentation isn&apos;t exactly exciting reading material. But you should be able to complete the job in a productive manner if you keep your coffee cup full and follow the editing guidelines below.</description>
	</item>
	<item>
		<title>Improving Your Editing Efficiency: Software Skills, Soft Skills, and Survival Skills</title>
		<link>http://tc.eserver.org/29655.html</link>
		<guid>http://tc.eserver.org/29655.html</guid>
		<description>Editing efficiently involves a mix of software skills, soft (human) skills, and strategies for surviving chaos. Although software skills are certainly important--we never have as much time as we need, and computers really can help--we must still nurture author-editor relationships. Knowing the strategies battle-scarred editors have developed over the years can save you from duplicating those scars. In this paper, I&apos;ll discuss the software skills you&apos;ll need to work efficiently, how to cope with the human factors involved in editing, and some strategies for managing the often-chaotic editorial life.</description>
	</item>
	<item>
		<title>Electronically Indicating Approvals or Rejections of Editorial Changes</title>
		<link>http://tc.eserver.org/22136.html</link>
		<guid>http://tc.eserver.org/22136.html</guid>
		<description>This technique (involving two macros) works in Word97, but not in Word6 or 7/95. The requirement is to indicate (for audit purposes) whether an editorial change was accepted or rejected by the author or other authority.</description>
	</item>
	<item>
		<title>Automating Your Edits</title>
		<link>http://tc.eserver.org/15092.html</link>
		<guid>http://tc.eserver.org/15092.html</guid>
		<description>Suggests several uses of Microsoft Word&apos;s macro capabilities to help editors improve their speed and consistency. Macros, for example, are customized keystroke commands.</description>
	</item>
	<item>
		<title>Identifying Additions and Deletions, Part I: Using Compatible Software</title>
		<link>http://tc.eserver.org/14722.html</link>
		<guid>http://tc.eserver.org/14722.html</guid>
		<description>Hart describes the problems and possibilities of Microsoft Word&apos;s Track Changes feature.</description>
	</item>
	<item>
		<title>Identifying Additions and Deletions, Part II: Incompatible Software</title>
		<link>http://tc.eserver.org/14736.html</link>
		<guid>http://tc.eserver.org/14736.html</guid>
		<description>Hart describes the difficulties of viewing electronic edits when the editor and the author are using incompatible software, and offers tips for working around these difficulties.</description>
	</item>
	<atom:link href="http://tc.eserver.org/dir/Articles/Editing/Software.xml" rel="self" type="application/rss+xml"/>
</channel>
</rss>