<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
	<title>PlainLanguage.gov</title>	<link>http://tc.eserver.org/publisher/PlainLanguage.gov</link>
	<description>A listing of works published by PlainLanguage.gov 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>PlainLanguage.gov</title>
		<link>http://tc.eserver.org/dir/PlainLanguage.gov</link>
	</image>
	<item>
		<title>Engineering Terms in Plain English</title>
		<link>http://tc.eserver.org/25999.html</link>
		<guid>http://tc.eserver.org/25999.html</guid>
		<description>Twenty terms from engineering writiting translated into the vernacular.</description>
	</item>
	<item>
		<title>High Tech Humor</title>
		<link>http://tc.eserver.org/25990.html</link>
		<guid>http://tc.eserver.org/25990.html</guid>
		<description>The remarkable growth of the information technology industry has created a tremendous opportunity for people with skill putting words on paper. Technical writers, once a rare and highly skilled position, are now as common as fruit flies—though they take up a lot more space. Yet the pay is pretty good considering how little work they actually do, so young English-major weenies desperate for employment continue to swarm around IT companies, hoping for a bit of rotting fru—er, looking for a plum position.</description>
	</item>
	<item>
		<title>A History of Plain Language in the United States Government</title>
		<link>http://tc.eserver.org/25991.html</link>
		<guid>http://tc.eserver.org/25991.html</guid>
		<description>Awareness of the need for clear language isn&apos;t new in the US government.</description>
	</item>
	<item>
		<title>How to Write Good</title>
		<link>http://tc.eserver.org/26000.html</link>
		<guid>http://tc.eserver.org/26000.html</guid>
		<description>Fifty-two humorous rules about how to write well (each of which is broken).</description>
	</item>
	<item>
		<title>Nine Easy Steps to Longer Sentences</title>
		<link>http://tc.eserver.org/26001.html</link>
		<guid>http://tc.eserver.org/26001.html</guid>
		<description>Are you tired of short, direct, and simple sentences that seem to take forever to fill up a page? Are you paid by the word? In either case you can benefit by increasing the number of words in your sentences and the bulk of your writing. And it&apos;s easy if you just follow nine simple steps, many of which you may already know and practice.</description>
	</item>
	<item>
		<title>Writing Effective Letters</title>
		<link>http://tc.eserver.org/26003.html</link>
		<guid>http://tc.eserver.org/26003.html</guid>
		<description>Always start by putting your main message up front. Some people feel that bad news should be buried. But research shows that readers will always look for the bottom line.</description>
	</item>
	<item>
		<title>Writing Reader-Friendly Documents</title>
		<link>http://tc.eserver.org/26002.html</link>
		<guid>http://tc.eserver.org/26002.html</guid>
		<description>The traditional way of writing government documents has not worked well.  Too often, complicated and jargon filled documents have resulted in frustration, lawsuits, and a lack of trust between citizens and their government. To overcome this legacy, we have a great responsibility to communicate clearly.</description>
	</item>
	<atom:link href="http://tc.eserver.org/publisher/PlainLanguage.gov.xml" rel="self" type="application/rss+xml"/>
</channel>
</rss>