<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
	<title>Ribert, Roger</title>	<link>http://tc.eserver.org/authors/Ribert,_Roger</link>
	<description>A bibliography of works by Ribert, Roger 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>Ribert, Roger</title>
		<link>http://tc.eserver.org/dir/Ribert,_Roger</link>
	</image>
	<item>
		<title>How to &quot;Proof&quot; a Translation</title>
		<link>http://tc.eserver.org/34594.html</link>
		<guid>http://tc.eserver.org/34594.html</guid>
		<description>As the global economy expands, American companies are translating large numbers of documents into multiple languages. As a technical writer, my job is to read documents in German, Italian, Danish, French, Spanish, Greek, and Polish among other languages. I also review documents in Chinese, Japanese, and Korean, but the process is harder and less productive. This article will provide a few practical tips for &quot;proofing&quot; translations of Western documents.</description>
	</item>
	<atom:link href="http://tc.eserver.org/authors/Ribert,_Roger.xml" rel="self" type="application/rss+xml"/>
</channel>
</rss>