<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
	<title>Impact Information</title>	<link>http://tc.eserver.org/publisher/Impact_Information</link>
	<description>A listing of works published by Impact Information 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>Impact Information</title>
		<link>http://tc.eserver.org/dir/Impact_Information</link>
	</image>
	<item>
		<title>The Basics of Plain Language </title>
		<link>http://tc.eserver.org/31613.html</link>
		<guid>http://tc.eserver.org/31613.html</guid>
		<description>The purpose of this lesson is to introduce the basic concepts of plain language.</description>
	</item>
	<item>
		<title>Get on Board the XML Train</title>
		<link>http://tc.eserver.org/31614.html</link>
		<guid>http://tc.eserver.org/31614.html</guid>
		<description>The next century will be an XML century, make no mistake about it. All our documents, even checks, credit card slips, personal letters, recipes, technical documents, everything, will benefit from XML technologies. Students are already learning XML in schools, and big businesses are using it to publish their databases on the web. The appearance of the electronic spreadsheet ten years ago changed the way we do business. XML will change the way we write documents.</description>
	</item>
	<item>
		<title>It&apos;s a People Thing: The Switch to Reader-Centered Documents</title>
		<link>http://tc.eserver.org/31611.html</link>
		<guid>http://tc.eserver.org/31611.html</guid>
		<description> One of the central causes of poor writing is a lack of a thorough understanding of the audience. What are the problems that readers have to solve, and how can we help them? Too many writers believe that people will understand what they have written just because the writers themselves understand it.&#xD;&#xD;Good writing always begins with a study of the readers&apos; reading skills, their actual physical situation, the problems they face, the motivation they need, and the actions they need to take. </description>
	</item>
	<item>
		<title>The Literacy Alarm: It&apos;s Everyone&apos;s Problem</title>
		<link>http://tc.eserver.org/31608.html</link>
		<guid>http://tc.eserver.org/31608.html</guid>
		<description>Between 21 and 23 percent of Americans (40 million) are functioning at Level 1 literacy rating, defined simply as &quot;not having adequate reading skills for daily life.&quot; The rate for California is 24 %, for Orange County, 20%. These are people who cannot read, must struggle to read, or cannot cope with unfamiliar or complex information.</description>
	</item>
	<item>
		<title>Overcoming Word Inflation: The Benefits of Minimalist Design</title>
		<link>http://tc.eserver.org/31609.html</link>
		<guid>http://tc.eserver.org/31609.html</guid>
		<description>Writers are great inflators. We can take a simple half page describing a computer interface and in a few hours transform it into a 35-page document complete with glossaries, type conventions, overviews, introductions, mission statements, charts, clip art, and copyright pages full of disclaimers, trademark acknowledgements, and credits. The results will make the people in marketing and sales simply glow.</description>
	</item>
	<item>
		<title>The Plain Language Process: Steps for Effective Writing</title>
		<link>http://tc.eserver.org/31607.html</link>
		<guid>http://tc.eserver.org/31607.html</guid>
		<description>Effective writing does not come by chance. The creation of all documents, including forms, labels, websites, business letters, legal notices, manuals, procedures, reports, and proposals, usually involves the following key steps.</description>
	</item>
	<item>
		<title>Politics and the English Language</title>
		<link>http://tc.eserver.org/31610.html</link>
		<guid>http://tc.eserver.org/31610.html</guid>
		<description>If thought corrupts language, language can also corrupt thought. A bad usage can spread by tradition and imitation, even among people who should and do know better.</description>
	</item>
	<item>
		<title>Writing for Dollars, Writing to Please</title>
		<link>http://tc.eserver.org/31612.html</link>
		<guid>http://tc.eserver.org/31612.html</guid>
		<description>Call it the benefits of plain language. The literature contains studies about these benefits, but no one has ever collected and summarized the studies in a way that makes their full force apparent. As you read the summaries in this article, try to imagine the costs of poor writing — typified by officialese and legalese — in business, government, and law. The costs are almost beyond imagining, and certainly beyond calculating. If this evidence doesn&apos;t convince organizations and individual writers that plain language can change their fortunes, probably nothing will.</description>
	</item>
	<item>
		<title>XML Arrives in Word 2003</title>
		<link>http://tc.eserver.org/31615.html</link>
		<guid>http://tc.eserver.org/31615.html</guid>
		<description>The XML train is finally pulling into the station. It brings an ocean change in the way we create, store, and manage information. In October of last year, Microsoft released Office 2003, which brings the promise of XML to the desktop. Previously, Word 2000 saved only the Properties of documents in an XML module in files converted to HTML.&#xD;&#xD;In this new edition, you can save or export all Office documents as XML documents. Using XML tags, we can now identify various elements of our documents for manipulation, storage, and retrieval as you would data in a data bank. It also enables us to more easily share information in those documents across other applications (including Web applications), networks, and operating systems.</description>
	</item>
	<item>
		<title>Readability</title>
		<link>http://tc.eserver.org/31606.html</link>
		<guid>http://tc.eserver.org/31606.html</guid>
		<description>I know from some years running a reading clinic in the United States that you can make more progress if you start the students out on relatively easy reading material so the the students can read the materials with some comprehension and success.  But how do you tell these African instructors how to select “relatively easy” reading materials in technical English?  The answer - use a readability formula.</description>
	</item>
	<atom:link href="http://tc.eserver.org/publisher/Impact_Information.xml" rel="self" type="application/rss+xml"/>
</channel>
</rss>