<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Felix Blog &#187; misc</title>
	<atom:link href="http://felix-cat.com/blog/category/misc/feed/" rel="self" type="application/rss+xml" />
	<link>http://felix-cat.com/blog</link>
	<description>Blog for the Felix CAT tool</description>
	<lastBuildDate>Tue, 15 May 2012 04:44:32 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
		<item>
		<title>Comparison of Felix and Trados matching algorithms</title>
		<link>http://felix-cat.com/blog/2008/08/15/comparison-of-felix-and-trados-matching-algorithms/</link>
		<comments>http://felix-cat.com/blog/2008/08/15/comparison-of-felix-and-trados-matching-algorithms/#comments</comments>
		<pubDate>Fri, 15 Aug 2008 03:10:28 +0000</pubDate>
		<dc:creator>Ryan Ginstrom</dc:creator>
				<category><![CDATA[Felix]]></category>
		<category><![CDATA[misc]]></category>
		<category><![CDATA[algorithm]]></category>
		<category><![CDATA[fuzzy]]></category>
		<category><![CDATA[matching]]></category>
		<category><![CDATA[TM]]></category>
		<category><![CDATA[trados]]></category>
		<category><![CDATA[translation memory]]></category>

		<guid isPermaLink="false">http://felix-cat.com/blog/?p=40</guid>
		<description><![CDATA[The About Translation blog posted a while ago about quirks in the matching algorithm employed by Trados. He posts the following match results: Trados matches for &#8220;LEAD DESIGN -&#8221; Source Fuzzy Score LEAD PROGRAMMER - 75% Lead Design 67% He points out that this seems unintuitive and less than useful. Felix seems to do a [...]]]></description>
			<content:encoded><![CDATA[<p>The <a href="http://aboutranslation.blogspot.com/">About Translation blog</a> posted a while ago about <a href="http://aboutranslation.blogspot.com/2008/01/shouldnt-trados-programmers-improve.html">quirks in the matching algorithm employed by Trados.</a></p>
<p>He posts the following match results:</p>
<h3>Trados matches for &#8220;LEAD DESIGN -&#8221;</h3>
<table border="1" cellpadding="5" cellspacing="0" >
<tr>
<th>Source</th>
<th>Fuzzy Score</th>
</tr>
<tr style="background-color: #8f8">
<td>LEAD PROGRAMMER -</td>
<td align="right">75%</td>
</tr>
<tr style="background-color: orange">
<td>Lead Design</td>
<td align="right">67%</td>
</tr>
</table>
<p>He points out that this seems unintuitive and less than useful.</p>
<p>Felix seems to do a better job at assigning scores:</p>
<h3>Felix matches for &#8220;LEAD DESIGN -&#8221;</h3>
<table border="1" cellpadding="5" cellspacing="0" >
<tr>
<th>Source</th>
<th>Fuzzy Score</th>
</tr>
<tr style="background-color: orange">
<td>LEAD PROGRAMMER -</td>
<td align="right">41%</td>
</tr>
<tr style="background-color: #8f8">
<td>Lead Design</td>
<td align="right">85%</td>
</tr>
</table>
<p><img src="/media/img/lead_design.png" alt="Fuzzy match results for LEAD DESIGN" /></p>
<p>Note that the scores may differ slightly depending on your Felix search settings. For example, you can set it to ignore case, wide/narrow characters, assign penalties for formatting mismatches, and the like. The scores above are with the &#8220;ignore case&#8221; setting. The part highlighted in red is the part that Felix recognizes as differing between the two strings.</p>
]]></content:encoded>
			<wfw:commentRss>http://felix-cat.com/blog/2008/08/15/comparison-of-felix-and-trados-matching-algorithms/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

