<?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/"
		>
<channel>
	<title>Comments on: Alchemy Catalyst 8.0 localization environment pre-announced</title>
	<atom:link href="http://blog.albatrossolutions.com/localization-tools/alchemy-catalyst-80-localization-environment-pre-announced/feed" rel="self" type="application/rss+xml" />
	<link>http://blog.albatrossolutions.com/localization-tools/alchemy-catalyst-80-localization-environment-pre-announced</link>
	<description>All about TEnT, CAT tools, translation memory, translation resources, Italian localization, etc.</description>
	<lastBuildDate>Thu, 15 Jul 2010 15:44:29 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: Roberto Savelli</title>
		<link>http://blog.albatrossolutions.com/localization-tools/alchemy-catalyst-80-localization-environment-pre-announced/comment-page-1#comment-359</link>
		<dc:creator>Roberto Savelli</dc:creator>
		<pubDate>Mon, 11 May 2009 14:25:25 +0000</pubDate>
		<guid isPermaLink="false">http://blog.albatrossolutions.com/?p=216#comment-359</guid>
		<description>Hi Nick, thanks for your comment.

I have tried Catalyst 8 myself and I was pleased to see that there is an &quot;Export to Trados TagEditor&quot; feature, which can be used, for instance, for projects that do not involve the visual localization of interfaces (e.g. menus, dialog boxes), but rather separate strings with non context whatsoever, like error messages.

In this case the visual features of Catalyst are not used and I&#039;m sure most translators would prefer using a text-specific TEnT like Trados instead of having to struggle with the shortcomings of Catalyst&#039;s text-editing features.</description>
		<content:encoded><![CDATA[<p>Hi Nick, thanks for your comment.</p>
<p>I have tried Catalyst 8 myself and I was pleased to see that there is an &#8220;Export to Trados TagEditor&#8221; feature, which can be used, for instance, for projects that do not involve the visual localization of interfaces (e.g. menus, dialog boxes), but rather separate strings with non context whatsoever, like error messages.</p>
<p>In this case the visual features of Catalyst are not used and I&#8217;m sure most translators would prefer using a text-specific TEnT like Trados instead of having to struggle with the shortcomings of Catalyst&#8217;s text-editing features.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nick</title>
		<link>http://blog.albatrossolutions.com/localization-tools/alchemy-catalyst-80-localization-environment-pre-announced/comment-page-1#comment-356</link>
		<dc:creator>Nick</dc:creator>
		<pubDate>Thu, 07 May 2009 15:13:20 +0000</pubDate>
		<guid isPermaLink="false">http://blog.albatrossolutions.com/?p=216#comment-356</guid>
		<description>Hi Roberto,
I&#039;ve seen Catalyst 8 in action and posted a review of the launch at Localization, Localisation.
There are some interesting things in this release such progress in the simlutaneous management of TMs and fuzzy matches, multilingual and conditional XML or even the switch to TBX.
Nick.</description>
		<content:encoded><![CDATA[<p>Hi Roberto,<br />
I&#8217;ve seen Catalyst 8 in action and posted a review of the launch at Localization, Localisation.<br />
There are some interesting things in this release such progress in the simlutaneous management of TMs and fuzzy matches, multilingual and conditional XML or even the switch to TBX.<br />
Nick.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
