<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
	<title>Articles&gt;Language&gt;Localization&gt;Glossary</title>	<link>http://tc.eserver.org/dir/Articles/Language/Localization/Glossary</link>
	<description>A listing of the most recently indexed works about Articles and Language and Localization and Glossary 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;Language&gt;Localization&gt;Glossary</title>
		<link>http://tc.eserver.org/dir/Articles/Language/Localization/Glossary</link>
	</image>
	<item>
		<title>The Translation Glossary: Stepping Stone to a Quality Translation</title>
		<link>http://tc.eserver.org/18493.html</link>
		<guid>http://tc.eserver.org/18493.html</guid>
		<description>If your company is new to the process of translating their documentation, chances are little groundwork was laid for the &#xD;process. One thing you can do to improve the quality of the translation in this situation is to create a good translation &#xD;glossary. A translation glossary ensures consistent terminology in the translation; that a term in English always becomes&#xD;the same term in the translated text. It eliminates the problem of referring to the same concept or same component by&#xD;different names in different places in the documentation.&#xD;&#xD;Technical writers are in a good position to create the glossary. They constantly deal with questions of terminology. They &#xD;probably wrote the manual being translated and already had to make decisions about terminology for the English version.</description>
	</item>
	<atom:link href="http://tc.eserver.org/dir/Articles/Language/Localization/Glossary.xml" rel="self" type="application/rss+xml"/>
</channel>
</rss>