Jim Tivy: The Localization Lifecycle
30
The Localization Lifecycle From CCMS to TMS and back again Jim Tivy, CTO Bluestream Oct 2016
-
Upload
jack-molisani -
Category
Leadership & Management
-
view
44 -
download
3
Transcript of Jim Tivy: The Localization Lifecycle
The Localization Lifecycle
From CCMS to TMS and back again
Jim Tivy, CTO Bluestream Oct 2016
Tower of Babel to reach heaven - Gustave Dore - engraving
Contents
1. Introduction
2. Overview
3. Core Technologies
4. Use Cases of Note
5. Commercial Considerations
6. Summary
Introduction
• Germany, July 2016
– export 96 billion EUR
– import 80 billion EUR
• Features span multiple releases.
• Products release across locales
• Enter, CCMS and TMS +
Overview
Localization Process
Translation Process
• Topic set selection
• Can be incremental
Roles
• Content Development Team
• Localization Manager
• Localization Service Provider
• Translator
• In-Country Reviewer
Core Technologies
DITA
• XML and UTF-8
• Standalone Topics
• Conrefs
• Keys
• Conditional Processing
• Separation of content from presentation
• xml:lang=“fr-FR”
• translate =“no”
• dir=“ltr”
CCMS
• Parallel of source and target files
• Target version -> source version
• Used for publishing (scriptable)
Translation Memory (TM)
• A data model.
• stores segment correspondence
• Often proprietary database.
TMX
<?xml version="1.0" encoding="UTF-8"?> <tmx version="1.4"> <header/> <body> <tu> <tuv xml:lang="en"> <seg>Hello world!</seg> </tuv> <tuv xml:lang="fr"> <seg>Bonjour tout le monde!</seg> </tuv> </tu> </body> </tmx>
Translation Management System (TMS)
• Customers, TMs, Projects
• Roles and Users
• Online Translation Workbench
• Import and Export
– DITA
– XLIFF
• Terminology Management
• Federation
LSP and TMS Process
LSP Process
• Export – Files with remapped links
– Integrated with TMS
• Variations of Extract or Filter
• Analysis – ICE matches (in context)
– 100% matches (somewhere)
– Fuzzy matches (threshold – 70%)
– No match
Skeleton File
<?xml version="1.0" encoding="UTF-8"?> <topic xml:lang="en-US"> <title>%1%</title> <body><p>%2%</p></body> </topic>
XLiff <?xml version="1.0" encoding="UTF-8"?> <xliff version="1.0"> <file source-language="en" target-language="de"> <header/> <body> <trans-unit id="%1%"> <source>The Header</source> <target>Der Header</target> </trans-unit> <trans-unit id="%2%"> <source>The "Generator".</source> <target>Der "Generator".</target> </trans-unit> </body> </file> </xliff>
Reviewing
• Quality Assurance – LSP or…
• Review output to TM problem
• In-country review
LSP Hosted Review
Fixing the Segments
Use Cases of Note
Use Cases
• Basics
• Capture at release time.
• Iterative
• Common Content
• Manual Fixup
Basics
• 1 or n languages
• 1 or n LSPs
Capture
Goal: Capture approved content for version 1
Description: Version 1 of the content is fully approved and development is continuing on version 2.0 content.
Solutions:
– Branch the content
– Export Localization by Label
Iterative
• 60% pre translated
• Agile sprint translations
Common Content
Goal: Prevent re-translation of common content.
Description: Project A and Project B share some common corporate content.
Solutions:
– Separate Project.
– Let the TM handle it.
– Let the old/current CCMS status handle it
Manual Fixup
Goal: To incorporate some image files not translated by the LSP.
Description: Some images translations are handled by manufacturing (they are stickers on machine parts). You receive this set of images and now must incorporate these images into the translated content.
Solutions: – Direct Insertion into the CMS with Fixup.
Commercial Considerations
• Owning the TMS or TM
• Cost per word – cost of living
– German 20c
– Chinese 12c
– Malta 50c
• Project management fee: 8%
• No per TM cost.
• No cost for ICE matches
Summary
• Well known use cases
• Well understood techniques
• Proper factoring of tools
• Equals best practices
