1.
Translation and Crowd Sourcing: Opportunity or Heresy? Professional translators’ attitudes towards massive collaboration Alain Désilets Conseil national de recherches du Canada

2.
“ The most reliable way to forecast the future is to try to understand the present.” “ Trends, like horses, are easier to ride in the direction they are going.” -- John Naisbitt "You have to talk to [customers], watch them; this is the only way to understand their interests, their motives, their needs". -- Donald Norman

3.
Observing Translators <ul><li>Multi-disciplinary project that includes technology researchers from NRC and translation studies researchers from Université du Québec en Outaouais. </li></ul><ul><li>Contextual Inquiry: well known and tried technique in Human Computer Interaction for learning about end users. </li></ul><ul><li>Mix between observation and interviewing. </li></ul><ul><li>Observe potential end users while they work. </li></ul><ul><li>Ask them to think aloud. </li></ul><ul><li>Interrupt with lots of questions. </li></ul><ul><li>Use Qualitative and Quantitative data Analysis to make sense of what you witnessed. </li></ul>

4.
25 subjects Organization type large (250+ employees) LSPs (13), medium (<30 employees) LSPs (6), freelance (2), academic (2), amateur(2) Type of work “ conventional” translation (15), MT-Post Editing (8), Revision (2) Language pairs English -French (13),English-Spanish (6), English-Japanese (2) , Portuguese-Spanish (1), Chinese-English (1), English+Italian-Estonian (1), English-Inuktitut (1) Years of experience Ranged from < 2 years up to 20+ years. Source text domain Aboriginal affairs, Municipal affairs, Public administration, Education, Legal, Health, Software manual, Politics, Job offers. Source text length Min: ~20, Max:7000 Country Canada (15), Europe (5), US (3), Japan (2) Professional translators All but 2.

5.
Preaching the Wiki Word to Translators <ul><li>Involved in world of wikis since 2002 </li></ul><ul><li>Chaired WikiSym conference in 2007 (Montreal) </li></ul><ul><li>Have been telling professional translators about wikis since 2006 </li></ul><ul><li>Keynote at Translating and the Computer 2007: “Translation Wikified” . </li></ul><ul><li>Organized a workshop and panel on those topics. </li></ul><ul><li>Co-implemented wiki-based tools to support translation work </li></ul><ul><li>Cross lingual wiki engine: translate in a wiki context where pre-conditions of traditional translation workflows do not apply (ex: master language). </li></ul><ul><li>Tiki-CMT: TikiWiki module to support Collaborative Multilingual Terminology work. </li></ul>

6.
Talk Outline <ul><li>Are professionnal translators technology averse? </li></ul><ul><li>Professional translators attitudes and workpractices with respect to: </li></ul><ul><li>collaboratively built linguistic resources </li></ul><ul><li>collaborative translation and crowdsourcing </li></ul><ul><li>Please interrupt with questions at any point! </li></ul>

7.
Are professional translators technology averse?

8.
Translation Problems <ul><li>Translators use a lot of technology when trying to resolve translation problems. </li></ul><ul><li>Translation problem = </li></ul><ul><ul><li>any source language word or expression which presents a difficulty for a human translator (not machine) during the process of translation. </li></ul></ul><ul><ul><li>Term, idiomatic expression, named entity, etc... </li></ul></ul>

