<?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: Worldwide Lexicon and the Firefox Universal Translator add-on</title>
	<atom:link href="http://blog.mozilla.com/seth/2009/08/26/worldwide-lexicon-and-the-firefox-universal-translator-add-on/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.mozilla.com/seth/2009/08/26/worldwide-lexicon-and-the-firefox-universal-translator-add-on/</link>
	<description>localization and community at mozilla</description>
	<lastBuildDate>Tue, 07 Jun 2011 10:48:15 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Apartments</title>
		<link>http://blog.mozilla.com/seth/2009/08/26/worldwide-lexicon-and-the-firefox-universal-translator-add-on/comment-page-1/#comment-143641</link>
		<dc:creator>Apartments</dc:creator>
		<pubDate>Thu, 17 Sep 2009 21:12:47 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mozilla.com/seth/?p=552#comment-143641</guid>
		<description>I should tell that this information is very interesting to me &lt;a href=&quot;http://kiev-apartments.com.ua&quot; rel=&quot;nofollow&quot;&gt; Kiev apartments for rent. &lt;/a&gt;</description>
		<content:encoded><![CDATA[<p>I should tell that this information is very interesting to me <a href="http://kiev-apartments.com.ua" rel="nofollow"> Kiev apartments for rent. </a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Blow</title>
		<link>http://blog.mozilla.com/seth/2009/08/26/worldwide-lexicon-and-the-firefox-universal-translator-add-on/comment-page-1/#comment-143544</link>
		<dc:creator>Chris Blow</dc:creator>
		<pubDate>Thu, 10 Sep 2009 09:56:26 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mozilla.com/seth/?p=552#comment-143544</guid>
		<description>I&#039;m pretty excited about the WWL API design because it relies on a version controlled translation memory. True, it is a little slow because it parses and replaces the DOM. But this &quot;outside in&quot; approach makes it really platform independent.

The fact that you can host your own translation memory is very significant if you are running a large organization doing translation, or crowdsourcing.

I work for a nonprofit is using the WWL API to manage a collaborative translation effort -- http://meedan.net. We think WWL is really important. In particular, this part: http://www.worldwidelexicon.org/api

If you are already invested in translating your content, the WWL API really saves effort  -- it gives you a machine-translated baseline for your translators, from the translation services of your choice. Your translators are all available over an API, which can talk to a server that you own. This is different from the Google Translation Toolkit, in that it can use any translation API (eg, Yahoo) and you can do whatever you want with the translation metadata.

The Firefox Toolbar is especially cool seen in this context, since it makes the system usable with no setup, and an Open Source backend.

Here is an O&#039;Reilly Radar review: 
http://radar.oreilly.com/2009/08/world-wide-lexicon-toolbar-cha.html

&quot;Brian McConnell&#039;s latest coding effort, World Wide Lexicon Toolbar, meets my criterion for a piece of critical infrastructure: after two days with it I can&#039;t get along without it, and I plan to avoid any browser that doesn&#039;t have it installed.&quot;</description>
		<content:encoded><![CDATA[<p>I&#8217;m pretty excited about the WWL API design because it relies on a version controlled translation memory. True, it is a little slow because it parses and replaces the DOM. But this &#8220;outside in&#8221; approach makes it really platform independent.</p>
<p>The fact that you can host your own translation memory is very significant if you are running a large organization doing translation, or crowdsourcing.</p>
<p>I work for a nonprofit is using the WWL API to manage a collaborative translation effort &#8212; <a href="http://meedan.net" rel="nofollow">http://meedan.net</a>. We think WWL is really important. In particular, this part: <a href="http://www.worldwidelexicon.org/api" rel="nofollow">http://www.worldwidelexicon.org/api</a></p>
<p>If you are already invested in translating your content, the WWL API really saves effort  &#8212; it gives you a machine-translated baseline for your translators, from the translation services of your choice. Your translators are all available over an API, which can talk to a server that you own. This is different from the Google Translation Toolkit, in that it can use any translation API (eg, Yahoo) and you can do whatever you want with the translation metadata.</p>
<p>The Firefox Toolbar is especially cool seen in this context, since it makes the system usable with no setup, and an Open Source backend.</p>
<p>Here is an O&#8217;Reilly Radar review:<br />
<a href="http://radar.oreilly.com/2009/08/world-wide-lexicon-toolbar-cha.html" rel="nofollow">http://radar.oreilly.com/2009/08/world-wide-lexicon-toolbar-cha.html</a></p>
<p>&#8220;Brian McConnell&#8217;s latest coding effort, World Wide Lexicon Toolbar, meets my criterion for a piece of critical infrastructure: after two days with it I can&#8217;t get along without it, and I plan to avoid any browser that doesn&#8217;t have it installed.&#8221;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Aaron Strontsman</title>
		<link>http://blog.mozilla.com/seth/2009/08/26/worldwide-lexicon-and-the-firefox-universal-translator-add-on/comment-page-1/#comment-143239</link>
		<dc:creator>Aaron Strontsman</dc:creator>
		<pubDate>Thu, 27 Aug 2009 10:36:50 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mozilla.com/seth/?p=552#comment-143239</guid>
		<description>I don&#039;t think this is going to work well. Why? Active websites are often updated every day, the web is huge and it can take a lot of time to make machine translations into proper translations. And besides, the add-on is tedious to use.</description>
		<content:encoded><![CDATA[<p>I don&#8217;t think this is going to work well. Why? Active websites are often updated every day, the web is huge and it can take a lot of time to make machine translations into proper translations. And besides, the add-on is tedious to use.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

