<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Yeah, right&#8230;</title>
	<atom:link href="http://translationmusings.com/2008/06/09/yeah-right/feed/" rel="self" type="application/rss+xml" />
	<link>http://translationmusings.com/2008/06/09/yeah-right/</link>
	<description>featuring musings about my life and the translation industry</description>
	<lastBuildDate>Thu, 09 Feb 2012 18:49:40 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Ryan Ginstrom</title>
		<link>http://translationmusings.com/2008/06/09/yeah-right/#comment-29</link>
		<dc:creator><![CDATA[Ryan Ginstrom]]></dc:creator>
		<pubDate>Tue, 10 Jun 2008 01:04:11 +0000</pubDate>
		<guid isPermaLink="false">http://jillsommer.wordpress.com/?p=31#comment-29</guid>
		<description><![CDATA[As Corrine says, if using a translation-memory tool allows you to work faster, it&#039;s reasonable to pass on a &lt;em&gt;portion&lt;/em&gt; of those savings on to the client. You also need to keep at least some of the savings to recoup the cost of your software, the time you spent to learn it, and the expertise you&#039;ve gained in its use.

If the translation memory doesn&#039;t save you time, then I see no reason to provide a discount. For example, I recently &lt;a href=&quot;http://felix-cat.com/blog/2008/05/22/charge-for-100-matches/&quot; rel=&quot;nofollow&quot;&gt;argued that translators should charge for 100% matches&lt;/a&gt;. In addition, not all TMs are created equal, and working with a TM created by another translator can often take &lt;em&gt;more&lt;/em&gt; time than not using one at all.]]></description>
		<content:encoded><![CDATA[<p>As Corrine says, if using a translation-memory tool allows you to work faster, it&#8217;s reasonable to pass on a <em>portion</em> of those savings on to the client. You also need to keep at least some of the savings to recoup the cost of your software, the time you spent to learn it, and the expertise you&#8217;ve gained in its use.</p>
<p>If the translation memory doesn&#8217;t save you time, then I see no reason to provide a discount. For example, I recently <a href="http://felix-cat.com/blog/2008/05/22/charge-for-100-matches/" rel="nofollow">argued that translators should charge for 100% matches</a>. In addition, not all TMs are created equal, and working with a TM created by another translator can often take <em>more</em> time than not using one at all.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: yndigo</title>
		<link>http://translationmusings.com/2008/06/09/yeah-right/#comment-28</link>
		<dc:creator><![CDATA[yndigo]]></dc:creator>
		<pubDate>Mon, 09 Jun 2008 23:11:52 +0000</pubDate>
		<guid isPermaLink="false">http://jillsommer.wordpress.com/?p=31#comment-28</guid>
		<description><![CDATA[Jill,
&quot;That&#039;s how they get ya&#039;&quot; is what my father-in-law says. I think the operative word in the term &quot;Trados suggested rate&quot; is &quot;suggested.&quot; reminds me of something I should have noticed a while ago: I went to supermarket to buy a half gallon of ice cream and most of the half gallons are now 1.5 quarts, i.e., one quarter less. 

From an agency&#039;s point of view, if those rates can be nudged downward just a bit, it helps their bottom line. Ignoring the email was a good idea IMHO.]]></description>
		<content:encoded><![CDATA[<p>Jill,<br />
&#8220;That&#8217;s how they get ya&#8217;&#8221; is what my father-in-law says. I think the operative word in the term &#8220;Trados suggested rate&#8221; is &#8220;suggested.&#8221; reminds me of something I should have noticed a while ago: I went to supermarket to buy a half gallon of ice cream and most of the half gallons are now 1.5 quarts, i.e., one quarter less. </p>
<p>From an agency&#8217;s point of view, if those rates can be nudged downward just a bit, it helps their bottom line. Ignoring the email was a good idea IMHO.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Corinne McKay</title>
		<link>http://translationmusings.com/2008/06/09/yeah-right/#comment-27</link>
		<dc:creator><![CDATA[Corinne McKay]]></dc:creator>
		<pubDate>Mon, 09 Jun 2008 20:00:59 +0000</pubDate>
		<guid isPermaLink="false">http://jillsommer.wordpress.com/?p=31#comment-27</guid>
		<description><![CDATA[Thanks for the great post! To me, anything below about 95% match produces a consistency advantage but not necessarily a speed advantage, and speed advantages are the only reason I see to give a discount. Sometimes I voluntarily give a discount when an agency sends a set of documents that are substantially similar, because the first one might take 7 hours and the second one might take 3 hours. I think that&#039;s fair, whereas giving a discount because the translation took the same amount of time but was more consistent does not seem fair to me, and in my experience that&#039;s the result (same amount of time, more consistent) when you get down into the 80% and 70% match terrain.]]></description>
		<content:encoded><![CDATA[<p>Thanks for the great post! To me, anything below about 95% match produces a consistency advantage but not necessarily a speed advantage, and speed advantages are the only reason I see to give a discount. Sometimes I voluntarily give a discount when an agency sends a set of documents that are substantially similar, because the first one might take 7 hours and the second one might take 3 hours. I think that&#8217;s fair, whereas giving a discount because the translation took the same amount of time but was more consistent does not seem fair to me, and in my experience that&#8217;s the result (same amount of time, more consistent) when you get down into the 80% and 70% match terrain.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

