localization -writepoint & net translators

© 2010 WritePoint Ltd. All rights reserved.

Localization and Technical Writing: Living together in perfect harmony?


Start With the Basics

TW has the largest impact on localization (l10n)Good TW leads to good translation t9nTranslating technical doc is not translating lit.Simplicity is the key


Set the Pace/Plan

Consider writing up a Translation Guide


Translation Guide

Typically written by Documentation Manager or technical writer

Tasks that need to be completedWho needs to do whatDeadlines for each stageWhat is transferred in each stageFinal goals and deliverables


Translation Guide

DO YOU REALLY WANT THE EXTRA WORK??Save yourself time and grief Vendor vs. DIY

MLV vs. SLVKitbag ?There are a LOT of translators out thereChoose one who will do it “RIGHT”!Do it “Write” the first time


Translation Guide

Specify Assumptions Do you assume translators have experience with help files, complicated formats, templates?Who is working with what tool (versions)


Translation Guide

Define the Tasks Technical Writers (today’s focus)TranslatorsEngineers / DevelopersQA Team


Technical Writing Tasks

Writing documentationProducing online help files (if any)Transfer of files to translatorsBe available for questions


Translation Guide

Define key areas Set requirements Monitor the process Evaluate results

This will enable you to hit a home run each and every time


From the initial stagesProject PlanningLocKitTranslationTestingLinguistic quality checks with industry defined metricsAutomated checks


Writing Rules

Use active tenseEasier to translateLess complexLess likely to be misunderstood/mistranslated

For instructions, use the imperative mood “Select on option from the combo list, then click Save.


Writing Rules

Standard Technical Writing Rules ApplyWrite clearlyWrite conciselyWrite consistently


Writing Rules

If you use a word as a noun, don’t also use it as a verb or to describe something different

Example: “account” has specific meaning in finance, so don’t say “account for the missing values in the user account”


Writing Rules

Don’t use idiomatic phrases (as a rule of thumb, on-the-fly, etc.) Avoid cultural examples Avoid country-specific examplesUse serial commas in a list, so that it’s clear which item goes with what (e.g., red, blue, and white) Avoid using compound sentences

Translations into some languages produce much longer sentences


Writing Process

Prepare a glossary that you can give to the translators.Verify that all technical writers are using it.Verify that all translators receive it.Use it as a style guide for the rest of the translation.


Writing Process

Glossary=TermBaseTwo types of Databases

Translation MemoryTermBase

TW for t9n is not a creative writing class, do not use synonyms (what’s another word for synonym), if you use socket an outlet you will need to add another entry to your glossary


Do FULL QA BEFORE Translation

Page breaks don’t matter…but these do:Formatting/styling PunctuationHeading structureOrganizationClear sentences, no missing words


Pre QA and Content review

Localization is the one place you don’t want to recycleContent review allows us to identify possible failure points before translationPre-DTP allows us to address issues such as:

Identify text which may be embedded in an imageDelete extra spacesPrepare documentation which is being translated but not having the UI translated WORD “WORD”Adding correct and consistent styles or fonts which support other languagesChange Shift+ENTER with spacesetc


Working with Graphics

Link to graphics rather than embedding them (where possible)

Saves timeDon’t need to reinsert them

Graphics need to be translated via a graphics editor, not in the text translation tool.

Save them in editable format. Consider using numbers instead of text for callouts.


Single-Sourcing

To keep your costs down, use single sourcing

Avoid lengthy topics and unnecessary verbageDon’t send topics that haven’t changed and therefore don’t need translating again. Keep track of your files and graphics, so that you know what has changed.


Single Sourcing et al

Reusability ProcessSave on DTP time and effortConsistencySAVE $$$$$$$$$$$$$ROI is very short when translating


Round Two Realities

Be careful what you change.Example:

Round 1: The Events Window can be used to schedule events.

Round 2a: The Events Window can be used to create events.

Round 2b: Use the Events Window to create events.


Round Two Changes

Don’t change text needlesslyAlert translators to major changes

Blocks of text that have been added or deletedChanges in terminology


Define Rules for Translation

According to company rules of look and feelCapitalization Abbreviations, acronyms, and trademarks Copyright statementsGraphic presentation and titling Reference usage and listing Numerical and unit conventionsOthers specific to your business


Technical Writing Tasks

Define terms that remain in EnglishCompany nameDefault passwordsProduct nameInterface options (?)


Managing a Translation Project

Set the goals: what gets translatedOrganization of the source content Scheduling of the content release, along with the translated content Managing of freelancers/agencies Communication between engineers/technical writers/translators/customer or end use


Managing a Translation Project

Check whether translator/agency uses translation memory software

Decreases your costs dramaticallyProtects source code in help files


How the customer sees the project 3

Thank you…

Questions?

localization -writepoint & net translators

Technology

translation guide

translation project

technical writing tasks

rules dont

text translation tool

dont need

good translation t9n

translation predtp