Automating Content Automating Content Localization: Localization:
DITA + XLIFF + CMSDITA + XLIFF + CMS
Tony JewtushenkoTony JewtushenkoCoCo--Chair, OASIS XLIFF TCChair, OASIS XLIFF TCDirector, Product Innovator Ltd, Dublin IrelandDirector, Product Innovator Ltd, Dublin Ireland
[email protected]@ProductInnovator.com
www.oasis-open.org
What is a CMS?
Creates or acquires contentOrganizes and structures the contentStores content and metadata in a repositoryBusiness and workflow rules that customize and retrieve contentPublishes format & output
Why use a CMS?
Benefits any organization producing content with:
Lots of contributorsLots of revisionsLots of contentLots of different publication formatsNeed for fast turnaroundNeed for high quality
www.oasis-open.org
Content Management Systgem (CMS) Workflow
<Pub
lishi
ng>
<Rep
osito
ry>
<Tra
nsla
te>
<Aut
horin
g>
DocumentCreation
Review /Edit
Store/update
Store/update
Review /Approve
XHTMLPDF HTMLHelp
Deploy Archive
What is a GMS?
A Globalization Management System consists of:
A CMS to connect withCMS ConnectorsWorkflow EngineTranslation RepositoryCAT Software: TM, TermBase, MT
In a Nutshell: A CMS + Workflow for Pre-translation
www.oasis-open.org
CMS Workflow with GMS
<Pub
lishi
ng>
<Rep
osito
ry>
<Tra
nsla
te>
<Aut
horin
g>
DocumentCreation
Review /Edit
Store/update
Store/update
Review /Approve
XHTMLPDF HTMLHelp
Deploy Archive
GMS
Elements of a GMS
CMS’s / GMS’s that support DITA and XLIFF
An XLIFF document is a container for all localization data1. Localizable objects (e.g. text strings,
graphics) in source and target languages.2. Supplementary information (e.g. glossaries,
or material to recreate the original format).3. Administrative information (e.g. workflow
data).4. Custom data (e.g. initialization information
for tools).
XLIFF Bilingual ModelEach <file> element is designed to store one source language and one target languageThe rationale is that the translation of different target language is done by different people most of the timeHowever, languages in <alt-trans> element can be different. For example, proposed matches in national Portuguese when translating into Brazilian Portuguese.
Desktop Localization with DITA & XLIFF
Author
Translator
LocalizationManager Translation Kit
Term Base
Translate
LinguisticReviewer
Review
DITA
TM Term Base
MachineTranslation
Enterprise Localization Automation with DITA & XLIFF
Author
Translator
XLIFF
LocalizationManager
XLIFF Translation Kit
100% match
TranslationRepository
XLIFF Editor
XLIFF Translation Kit
Translate
RequiresTranslation
100%Translated
<100% Translated
100%Translated
Fuzzymatch
TranslationMemory
MachineTranslation
MachineTranslate
Update
CMS
LinguisticReviewer
Review
Pre & Post Translation Workflow
(GMS)
DITA
PubsManager
Why use XLIFF?DITA content with metadata to automate the localization workflowGreater control over localization assets & workflow
Saves $$$Faster turnaroundBetter quality
Reduces vendor lock-inOpen XML format for localization kitsIntegrates with other open L10n standards like xml:tm, SRX and OAXAL
OAXAL: a new OASIS TC
“Open Architecture for XML Authoring and Localization”Chaired by by Andrzej Zydron, XML-IntlBasic concept is: xml:tm + DITA + XLIFFhttp://www.oasis-open.org/committees/tc_home.php?wg_abbrev=oaxal
OAXAL Architecture
From: http://www.xml.com/pub/a/2007/02/21/oaxal-open-architecture-for-xml-authoring-and-localization.html?page=1
OAXAL Translation Scenario
extractExtracted
texttm process XLIFF
file
update matching
leveraged matching
Automatic Process
Publishing
xml:tmsource
text
Web service/ interface
mergeAutomatic Process
TranslatorTranslateQAWeb
xml:tmtarget text
From:http://www.gca.org/xmlusa/2004/slides/zydron/Coping%20with%20Babel%20-%20how%20to%20localize%20XML.ppt#40
Takeaways:XLIFF enhances DITA support for localization:
project management workflowsupplemental filestranslation memory metadata
DITA with XLIFF can save translation $$$XLIFF is an open standard for localization kit package for pre and post translationDITA with XLIFF reduces vendor lock-in
Questions?