<?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: Translation policy for ICANN</title>
	<atom:link href="http://blog.icann.org/2007/06/translation-policy-for-icann/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.icann.org/2007/06/translation-policy-for-icann/</link>
	<description>Internet Corporation for Assigned Names and Numbers</description>
	<lastBuildDate>Wed, 08 Feb 2012 01:42:27 -0800</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Mark Alford</title>
		<link>http://blog.icann.org/2007/06/translation-policy-for-icann/comment-page-1/#comment-2390</link>
		<dc:creator>Mark Alford</dc:creator>
		<pubDate>Tue, 10 Jul 2007 05:45:50 +0000</pubDate>
		<guid isPermaLink="false">http://blog.icann.org/?p=155#comment-2390</guid>
		<description>ICAN Like any large organization has many challenges when it comes to language and language based communication. Machine translation is poor at best and using Machine Memory is by far and the way best for effective and correct translation. However. contextual or localisation is perhaps the key. We have developed a community of interest publishing tool and this allows users in any language to collaborate and transcreate or loclaise document content via a web browser.At the moment the system is Quark based but we are developing a Word, Excel an PowerPoint tool. Our work flow is XML so population of Web page frames or wires is very simple. In essence we allow localisation of any document based on a user profile and access rites. Finally we deliver a PDF that is a language based facsimile of teh original in any language. Perhaps best of all we are storing the language based on document based on language to language so this can be reused.</description>
		<content:encoded><![CDATA[<p>ICAN Like any large organization has many challenges when it comes to language and language based communication. Machine translation is poor at best and using Machine Memory is by far and the way best for effective and correct translation. However. contextual or localisation is perhaps the key. We have developed a community of interest publishing tool and this allows users in any language to collaborate and transcreate or loclaise document content via a web browser.At the moment the system is Quark based but we are developing a Word, Excel an PowerPoint tool. Our work flow is XML so population of Web page frames or wires is very simple. In essence we allow localisation of any document based on a user profile and access rites. Finally we deliver a PDF that is a language based facsimile of teh original in any language. Perhaps best of all we are storing the language based on document based on language to language so this can be reused.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rafik DAMMAK</title>
		<link>http://blog.icann.org/2007/06/translation-policy-for-icann/comment-page-1/#comment-2383</link>
		<dc:creator>Rafik DAMMAK</dc:creator>
		<pubDate>Mon, 09 Jul 2007 09:41:15 +0000</pubDate>
		<guid isPermaLink="false">http://blog.icann.org/?p=155#comment-2383</guid>
		<description>the main problems with translation policy are the cost and the choice of targeted languages. 
How to finance these tasks? and what is th reasons of choosing languages instead others?</description>
		<content:encoded><![CDATA[<p>the main problems with translation policy are the cost and the choice of targeted languages.<br />
How to finance these tasks? and what is th reasons of choosing languages instead others?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

