160 likes | 290 Views
Modelling Continuous Translation. Fred Hollowood. Assumptions. 3. Examine the traditional model. Goals. 2. 1. Challenges. Continuous Model. Building / Assembly. 6. 4. 5. Agenda. Goals. Need to deliver language products simultaneously
E N D
Modelling Continuous Translation Fred Hollowood
Assumptions 3 Examine the traditional model Goals 2 1 Challenges Continuous Model Building / Assembly 6 4 5 Agenda
Goals • Need to deliver language products simultaneously • Maximise translation activity before source completion • Translation automation options • Connect the translator to the writers’ CMS system • Use MT to increase throughput in the translation phase • Translate as source content becomes available • Build deliverables regularly • Implies mixed language interim results • Release Phase • Little new content • Experienced with deliverable builds
Translation timing - Reprise New version • Apply a multi-drop model to black-box writing process New writing Legacy Writing phase Release Phase Time t0 • Best guess readiness determines timings • Wide variation among writing groups • More drops more cost • “Wait until you see the whites of their eyes” • Terminology a translator task
rm Res 3% to 38% 90% ri 100% Writing phase Release Phase t2 Time t0 t1 tr Traditional Translation Model • t0 Start of translation phase • t1 Start of source release phase • t2 End of source release phase • tr End of localisation release phase • ri Steady state translation resource • rm Peak translation resource
Challenges • Apply a continuous translation model to a transparent writing process • Regular metrics determine timings • Recognise your writing groups • Cost controlled by measuring and limiting “rewrites” • Agree when to start and how much to do • Terminology extraction becomes a continuous process • Develop automated and continuous QA
Assumptions • Source topics can be identified as “ready” • Source flagged as “ready” can commence translation immediately • Source classed as “ready” should not be revisited • Source classed as “translated” recognised to incur expense if revisited • Deliverables preparation is clearly defined and scheduled • QA is segmented into language and functional activity
120k words 8d/w 2d/w Continuous Translation Model Res rm ri Writing phase Release Phase t2 Time t0 t1 tr 24 hours 8 weeks 2 weeks • t0 Start of translation phase • t1 Start of source release phase • t2 End of source release phase • tr End of localisation release phase • ri Steady state translation resource • rm Peak translation resource
It is not all about translation…… • Look at your critical path • Building and bug fixing follow translation • Resource bound • End-game stuffed with novel translations • A 2 or 3 week old process at best
Assembly Traditional Translation-Assembly rm Res 90% ri 100% Writing phase Release Phase t2 Time t0 t1 tr • t0 Start of translation phase • t1 Start of source release phase • t2 End of source release phase • tr End of localisation release phase • ri Steady state translation resource • rm Peak translation resource
Res rm ri Translation Assembly Writing phase Release Phase t2 Time t0 t1 tr Assembly Model • t0 Start of translation phase • t1 Start of source release phase • t2 End of source release phase • tr End of localisation release phase • ri Steady state translation resource • rm Peak translation resource
Untouched topics Topics Ready New writing Concepts Reference Task Time t0 Alpha Beta Writing phase Release Phase Dewey Updates Managing Continuous Translation • Keep the infrastructure functioning • Monitor the content development • Drive down rewriting • Early warning on “release phase” churn • Visibility inside the “black box” CTS
Topics Streamed for Translation • A “little” often • Spread the release of topics across a significant timescale • Design deliverables early • Allows localisation to build partially translated deliverables constantly (automatically) • Topics for translation • Concepts first • Reference next • Tasks as they become fixed
Q and A fhollowood@symantec.com