<?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: Reader survey: the best and worst things about your CAT tools</title>
	<atom:link href="http://thoughtsontranslation.com/2010/01/25/reader-survey-the-best-and-worst-things-about-your-cat-tools/feed/" rel="self" type="application/rss+xml" />
	<link>http://thoughtsontranslation.com/2010/01/25/reader-survey-the-best-and-worst-things-about-your-cat-tools/</link>
	<description>...the translation industry and becoming a translator</description>
	<lastBuildDate>Sun, 27 May 2012 05:56:20 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Riccardo ：GT4T 评测 &#124; DALLASCAO.COM</title>
		<link>http://thoughtsontranslation.com/2010/01/25/reader-survey-the-best-and-worst-things-about-your-cat-tools/#comment-3505</link>
		<dc:creator><![CDATA[Riccardo ：GT4T 评测 &#124; DALLASCAO.COM]]></dc:creator>
		<pubDate>Sat, 05 Jun 2010 12:40:33 +0000</pubDate>
		<guid isPermaLink="false">http://thoughtsontranslation.com/?p=795#comment-3505</guid>
		<description><![CDATA[[...] 作者： Riccardo 张贴于： http://thoughtsontranslation.com/2010/01/25/reader-survey-the-best-and-worst-things-about-your-cat-t... [...]]]></description>
		<content:encoded><![CDATA[<p>[...] 作者： Riccardo 张贴于： http://thoughtsontranslation.com/2010/01/25/reader-survey-the-best-and-worst-things-about-your-cat-t&#8230; [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Roman Mironov</title>
		<link>http://thoughtsontranslation.com/2010/01/25/reader-survey-the-best-and-worst-things-about-your-cat-tools/#comment-2913</link>
		<dc:creator><![CDATA[Roman Mironov]]></dc:creator>
		<pubDate>Mon, 15 Feb 2010 12:04:54 +0000</pubDate>
		<guid isPermaLink="false">http://thoughtsontranslation.com/?p=795#comment-2913</guid>
		<description><![CDATA[I have had a short experience with OmegaT recently, and here is what I have come up with after testing (as my testing was really short, there is a great chance that I am wrong or settings exist that can eliminate the below problem):
1.OmegaT does not support shared access to  translation memory which means limited teamwork capabilities.
2.My opinion is that the GUI, although usable, does not comply with the usability standards of today. It is difficult to understand which segment is currently open, switching between non-adjacent segments is possible with mouse only, source highlighting is possible again with mouse only.
3.As far as I understand, the only way to search the TM is through the standard Search feature. I do not think that this is convenient enough compared to what we have in other common translation environments. The search results are not highlighted. I also did not find the “search and replace” feature.
4.The tags are not protected by default.
5.I experienced problems with copying text into the clipboard, which might be attributable to Java environment.
The advantages include:
1.Automatic project structure creation.
2.The selection is automatically inserted in the Search field when you open the Search feature.
3.I liked the way the “clean up” feature is implemented.
4.Open source, which allows modification.

In general, it is quite good for a free software. For small translations, however, I&#039;d rather use the more  sophisticated Wordfast Pro that is free until 500 segments in the TM.]]></description>
		<content:encoded><![CDATA[<p>I have had a short experience with OmegaT recently, and here is what I have come up with after testing (as my testing was really short, there is a great chance that I am wrong or settings exist that can eliminate the below problem):<br />
1.OmegaT does not support shared access to  translation memory which means limited teamwork capabilities.<br />
2.My opinion is that the GUI, although usable, does not comply with the usability standards of today. It is difficult to understand which segment is currently open, switching between non-adjacent segments is possible with mouse only, source highlighting is possible again with mouse only.<br />
3.As far as I understand, the only way to search the TM is through the standard Search feature. I do not think that this is convenient enough compared to what we have in other common translation environments. The search results are not highlighted. I also did not find the “search and replace” feature.<br />
4.The tags are not protected by default.<br />
5.I experienced problems with copying text into the clipboard, which might be attributable to Java environment.<br />
The advantages include:<br />
1.Automatic project structure creation.<br />
2.The selection is automatically inserted in the Search field when you open the Search feature.<br />
3.I liked the way the “clean up” feature is implemented.<br />
4.Open source, which allows modification.</p>
<p>In general, it is quite good for a free software. For small translations, however, I&#8217;d rather use the more  sophisticated Wordfast Pro that is free until 500 segments in the TM.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: JonJ</title>
		<link>http://thoughtsontranslation.com/2010/01/25/reader-survey-the-best-and-worst-things-about-your-cat-tools/#comment-2870</link>
		<dc:creator><![CDATA[JonJ]]></dc:creator>
		<pubDate>Fri, 05 Feb 2010 20:16:33 +0000</pubDate>
		<guid isPermaLink="false">http://thoughtsontranslation.com/?p=795#comment-2870</guid>
		<description><![CDATA[I&#039;ve been using OmegaT for a relatively short time, and work with Japanese pdfs which do produce lots of useless tags when I OCR them. My solution is simple, but probably very unorthodox. I just ignore the tags; when I&#039;m through, I just copy the whole translation, paste it into a Word file, and make it into a proper document. This last step requires some time and effort, but on jobs like patents, with lots of repetitions, I assume that I&#039;m still saving time.]]></description>
		<content:encoded><![CDATA[<p>I&#8217;ve been using OmegaT for a relatively short time, and work with Japanese pdfs which do produce lots of useless tags when I OCR them. My solution is simple, but probably very unorthodox. I just ignore the tags; when I&#8217;m through, I just copy the whole translation, paste it into a Word file, and make it into a proper document. This last step requires some time and effort, but on jobs like patents, with lots of repetitions, I assume that I&#8217;m still saving time.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Riccardo</title>
		<link>http://thoughtsontranslation.com/2010/01/25/reader-survey-the-best-and-worst-things-about-your-cat-tools/#comment-2821</link>
		<dc:creator><![CDATA[Riccardo]]></dc:creator>
		<pubDate>Fri, 29 Jan 2010 00:57:51 +0000</pubDate>
		<guid isPermaLink="false">http://thoughtsontranslation.com/?p=795#comment-2821</guid>
		<description><![CDATA[GT4T Pro (Google Translator for Translators, available from http://dallascao.com)

Pros: If you want to speed up your translation by taking advantage of Google Translate&#039;s suggestions, this tool allows you to do it from within any program you are using to translate: just select the sentence to translate, hit Ctrl+J, and the selected source text is replaced by the Google translation. I tested it from within Workbench (using both the Word and the Tag Editor interfaces), and from within SDLX. It works, and can help speeding up your translation. The tool is cheap, and allows for a generous trial period.

Cons: Apart from the obvious (the quality of the MT provided), the tool sometime only translates parts of the text, if the selection is too long. Also, concerns have been voiced about the use Google will make of the texts you pass through their translation engine, and they also apply if the text is processed by Google through another interface such as this one.

As regards the quality of the MT provided by Google, your mileage may vary, depending on the type of text and language pair. In some fields I find it is good enough as a first rough draft. In others it is still quite useless.]]></description>
		<content:encoded><![CDATA[<p>GT4T Pro (Google Translator for Translators, available from <a href="http://dallascao.com" rel="nofollow">http://dallascao.com</a>)</p>
<p>Pros: If you want to speed up your translation by taking advantage of Google Translate&#8217;s suggestions, this tool allows you to do it from within any program you are using to translate: just select the sentence to translate, hit Ctrl+J, and the selected source text is replaced by the Google translation. I tested it from within Workbench (using both the Word and the Tag Editor interfaces), and from within SDLX. It works, and can help speeding up your translation. The tool is cheap, and allows for a generous trial period.</p>
<p>Cons: Apart from the obvious (the quality of the MT provided), the tool sometime only translates parts of the text, if the selection is too long. Also, concerns have been voiced about the use Google will make of the texts you pass through their translation engine, and they also apply if the text is processed by Google through another interface such as this one.</p>
<p>As regards the quality of the MT provided by Google, your mileage may vary, depending on the type of text and language pair. In some fields I find it is good enough as a first rough draft. In others it is still quite useless.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kevin Lossner</title>
		<link>http://thoughtsontranslation.com/2010/01/25/reader-survey-the-best-and-worst-things-about-your-cat-tools/#comment-2817</link>
		<dc:creator><![CDATA[Kevin Lossner]]></dc:creator>
		<pubDate>Tue, 26 Jan 2010 00:18:26 +0000</pubDate>
		<guid isPermaLink="false">http://thoughtsontranslation.com/?p=795#comment-2817</guid>
		<description><![CDATA[The ergonomics of Across are appalling, or at least that was the case in the last version I tried. You really do get what you pay for in this case unless you are a corporate licensee.

Right now among the major commercial products I think MemoQ has the best mix of features, support and ease of use. The things I am seeing in the soon-to-be released (Feb 1) version 4 are exciting.

I am fascinated by what a colleague said recently about CafeTrans (from Poland) and plan to have a look. It&#039;s multi-platform, inexpensive and has an impressive spiel.]]></description>
		<content:encoded><![CDATA[<p>The ergonomics of Across are appalling, or at least that was the case in the last version I tried. You really do get what you pay for in this case unless you are a corporate licensee.</p>
<p>Right now among the major commercial products I think MemoQ has the best mix of features, support and ease of use. The things I am seeing in the soon-to-be released (Feb 1) version 4 are exciting.</p>
<p>I am fascinated by what a colleague said recently about CafeTrans (from Poland) and plan to have a look. It&#8217;s multi-platform, inexpensive and has an impressive spiel.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ruben de la Fuente</title>
		<link>http://thoughtsontranslation.com/2010/01/25/reader-survey-the-best-and-worst-things-about-your-cat-tools/#comment-2816</link>
		<dc:creator><![CDATA[Ruben de la Fuente]]></dc:creator>
		<pubDate>Mon, 25 Jan 2010 17:28:39 +0000</pubDate>
		<guid isPermaLink="false">http://thoughtsontranslation.com/?p=795#comment-2816</guid>
		<description><![CDATA[Hi Corinne,

I&#039;d like to comment on Trados Studio. The down side is that it is very pricy and the customer service is not optimal. The good news is that it is very powerful: supports a lot of formats (xliff, native DTP formats, even pdfs), it is integrated with machine translation for no matches, predictive text (Auto suggest dictionaries), extended QA features.

A very interesting tool I haven&#039;t used yet but looks very promissing is Across: translator version is free and has all capabilities (unlike lite versions of other tools). Has anyone tried it yet?]]></description>
		<content:encoded><![CDATA[<p>Hi Corinne,</p>
<p>I&#8217;d like to comment on Trados Studio. The down side is that it is very pricy and the customer service is not optimal. The good news is that it is very powerful: supports a lot of formats (xliff, native DTP formats, even pdfs), it is integrated with machine translation for no matches, predictive text (Auto suggest dictionaries), extended QA features.</p>
<p>A very interesting tool I haven&#8217;t used yet but looks very promissing is Across: translator version is free and has all capabilities (unlike lite versions of other tools). Has anyone tried it yet?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