9.
Tools, Tools, more Tools! Average of 10 resources in our subjects’ toolboxes!!! <ul><li>private (to the individual) lexicons built using simple office suites (ex: Excel spreadsheets, MS-Word documents) </li></ul><ul><li>1 large, public general purpose bi-text (TransSearch) </li></ul><ul><li>private (to the individual) or institutional Translation Memories built with 3 different products (Trados, Multitrans, LogiTerm) </li></ul><ul><li>2 private (to the individual) or institutional, unaligned archives of previous translations, either stored in a database or the file system </li></ul><ul><li>9 unilingual general purpose dictionaries (Multidictionnaire, Petit Robert, Merriam-Webster, Dictionnaire des cooccurrences, dictionary.references.com, Canadian Oxford, Trésor de la langue française, www.dictionary.com, urban dictionary) </li></ul><ul><li>2 unilingual thesauri (Dictionnaire analogique, Dictionnaire des synonymes de l'Université de Caen) </li></ul><ul><li>2 unilingual specialized dictionaries and lexicons (Dictionnaire de droit québécois, Lexique des noms géographiques) </li></ul><ul><li>3 bilingual dictionaries (LexibasePro, René Merteens, Robert & Collins) </li></ul><ul><li>the source text being translated, as well as its partial translation </li></ul><ul><li>bilingual documents related to the source text (ex: minutes of meetings being discussed in the source text)2 instances of the client's Web sites </li></ul><ul><li>2 large, bilingual Web sites not directly related to the domain of the source text (gc.ca domain, Canadian Broadcasting Corporation) </li></ul><ul><li>3 large, bilingual Web sites directly related to the domain of the source text (CanLII, Canadian Federal Court, University of Ottawa) </li></ul><ul><li>the whole Web in the source or target language (mined using Google search engine) </li></ul><ul><li>2 manuals of style (Guide du rédacteur, Le Ramat de la typographie) </li></ul><ul><li>2 spell and grammar checkers (MS-Word, Antidote) </li></ul><ul><li>1 database of newspaper articles in the target language </li></ul>

10.
Tools, Tools, more Tools! (2) Translators use a wide range of tools when resolving translation problems. Vast majority of those are electronic. p < 0.001

11.
Adoption of Corpus-Based Tools <ul><li>Both type equally used. </li></ul><ul><li>Corpus-based tools have made it into the mainstream. </li></ul><ul><li>But they have not displaced Termino-lexicographic tools. </li></ul><ul><li>Termino-lexicographic = </li></ul><ul><li>Dictionary </li></ul><ul><li>Terminology Database </li></ul><ul><li>Lexicon, etc. </li></ul><ul><li>Corpus-based = </li></ul><ul><li>Translation Memory </li></ul><ul><li>Bilingual web site, etc. </li></ul>p > 0.05

12.
Advanced Google Use <ul><li>Translators are among the world’s most advanced Google users. </li></ul><ul><li>They know the advanced syntax, and expect it in most search tools they use. </li></ul><ul><li>They use Google in various ways to mine the web-as-a-corpus </li></ul><ul><ul><li>Ex: search bilingual sites for solutions, assessing usage in target language of particular solutions. </li></ul></ul>

13.
Searching Bilingual Sites

14.
Searching Bilingual Sites (2)

15.
Hot Buttons <ul><li>That said, translators strongly resist technology that either: </li></ul><ul><li>disrupts the fair compensation equation , or </li></ul><ul><li>exerts downward pressure on quality of end product </li></ul><ul><li>Translation crowdsourcing is likely to press on both these buttons. </li></ul>

16.
Fair Compensation Equation <ul><li>Translators are paid by the word. </li></ul><ul><li>Technology that increases productivity exerts strong downward pressure on per-word rate </li></ul><ul><li>Pressure is not always commensurate with actual productivity gain . </li></ul><ul><li>Example: </li></ul><ul><li>10 words sentence with 80% fuzzy match level. </li></ul><ul><li>Should translator only get paid for two words? </li></ul><ul><li>Eventhough she still has to read the whole sentence... </li></ul><ul><li>... and may have to change the rest of the sentence to make it work with the translation of those 2 words? </li></ul><ul><li>Once a new fair equilibrium has been reached, this initial resistance may go away. </li></ul>

17.
Lowering Quality? <ul><li>Translators </li></ul><ul><ul><li>Craftspeople who take pride in the quality of their end product. </li></ul></ul><ul><ul><li>Quality = original sense is rendered, AND translation reads as though it was an original text written by a native speaker . </li></ul></ul><ul><li>Customers </li></ul><ul><ul><li>Translation = cost center, not part of their core business </li></ul></ul><ul><ul><li>Can’t always tell quality when they see it, nor measure clear link between translation quality and bottom line. </li></ul></ul><ul><ul><li>liable to introduce cost-reducing technologies without realizing impact on quality. </li></ul></ul>

18.
Attitudes and workpractices with respect to collaboratively built linguistic resources

19.
Is Wikipedia Useful for Translators? <ul><li>We witnessed very little use of Wikipedia in our translator observation. </li></ul><ul><li>On a few occasions, subjects consulted Wikipedia to get background information on a particular concept, but never to get a solution to a terminology difficulty. </li></ul><ul><li>Analysis conducted in June 2007 indicates that coverage of typical terminology difficulties may be insufficient for the later task (finding equivalents). </li></ul>

20.
Is Wikipedia Useful for Translators (2)? <ul><li>Wikipedia’s coverage of 42 observed terminology problems (June 2007) </li></ul>Note: TERMIUM = Terminology DB of the Gov. Of Canada. WikiPedia Wiktionary TERMIUM Has English entry 71.4% 47.6% 80.1% Has English entry in right sense 57.1% 45.2% 76.2% Has French equivalent 33.3 % 35.7% 76.2% Has French equivalent in correct sense 26.1 % 33.3% 76.2%

21.
Is Wikipedia Useful for Translators (3)? <ul><li>Evolution of translators attitudes towards Wikipedia and wikis: </li></ul><ul><li>4 yrs ago: “Wikipedia, what’s that?” </li></ul><ul><li>3 yrs ago: “I know about Wikipedia and I think it’s crap because any clown can write to it.” </li></ul><ul><li>2 yrs ago: “ You know, Wikipedia is surprisingly good and I use it all the time in my work now.” </li></ul><ul><li>1 yr ago: “This collaborative, wiki stuff is bound to be important for translation, but I am not sure how best to leverage it.” </li></ul>

22.
What Makes a Good Source? <ul><li>Professional Translators are trained to: </li></ul><ul><li>only use trusted sources. </li></ul><ul><li>focus on sources that are specialised for their domain or client. </li></ul><ul><li>never use content that may have been translated, or written by non-native speakers. </li></ul><ul><li>In theory, that would rule out most collaborative sources. </li></ul><ul><li>In practice, translators are pragmatic and will consult sources that do not meet those criteria when necessary. </li></ul>

23.
Use of Public Sources <ul><li>Our subjects used significantly more public resources. </li></ul><ul><li>Many of them available for free (ex: customer’s web site). </li></ul><ul><li>Caveat: Situation is different for highly repetitive, technical translation. </li></ul>p < 0.001 <ul><li>Public = </li></ul><ul><ul><li>Anyone can access, possibly at a fee. </li></ul></ul><ul><li>Private = </li></ul><ul><ul><li>Only accessible to certain translators (ex: those working for particular employer) </li></ul></ul>

24.
Use of General Sources <ul><li>Our subjects used significantly more multidomain resources. </li></ul><ul><li>Seemed to prefer casting a wide net, and then sift the results. </li></ul><ul><li>Caveat: again here, situation is different for highly repetitive, technical translation. </li></ul>p < 0.05 <ul><li>Multidomain = </li></ul><ul><ul><li>Covers multiple domains, and subject searched it without restricting domain </li></ul></ul><ul><li>Single domain = </li></ul><ul><ul><li>Covers single domain, or, covers many, but subject restricted search by domain </li></ul></ul>

25.
Use of Translated Material Our subjects frequently searched in bilingual Canadian sites for French equivalents. Estimated 75% of French content on those sites was translated. Thus, in 75% of the case, this strategy ended up yielding solutions taken from translated material. Frowned upon in Terminology, and, to a lesser extent in Translation. But our subjects did it anyway. Here’s why…

26.
Translator Jugement <ul><li>Subjects exercised a lot of critical judgment w.r.t to resources. </li></ul><ul><li>Did not blindingly trust any source, even highly reputed ones like TERMIUM (Terminology DB of the Gov. of Canada). </li></ul><ul><li>In 35% of the cases, searched in a second resource, after finding some relevant information. </li></ul><ul><li>Subjects adept at rapidly scanning list of suggestions and sifting grain from chaff. </li></ul><ul><li>Problem Coverage (i.e. probability that at least one relevant solution found in top 10), seemed more important than Precision (i.e. probability that a proposed solution is relevant). </li></ul><ul><li>Recall (i.e. percentage of all relevant solutions that is actually proposed by the resource) also seemed important, but to a much lesser degree. </li></ul>

27.
Resources Quality Control <ul><li>Our subjects preferred more tightly controlled resources. </li></ul><ul><li>But still made non-negligible use of Moderately controlled ones (38% of all consultations). </li></ul><ul><li>Almost no use of completely Open resources. </li></ul><ul><li>Tight = </li></ul><ul><ul><li>Carefully crafted and revised (linguists, terminologists, revisers). Ex: TERMIUM. </li></ul></ul><ul><li>Moderate = </li></ul><ul><ul><li>Comes from reputed organizations, but may not be as carefully crafted and revised. Ex: Gov of Canada web sites. </li></ul></ul><ul><li>Open = </li></ul><ul><ul><li>Could have been produced by anyone. Ex: the whole web. </li></ul></ul>p < 0.05 p < 0.001

28.
Write Access <ul><li>Our subjects were predominantly consumers of resources, as opposed to contributors. </li></ul><ul><li>Many comments about lack of time to contribute. </li></ul><ul><li>But in most collaborative resources, only need a small percentage of contributors. </li></ul><ul><li>Read-only = </li></ul><ul><ul><li>Subject cannot write, or can only do so through an intermediary. Ex: TERMIUM </li></ul></ul><ul><li>Read-Write = </li></ul><ul><ul><li>Subject can write directly without an intermediary. Ex: subject’s own lexicon. </li></ul></ul>p < 0.001

29.
Use of collaborative sources is not that common yet, but growing. Collaborative resources go against the grain of some translator attitudes, but nothing that can’t be surmounted. Need to address perception of quality and trustworthiness. Cannot expect majority of translators to contribute.

30.
Attitudes and workpractices with respect to collaborative translation

31.
Flavours of Collaborative Translation <ul><li>In increasing order of controversy: </li></ul><ul><li>Translation teamware </li></ul><ul><ul><li>Allow multidisciplinary teams of translators, terminologists, customers, domain experts to collaborate efficiently on a translation project. </li></ul></ul><ul><li>Online market place for translators </li></ul><ul><ul><li>E-bay like platforms for connecting customers and translators with minimal intervention by a middle man. </li></ul></ul><ul><li>Translation crowdsourcing </li></ul><ul><ul><li>Mechanical Turk style platform for distributing translation projects across large crowds of mostly amateur translators. </li></ul></ul>

32.
Translation Teamware <ul><ul><li>Allow multidisciplinary teams of translators, terminologists, customers, domain experts to collaborate efficiently on a translation project. </li></ul></ul><ul><li>Relatively uncontroversial. </li></ul><ul><li>Many commercial translation workflow products are along those lines, but follow a somewhat assembly-line model. </li></ul><ul><li>More resistance to wiki-like platforms that breakdown barriers and open up horizontal communication channels </li></ul><ul><ul><li>Ex: Customer seeing early drafts of translations, and commenting on them. </li></ul></ul><ul><ul><li>Translators like to (need to?) stay in their own bubble. </li></ul></ul><ul><ul><li>Fear of undue interference by non-qualified staff. </li></ul></ul><ul><ul><li>But starting to see more and more case studies of this (ex: using BaseCamp or wikis to coordinate translation teams) </li></ul></ul>

33.
Online Market Place for Translators <ul><ul><li>E-bay like platforms for connecting customers and translators with minimal intervention by a middle man. </li></ul></ul><ul><ul><li>Ex: ProZ, Translated.net </li></ul></ul><ul><li>Usually includes </li></ul><ul><ul><li>automatic reputation management. </li></ul></ul><ul><ul><li>free, open resources for translators (ex: Kudoz, MyMemory). </li></ul></ul><ul><li>Somewhat controversial: </li></ul><ul><ul><li>Some freelancers perceive it as empowering (cut out the middle man). </li></ul></ul><ul><ul><li>Others perceive it as an impersonal “Wallmart of translation”, i.e. something that encourages , low-quality translation. </li></ul></ul>

34.
Translation Crowdsourcing <ul><li>Mechanical Turk style platform for distributing translation projects across large crowds of mostly amateur translators. </li></ul><ul><ul><li>This is REALLY controversial. </li></ul></ul><ul><ul><ul><li>So far, only heard one professional translator say that this is a good thing. </li></ul></ul></ul><ul><ul><li>Disrupts the fair compensation equation AND exerts downward pressures on quality. </li></ul></ul><ul><ul><ul><li>One crowdsourcing vendor quotes average of $0.0008/word (vs $0.25-0.30/word for your average professional translator). </li></ul></ul></ul><ul><ul><ul><li>Translating out of context is known to be error-prone. </li></ul></ul></ul><ul><ul><ul><li>Amateur translators tend to produce texts that read like translations. </li></ul></ul></ul>

35.
Translation Crowdsourcing (2) <ul><li>One hopes that CrowdSourcing technology will be used wisely and in a way that continues to leverage professional translator skills, for example: </li></ul><ul><ul><ul><li>Crowdsourcing used mostly for low-stake or user-generated content that is currently not being translated at all. </li></ul></ul></ul><ul><ul><ul><li>Professionals continue to play a pivotal role, by revising translations produced by the crowd and paying special attention to amateurs’ main weakness: native-sounding translation. </li></ul></ul></ul><ul><ul><li>But we, researchers and developers, cannot guarantee that this is how things will unfold. </li></ul></ul><ul><ul><li>We need to be sensitive to those issues while we build the future of translation crowdsourcing. </li></ul></ul>

36.
Conclusions

37.
Conclusions <ul><li>Professional translators are NOT technology averse, but they will resist technologies that disrupt the fair compensation equation, or exert downward pressures on quality. </li></ul><ul><li>Crowdsourcing of large linguistic resources is compatible with the views of professional translators, although it is not yet part of their mainstream work practices. </li></ul><ul><li>Also non-controversial, is the use of online collaboration to facilitate team coordination, or to create “fair” marketplaces for freelance translators. </li></ul><ul><li>Crowd-sourcing of translation on the other hand is very controversial in translator circles, and we need to be sensitive to that issue in building and designing translation crowdsourcing environments. </li></ul>

38.
Questions?

39.
Thank you for your attention. For more details… Alain Désilets National Research Council of Canada [email_address]