A Bad Idea Since 1965

Post-Editing !!

Introducing Interactive, Adaptive MT

Spence Green

spence@lilt.com

Problem #1: User Experiencea slave’s eye view Beyer (1965)

“Why can’t the system learn from my

corrections?” [translators] asked over and

over again. TransType (2005)

A tedious and boring chore Bell Labs (1993)

Problem #1: User ExperienceDid you like the task of post-editing? Moorkens and O’Brien (2015)

Yes No

Fix UX problems with training?

Problem #2: Pricing with MTDiscount for MT?

Which band?TM #

wordsdiscoun

t101% 1 100%95-99%

4 30%

75-84%

8 20%

New 16 0%

??

Input quality of MT?Correlated w/

trans. timeWait for MT

training?

RecapMT + Post-edit an approach that, generally:

Translators have never likedBusinesses can’t value effectively

Loser !!

Les rivières isolées ⇒ Lonely rivers

Interactive predictive typing

Adaptive instantly learn from feedback

Responsive<0.4 sec worldwide

Pricing: Supply Chain Analytics

5,300 words @ 1,237 words / hour

Buyer → LSP1,237 x $0.20 = $247.40

LSP → Translator1,237 x $0.08 = $98.96

CAT Tool REST API

GET /tr?prefix=Lonely

GET /tr?prefix=Lonely%20rivers

GET /tr?prefix=Lonely

%20rivers…

POST /mem?source=&target=

One price unlimited engines, unlimited users

Supercharge the Textarea: lilt.js

Enhance existing UIs

Better/faster crowd/community translationIn-context → sites and apps

There’s never been a better time to stop post-editing

For the Win!