10 steps to streamlining your localisation process How
- Slides: 40
10 steps to streamlining your localisation process How we halved the production time for a 28 -language documentation suite @3 ditweets
start single file documents (e. g. word) @3 ditweets
goal time | effort | cost @3 ditweets
the scenario @3 ditweets
www. prometheanworld. com @3 ditweets
o interactive panels o seasonal purchasing cycle o 154 countries | 28 languages o recognise need to change @3 ditweets
initial improvements @3 ditweets
reduce text only translate necessary text start global – adapt to local quick install guides @3 ditweets
@3 ditweets
more images replace text with images i. e. Ikea style @3 ditweets
@3 ditweets
fewer docs fewer items to process i. e. multi-lingual guides @3 ditweets
@3 ditweets
words process assets ① less text ② more images ③ fewer docs @3 ditweets
words word count t 9 n cost process complexity @3 ditweets
the brief @3 ditweets
l a u g n i l i t l u m r o f e m i t e l ” c y % c 0 t 5 u c y “ b n o i t a t n e m u c do @3 ditweets
manual tasks copy / paste dtp of lang. versions @3 ditweets
manual tasks time | quality @3 ditweets
improve the source @3 ditweets
structured layout eliminate dtp same rules for all langs. @3 ditweets
o product name o document name o languages o document id @3 ditweets
modular content blocks fit into layout translate blocks reuse content @3 ditweets
style content style applied by rules e. g. css @3 ditweets
o right-to-left languages o specialised fonts @3 ditweets
tool chain manage modular content t 9 n workflow @3 ditweets
@3 ditweets
automate when source (input) optimised errors | time | frequency @3 ditweets
@3 ditweets
, n i t * * “S ”. t u o t * s* anon @3 ditweets
words process ① less text ④ structured layout ② more images ⑤ modular content ③ fewer docs ⑥ style assets content ⑦ tool chain ⑧ automate @3 ditweets
process improve the source simplify the processing time | quality @3 ditweets
10 weeks to <5 weeks throughput @3 ditweets
can we do more @3 ditweets
translation decisions made each round stored in tm / mt quality | frequency @3 ditweets
terminology define key terms - globally stored in database time | quality @3 ditweets
assets time invested in creating need to be managed throughput | quality @3 ditweets
words process assets ① less text ④ structured layout ⑨ translation quality ② more images ⑤ modular content ⑩ terminology ③ fewer docs ⑥ style content ⑦ tool chain ⑧ automate @3 ditweets
? @3 ditweets
o focus on word count less to translate but introduces complexity cost | time | quality o focus on process improve source to reduce manual work time | quality | throughput o focus on assets ? time | quality @3 ditweets