<?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: XLIFF&#8230;Where For Art Thou?</title>
	<atom:link href="http://thecontentwrangler.com/2009/04/21/xliffwhere_for_art_thou/feed/" rel="self" type="application/rss+xml" />
	<link>http://thecontentwrangler.com/2009/04/21/xliffwhere_for_art_thou/</link>
	<description>Content is a business asset worthy of being managed</description>
	<lastBuildDate>Thu, 11 Mar 2010 11:29:23 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=abc</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Elliot Nedas</title>
		<link>http://thecontentwrangler.com/2009/04/21/xliffwhere_for_art_thou/comment-page-1/#comment-498</link>
		<dc:creator>Elliot Nedas</dc:creator>
		<pubDate>Thu, 23 Apr 2009 07:19:53 +0000</pubDate>
		<guid isPermaLink="false">http://localhost:8888/ee/?p=285#comment-498</guid>
		<description>&lt;p&gt;Hi Scott,
&lt;/p&gt;
&lt;p&gt;
Great article. We noticed this too and have created XTM with CMS and XLIFF in mind. Based on Open Standards it has a the required filter and import / export functions. And its easily integrated with a CMS.
&lt;/p&gt;
&lt;p&gt;
Spread the word!
&lt;/p&gt;
&lt;p&gt;
Cheers,
&lt;/p&gt;
&lt;p&gt;
Elliot
&lt;/p&gt;</description>
		<content:encoded><![CDATA[<p>Hi Scott,
</p>
<p>
Great article. We noticed this too and have created XTM with CMS and XLIFF in mind. Based on Open Standards it has a the required filter and import / export functions. And its easily integrated with a CMS.
</p>
<p>
Spread the word!
</p>
<p>
Cheers,
</p>
<p>
Elliot</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sarah Maddox</title>
		<link>http://thecontentwrangler.com/2009/04/21/xliffwhere_for_art_thou/comment-page-1/#comment-497</link>
		<dc:creator>Sarah Maddox</dc:creator>
		<pubDate>Tue, 21 Apr 2009 21:21:44 +0000</pubDate>
		<guid isPermaLink="false">http://localhost:8888/ee/?p=285#comment-497</guid>
		<description>&lt;p&gt;Hallo Scott
&lt;/p&gt;
&lt;p&gt;
Great post! Everything you have said about CMSes could equally be applied to wikis. I do technical documentation on a wiki (Confluence, in my case) and translation/localisation is one of the things we have not paid enough attention to yet.
&lt;/p&gt;
&lt;p&gt;
You said it in a nutshell: &#8220;Create robust and easy to use import and export functionality.&#8221;
&lt;/p&gt;
&lt;p&gt;
Cheers, Sarah
&lt;/p&gt;</description>
		<content:encoded><![CDATA[<p>Hallo Scott
</p>
<p>
Great post! Everything you have said about CMSes could equally be applied to wikis. I do technical documentation on a wiki (Confluence, in my case) and translation/localisation is one of the things we have not paid enough attention to yet.
</p>
<p>
You said it in a nutshell: &#8220;Create robust and easy to use import and export functionality.&#8221;
</p>
<p>
Cheers, Sarah</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dierk Seeburg</title>
		<link>http://thecontentwrangler.com/2009/04/21/xliffwhere_for_art_thou/comment-page-1/#comment-496</link>
		<dc:creator>Dierk Seeburg</dc:creator>
		<pubDate>Tue, 21 Apr 2009 19:44:28 +0000</pubDate>
		<guid isPermaLink="false">http://localhost:8888/ee/?p=285#comment-496</guid>
		<description>&lt;p&gt;Hi Scott,
&lt;/p&gt;
&lt;p&gt;
Thanks for your article.&#160; I have had the same experience you have over the past few years.&#160; CMS clients should vote with their wallets and grant contracts only to those vendors whose products include effective integration of open translation standards such as XLIFF and file import and export functionality into their CMS workflows.
&lt;/p&gt;
&lt;p&gt;
As you suggest, I&#8217;ll &#8220;save myself the carpal tunnel&#8221; and won&#8217;t write  about attempts by a few companies to integrate translation functionality into CMS in one way or another.
&lt;/p&gt;
&lt;p&gt;
Cheerio,
&lt;br /&gt;
Dierk Seeburg
&lt;br /&gt;
IcoText - Translation Management
&lt;/p&gt;</description>
		<content:encoded><![CDATA[<p>Hi Scott,
</p>
<p>
Thanks for your article.&nbsp; I have had the same experience you have over the past few years.&nbsp; CMS clients should vote with their wallets and grant contracts only to those vendors whose products include effective integration of open translation standards such as XLIFF and file import and export functionality into their CMS workflows.
</p>
<p>
As you suggest, I&#8217;ll &#8220;save myself the carpal tunnel&#8221; and won&#8217;t write  about attempts by a few companies to integrate translation functionality into CMS in one way or another.
</p>
<p>
Cheerio,<br />
<br />
Dierk Seeburg<br />
<br />
IcoText &#8211; Translation Management</p>
]]></content:encoded>
	</item>
</channel>
</rss>
