<?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;Controlled Vocabulary</title>	<link>http://tc.eserver.org/dir/Articles/Language/Localization/Controlled-Vocabulary</link>
	<description>A listing of the most recently indexed works about Articles and Language and Localization and Controlled Vocabulary 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;Controlled Vocabulary</title>
		<link>http://tc.eserver.org/dir/Articles/Language/Localization/Controlled-Vocabulary</link>
	</image>
	<item>
		<title>Terminologiemanagement</title>
		<link>http://tc.eserver.org/31175.html</link>
		<guid>http://tc.eserver.org/31175.html</guid>
		<description>Der Unterschied zwischen dem richtigen Wort und dem beinahe richtigen ist derselbe Unterschied wie der zwischen dem Blitz und einem Glühwürmchen.</description>
	</item>
	<item>
		<title>Unexpected ROI (Return on Investment) from Terminology</title>
		<link>http://tc.eserver.org/30733.html</link>
		<guid>http://tc.eserver.org/30733.html</guid>
		<description>Personal experience shows that all localization clients are interested in terminology--without exception. Only very large organizations, however, actually seem to maintain terminology databases.</description>
	</item>
	<item>
		<title>The Direct Road</title>
		<link>http://tc.eserver.org/26357.html</link>
		<guid>http://tc.eserver.org/26357.html</guid>
		<description>Firms that export to the USA are faced with the challenge of having to deliver accompanying TD that meets the requirements of that country. This is true not only in legal or safety-relevant terms, but also in terms of the language used. Production and translation of multi-lingual documentation are part of an overall process. Even while creating the source text, the technical writer must keep in mind the translation into the target language. Unambiguous rendering, consistency in the terminology, wording that is appropriate for the target group and reader-friendliness are some of the highest criteria which would justify the use of a controlled language.</description>
	</item>
	<item>
		<title>Controlled Language - Risks and Side Effects</title>
		<link>http://tc.eserver.org/23496.html</link>
		<guid>http://tc.eserver.org/23496.html</guid>
		<description>Controlled Language (CL) is a controversial issue for linguists, editors, readers, but also for firms. Costs, marketing and sales figures are at stake.&#xD;&#xD;Why did I select &apos;risks and side effects&apos;, from the numerous problems involved, for my contribution? I am convinced that CL will be successful because positive / financial arguments prevail. Consequently, we will have to avail ourselves of CL, and identify and realize the risks involved and potential vicious side effects.</description>
	</item>
	<item>
		<title>Controlled Language and Translation Memory Technology: A Perfect Match to Save Translation Cost</title>
		<link>http://tc.eserver.org/23476.html</link>
		<guid>http://tc.eserver.org/23476.html</guid>
		<description>It goes without saying that controlled language makes it easier not only to understand a text, but also to translate it into another language, thereby reducing translation cost. This positive effect can be even more increased by the use of professional translation tools. By &quot;translation tools&quot;, I do not mean machine translation systems such as Logos or Systran, but rather terminology database and translation memory applications. Typical examples of such tools are MultiTerm &apos;95 Plus and Translator&apos;s Workbench.</description>
	</item>
	<item>
		<title>Different Types of Controlled Languages</title>
		<link>http://tc.eserver.org/23497.html</link>
		<guid>http://tc.eserver.org/23497.html</guid>
		<description>There has been much discussion on the topic of Controlled Language (CL) in the past issues of TC-Forum. With several years of experience as a translator, as a trainer of Controlled English writing and translation post-editing, and as a developer of Machine Translation (MT) and Translation Memory (TM) systems, I would like to clarify some points that do not seem to have been presented in other articles. These points do not indicate all of the details of possible CL systems, but I hope that they open up the discussion to cover both past and recent developments in CL system and application research and development.</description>
	</item>
	<item>
		<title>Writer&apos;s View of Using a Controlled Language</title>
		<link>http://tc.eserver.org/23499.html</link>
		<guid>http://tc.eserver.org/23499.html</guid>
		<description>While the benefits of using a controlled language are clear from a business perspective (reduced translation costs, standardized phrases, reduced potential for misinterpretation), applying it can be a challenge when writing even simple service procedures.</description>
	</item>
	<atom:link href="http://tc.eserver.org/dir/Articles/Language/Localization/Controlled-Vocabulary.xml" rel="self" type="application/rss+xml"/>
</channel>
</rss>