<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
	<title>Articles&gt;Documentation&gt;Technical Illustration</title>	<link>http://tc.eserver.org/dir/Articles/Documentation/Technical-Illustration</link>
	<description>A listing of the most recently indexed works about Articles and Documentation and Technical Illustration 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;Documentation&gt;Technical Illustration</title>
		<link>http://tc.eserver.org/dir/Articles/Documentation/Technical-Illustration</link>
	</image>
	<item>
		<title>So What’s Up with Screen Captures?</title>
		<link>http://tc.eserver.org/35523.html</link>
		<guid>http://tc.eserver.org/35523.html</guid>
		<description>In this first column on media matters, Lee discusses screen captures, including quality, manipulation, file type, file size, and more.</description>
	</item>
	<item>
		<title>Screen Shots in Documentation</title>
		<link>http://tc.eserver.org/35303.html</link>
		<guid>http://tc.eserver.org/35303.html</guid>
		<description>Just as I would with words, I&apos;ll cut out the obvious and whatever does not add value. I prefer an additive approach (put it in only when the words seem inadequate) over a subtractive approach (take it out if it seems superfluous). In other words, I&apos;ll be more open to screen shots in the future, but they have to work themselves into the document, not just be their by entitlement until expelled. </description>
	</item>
	<item>
		<title>Do Screen Captures Still Make Sense?</title>
		<link>http://tc.eserver.org/34788.html</link>
		<guid>http://tc.eserver.org/34788.html</guid>
		<description>Writing more simply helps keep content more manageable and can increase its usability. So why do we continue to litter content with screen captures, which can be difficult to manage and often duplicate what users already see in application interfaces?</description>
	</item>
	<item>
		<title>A Photo Essay of Classic Instruction Manuals</title>
		<link>http://tc.eserver.org/33155.html</link>
		<guid>http://tc.eserver.org/33155.html</guid>
		<description>How do you run the A/C on a spy plane? Where&apos;s the Start button on a nuclear power plant? Don&apos;t try to wing it—read the directions! A portfolio of classic instruction manuals.</description>
	</item>
	<item>
		<title>Using Comics in Technical Documentation</title>
		<link>http://tc.eserver.org/30640.html</link>
		<guid>http://tc.eserver.org/30640.html</guid>
		<description>This article is based on the research and feedback I received from a number of user experience designers, usability specialists, product developers and writers, which led me to engage in a dialogue with the users.</description>
	</item>
	<item>
		<title>Customer Satisfaction Lessons Learned from Building Furniture with Wordless Documentation</title>
		<link>http://tc.eserver.org/29763.html</link>
		<guid>http://tc.eserver.org/29763.html</guid>
		<description>Documentation and package design play a major role in customer satisfaction. The author tested three sets of wordless documentation by building pieces of furniture from three different manufacturers. While the construction methods, packaging, and wordless documentation methods were on the surface very similar, small differences had a significant impact on the usability of the instructions and the overall customer satisfaction with the documentation and the product. Decisions that were handled differently included visual verification of parts, whether or not extra hardware was provided and how it was provided, the appropriateness of the hardware, the quality of the hardware, the need for additional tools, and the care evidenced in packaging and labeling of parts. From these experiences, she makes recommendations for enhancing customer satisfaction that apply not just to wordless documentation, but to other consumer products.</description>
	</item>
	<item>
		<title>Wordless Manuals: Replacing Words with Pictures</title>
		<link>http://tc.eserver.org/24260.html</link>
		<guid>http://tc.eserver.org/24260.html</guid>
		<description>How do you convey an entire set of complex instructions without words, and why would you even bother? Since he first quipped this question, Patrick Hofmann has deleted countless words from the pages of hardware user manuals. Patrick is a technical illustrator and writer who, with the help of his team at Quintext information engineering in Waterloo, Canada, creates wordless documentation and visual solutions for his clients. In this session, you will learn what he learned: how to use wordlessness to downsize multi-lingual sets of assembly manuals, and how to illustrate complex instructions with the same concern for usability as we have with writing.</description>
	</item>
	<item>
		<title>Pictures for Procedures</title>
		<link>http://tc.eserver.org/24218.html</link>
		<guid>http://tc.eserver.org/24218.html</guid>
		<description>Illustrations for procedural documents should show actions from the mental perspective of people carrying them out. Illustrations also should take into account the twodimensional displays of printed documents and computer screens by orienting critical body positions and movements across displays.</description>
	</item>
	<item>
		<title>Photo-Tracing</title>
		<link>http://tc.eserver.org/21436.html</link>
		<guid>http://tc.eserver.org/21436.html</guid>
		<description>One of the most effective methods of creating a technical illustration is the photo-tracing technique.</description>
	</item>
	<atom:link href="http://tc.eserver.org/dir/Articles/Documentation/Technical-Illustration.xml" rel="self" type="application/rss+xml"/>
</channel>
</rss>