<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>experience matters &#187; CT3</title>
	<atom:link href="http://experiencematters.criticalmass.com/tag/ct3/feed/" rel="self" type="application/rss+xml" />
	<link>http://experiencematters.criticalmass.com</link>
	<description>great customer experiences and what it takes to pull them off</description>
	<lastBuildDate>Mon, 06 Feb 2012 23:11:04 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1</generator>
		<item>
		<title>CT3: Twitter Goes Multilingual</title>
		<link>http://experiencematters.criticalmass.com/2009/11/03/ct3-twitter-goes-multilingual/</link>
		<comments>http://experiencematters.criticalmass.com/2009/11/03/ct3-twitter-goes-multilingual/#comments</comments>
		<pubDate>Tue, 03 Nov 2009 18:01:13 +0000</pubDate>
		<dc:creator>William Bertolo</dc:creator>
				<category><![CDATA[Emerging Technology]]></category>
		<category><![CDATA[CT3]]></category>

		<guid isPermaLink="false">http://experiencematters.criticalmass.com/?p=996</guid>
		<description><![CDATA[Twitter announced last week that it would be using CT3 (community, crowdsourced and collaborative translation) to make its content available in the FIGS (French, Italian, German and Spanish) group of languages. They’re stepping on ground that brought some trouble to LinkedIn some time ago. Despite specific website approaches, the CT3 matter will be sure to [...]]]></description>
			<content:encoded><![CDATA[<p></a>Twitter announced last week that it would be using <a href="http://www.globalwatchtower.com/2009/10/13/twitter-migration">CT3</a> (community, crowdsourced and collaborative translation) to make its content available in the FIGS (French, Italian, German and Spanish) group of languages. They’re stepping on ground that brought some trouble to <a href="http://www.globalwatchtower.com/2009/06/19/linkedin-ct3/">LinkedIn</a> some time ago. Despite specific website approaches, the CT3 matter will be sure to generate a lot of debate in the times to come. So it would be nice to start understanding the factors that surround it.<br />
<img src="http://experiencematters.criticalmass.com/wp-content/uploads/2009/11/multilingual-twitter-300x285.jpg" alt="CT3" title="CT3" width="300" height="285" class="alignleft size-medium wp-image-998" /></p>
<p>The first factor is resistance. Professional translators may feel their market is at risk. To be honest, as a web developer, I felt the same in the past, when potential clients started considering the option of having their nephews, who “knew a bit of HTML”, build their corporate sites. So they probably question how people, who are not even professionals in the language area, can do their work for free, especially for-profit corporations. On the other hand, this kind of initiative can even bring more work for language professionals, as it can create opportunities for proofreading content which didn’t exist before.</p>
<p>On the CT3 defense side, it’s said that costs are not the motivation of crowdsourcing. CT3 is desired because it’s faster, better, wider and democratic. The article about LinkedIn I mention above goes deeper into this discussion, but I’ll try to summarize it below.</p>
<p>It’s faster: whoever has worked with contracting services for a specific business knows how long and painful the process can be. Vendor selection, contract process, prototype design, implementation and tests can take months. CT3 can bring results in a fraction of this time, as you can check out in this <a href="http://www.globalwatchtower.com/2008/08/14/community-translation-lifts-facebook-top-social-networking">article about the Facebook experience</a>.<br />
<span id="more-996"></span><br />
It’s better: subject-matter experts, the given website end users and regional language speakers can bring the quality of the content to its best, aside from the use of specific regionalisms.</p>
<p>It’s wider: when people get involved, they tend to increase the word of mouth effect, which is particularly good from a marketing standpoint.</p>
<p>It’s democratic: In some cases, the website users can vote if a given translation is proper to that case. That’s even more interesting than the traditional single writer/editor model.</p>
<p>Studies show that the social networking traffic has begun to stabilize in North America, but rapid growth can be seen in other parts of the globe (35 percent in Europe, 66 percent in the Middle East-Africa region, 33 percent in South America and 23 percent in Asia). In a June 2007-2008 comparison, Facebook traffic in Latin America grew 1055 percent (from 1 million to 12 million unique visitors/month). It only shows the potential reach a website can gain from having its content translated into multiple languages.</p>
<p>From different standpoints, CT3 can be good or bad, but it seems to have worked well for some enterprises. The most important thing to take into consideration, though, is how to conduct this effort along with the community, because that seems to be the most delicate point of the discussion.</p>
]]></content:encoded>
			<wfw:commentRss>http://experiencematters.criticalmass.com/2009/11/03/ct3-twitter-goes-multilingual/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
	</channel>
</rss>

