<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
	<title>Design&gt;Document Design&gt;Forms</title>	<link>http://tc.eserver.org/dir/Design/Document-Design/Forms</link>
	<description>A listing of the most recently indexed works about Design and Document Design and Forms 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>Design&gt;Document Design&gt;Forms</title>
		<link>http://tc.eserver.org/dir/Design/Document-Design/Forms</link>
	</image>
	<item>
		<title>Importing and Exporting Form Data in Acrobat</title>
		<link>http://tc.eserver.org/29930.html</link>
		<guid>http://tc.eserver.org/29930.html</guid>
		<description>When using PDF forms, it&apos;s possible to export, store and import the data in Form Data Format (FDF). Since an FDF file only includes the form data and not the form itself, it is much smaller and more lightweight that the complete PDF form, making it more efficient to manipulate. This tip explains how to export and import FDF data using Acrobat.</description>
	</item>
	<item>
		<title>Designing Information-Gathering Forms</title>
		<link>http://tc.eserver.org/27463.html</link>
		<guid>http://tc.eserver.org/27463.html</guid>
		<description>Poorly designed information-gathering forms drive up operating costs. Good design depends on a careful analysis of two users: Form-Fillers and Form Readers. Both types ofform user benefit if the form designer follows four principles of overall design. Guidelines for answer sections and user testing can also help designers produce more effective forms. Evaluation of existing forms can lead to successful revision so that costly mistakes can be avoided.</description>
	</item>
	<item>
		<title>&amp;#35774;&amp;#35745;&amp;#21487;&amp;#29992;&amp;#30340;&amp;#34920;&amp;#21333;&amp;#65306;&amp;#34920;&amp;#21333;&amp;#30340;&amp;#19977;&amp;#23618;&amp;#27169;&amp;#22411;</title>
		<link>http://tc.eserver.org/26956.html</link>
		<guid>http://tc.eserver.org/26956.html</guid>
		<description>&amp;#22312;‘&amp;#19977;&amp;#23618;&amp;#27169;&amp;#22411;’&amp;#20013;&amp;#65292;&amp;#19968;&amp;#20010;&amp;#34920;&amp;#21333;&amp;#26377;&amp;#19977;&amp;#31181;&amp;#23646;&amp;#24615;&amp;#65306;&amp;#24863;&amp;#30693;&amp;#65288;&amp;#24067;&amp;#23616;&amp;#65289;&amp;#12289;&amp;#23545;&amp;#35805;&amp;#65288;&amp;#38382;&amp;#39064;&amp;#21644;&amp;#22238;&amp;#31572;&amp;#65289;&amp;#12289;&amp;#21644;&amp;#20851;&amp;#31995;&amp;#65288;&amp;#20219;&amp;#21153;&amp;#30340;&amp;#32467;&amp;#26500;&amp;#65289;&amp;#12290;</description>
	</item>
	<item>
		<title>Designing Usable Forms: The Three-Layer Model of the Form</title>
		<link>http://tc.eserver.org/26396.html</link>
		<guid>http://tc.eserver.org/26396.html</guid>
		<description>Why do people say &apos;I’m not good with forms&apos; or &apos;I don’t like forms&apos; when a form is only a piece of paper, or a screen, with some printing on it? There must be something special about forms that inspires these comments.</description>
	</item>
	<item>
		<title>Creating Usable Forms</title>
		<link>http://tc.eserver.org/24962.html</link>
		<guid>http://tc.eserver.org/24962.html</guid>
		<description>A form is usable when it builds an effective communication bridge between your clients and your data entry staff. A usable form is readable, concise, and contains appropriate pictures and graphic elements. The steps in creating a usable form are the following: (1) Create a prototype. (2) Examine the extremes. (3) Produce the forms. (4) Fine tune the forms.</description>
	</item>
	<item>
		<title>Hooray, I&apos;m Doing the Forms!</title>
		<link>http://tc.eserver.org/24872.html</link>
		<guid>http://tc.eserver.org/24872.html</guid>
		<description>Everyone hates forms--users hate filling them out, and writers hate creating them. But forms offer writers a unique opportunity for rewarding work. Jarrett suggests ways to improve forms--and, possibly, users&apos; lives.</description>
	</item>
	<atom:link href="http://tc.eserver.org/dir/Design/Document-Design/Forms.xml" rel="self" type="application/rss+xml"/>
</channel>
</rss>