Technical communication and Translation

MTM LinguaSoft, © 2016 – Do not copy, reproduce or share without permission www.mtmlinguasoft.com

Made-To-Measure Language Solutions

Technical Communicators & Translators

Let’s speak the same language!Presented by Myriam Siftar, MTM LinguaSoftSTC Conduit, April 2nd, 2016

http://www.mtmlinguasoft.com/



Agenda

1. Why does localization matter?

2. Process overview

3. Factors that increase costs

4. Best practices

5. Summary




infographic, created by Alberto Lucas Lopéz for the South China Morning Post


http://www.lucasinfografia.com/Mother-tongues

http://www.lucasinfografia.com/Mother-tongues

http://www.scmp.com/infographics/article/1810040/infographic-world-languages



Content explosion• Need to create global content value chain

Seeking increased foreign markets share

Multilingual is a requirement, not a nice to haveo Compliance, regulations, mandateso User-generated contento Customer satisfaction and experience

• Needs to move from afterthought to forethought

Improve ROI and project success Old ways negatively impact agility, not responsive




• Localizing iPhone app increased downloads rate by128% per country.

• 26% increase in revenue for each country added via app localization - achieved within just one week

App localization effect




Definitions

Translation: replacing text in one language with text of equivalent meaning in another language.

Localization: includes all of the changes needed to adapt content for a particular market, to take into account things like local time, date, and currency formats; cultural preferences about content; UI and design choices.

Translation is part of Localization




Content Production Flow– Traditional “over the wall” model

AssemblyQA and

ApprovalSource language

Localizedvariants

LSP

Translation

Authoring

Static or dynamiccontent delivery

Tech manual

Source: Burton GROUP, 2008




Content Production Flow– Newer flow with localization in mind

Authoring

TMS

AssemblyQA and

Approval

Source language

Localizedvariants

CMS

LSP

Translation

Static or dynamiccontent delivery

Tech manual

Source: Burton GROUP, 2008




Value chain components

Authoring CMS TMS Translation

Single Sourcing(e.g. DITA)

XML-based

SourceLanguage QA

Documentmanagement

Web contentmanagement

Workflow/ PM

APIs

Translationmemory

Terminologymanagement

Human

Automated

Costing




Localization components

Localization

Translationmemory

Terminologymanagement

Human

Automated

AV assets




Translation ProcessSource file

received and prepped for translation ------------

Apply existing TM if any

Prepared file to translator

----------CAT & QA

Tools

Translated file to editor/proofreader who

marks changes------------------

CAT & QA tools

Translator and editor reconcile disagreements

Target file reviewed for specific client

requirements, final---------------

QA tools & TM update

Target file to client for publishing




Translation memory

Source: www.millercaldwell.org


http://www.millercaldwell.org/



Translation memory savings Comparison of Translation Costs with and without TM

(thousands of dollars)




MT decision tree




Cost Factors

• Need for pre-translation file prep• Number of words involved• Type of material (i.e., technical, specialized)• Need for post-translation file manipulation• Need for graphic/AV assets localization• Timeframe• Amount of repeated content or matches from

earlier translation (TM)




Factors That Increase Costs

1. Bad Content

• Unnecessary or verbose content

• Ambiguous content

• Unnecessary changes to already translated text

• Using different terms to mean the same thing





2. Bad Design / File Format

• Wrong authoring tool for purpose

Won’t play well with translator’s tools

• Misuse of authoring tool

• Embedded text





3. Lack of or bad planning

• Having more than one person in charge

• Assuming unrealistic timelines

• Making content changes in mid-process

• Inefficient in-country process




Best practices

• Build customer profiles for each local market

• Connect business goals with expectations of real prospects and customers

• Analyze content type

Source: Common Sense Advisory, Inc.

Explore content-tiering approach




Best practices

• Promoting single sourcing • Content with high reuse potential should be

authored with DITA• XML cures localization headaches

• Verify cultural sensitivity (caution with maps, colors, icons and symbols)

• Use design templates that can work in multiple languages

What can you do when authoring?




• Write excellent English but keep the tone more informal rather than stiff

• Learn about simplified English / Remove ambiguity

Best practices




Removing ambiguity

Think about terminology managementSamples to consider:

1. Different terms, same concept:• defect report, problem report, incident report, fault report• filler cap, fill cap and radiator cap• term in UI does not match term in Help

2. Same term, different concept• stock: inventory or shares• default: value in the absence of a user selection or failure

to make required payments




Removing ambiguity

Think about terminology management

Samples to consider (ctd)

3. Ambiguous usage:• Replace X: Put X back Substitute Y for

X• Last screen Previous screen Final screen

4. Avoid buzzword – one per sentence is enough




Terminology

Error propagation over time from a single error

0100

200300

400500

600

Design Authoring Translation

Stage of document life cycle

Erro

r Pro

paga

tion

1 error X 10 documents x 5 products= 50 errors

X 10 languages= 500 errors

Ignore at your own peril




Choose consistency over variation

Best practices




List all acronyms, abbreviations, technical terms, product names, corporate terms and other terms not to be translated.

Best practices

Terminology management + Style guides

Consistency and cultural neutrality




Best practices

Authoring, automation & consistency matter

Cost control tactics• Content-tiering • Planning• Selecting optimal workflow• Implementing language QA software at source and post• Partnership




• Educate yourself on localization• Move localization upfront• Review, test, implement proofs of concept• Help management with business case for a

content localization strategy• Technical communicator and LSP are partners

– each other’s advocates• Successful localization starts with the technical

communicator

Final recommendations




Questions / Contact

Follow us @mtmlinguasoft

Download our white papers

Learn more, visit our blog


https://twitter.com/mtmlinguasoft



http://www.mtmlinguasoft.com/mtm-linguasoft-white-papers-2/

http://www.mtmlinguasoft.com/blog/



Business

Technical communication and Translation