a standards driven workflow for sitecore localization
DESCRIPTION
When multinational Barco decided to replace their home-grown web CMS with Sitecore they realised this was the ideal moment to further automate the translation workflow of their multilingual website. They turned to Yamagata Europe early in the process to help develop an ideal scenario. This presentation will outline the route that was taken to come to the current workflow, including the difficulties we encountered, and explain the technical set-up, which combines several standards such as TIPP and XLIFF and the memoQ API.TRANSCRIPT
A standards driven workflowfor Sitecore localization
@Fantpmas
Thomas VackierLocalization Engineer
Yamagata EuropeTranslating Knowledge
@YamagataEurope
Our Customer
Used to have a home-grown web CMSthat exported content to Excel
They switched to Sitecore
Their site is big
So is their need for automation
We devised an FTP hand-off
Proprietary ZIP became TIPP
TIPP structure
GUID.tipp
manifest.xml
pobjects.zip
bilingual
tm
term
attachment
Language, task, files
XLIFF
manifest.xml
<TIPManifest version="1.3">...<OrderAction>
<OrderTask><TaskType>Translate</TaskType><SourceLanguage>eng-US</SourceLanguage><TargetLanguage>spa-ES</TargetLanguage>
</OrderTask></OrderAction>...<PackageObjects>
<PackageObjectSection sectionname="bilingual"><ObjectFile> <Type>XLIFFDatabaseExport</Type> <LocationPath>...</LocationPath> <Description>Control rooms</Description></ObjectFile>
...
We wanted clean XLIFF because there is already too much bad XLIFF out there
We also wanted XLIFF to automatically update TMs after revision in Sitecore
<TaskType>TM-Update</TaskType>
XLIFF
...<trans-unit id="..."><source>
<g id="" ctype="x-html-h3">Quick preview</g>
<g id="" ctype="x-html-p">
</g><g id="" ctype="x-html-div" xhtml:class="grayBgBox"><g id="" ctype="x-html-p"><g id="" ctype="x-html-strong">Choose your brightness <x id="" ctype="lb" /></g><x id="" ctype="lb" />From December 2012 onwards, ... </g></g></source>...
linebreaks to help segmentation in memoQ
General workflow
Content is added
TIPP > FTP
Imported via API
TIPP > FTP
TIPP > FTP
Translate in
client
Translations are imported
Review is done in Sitecore
Imported via API
TM update
memoQ workflow
TIPP
ERP
Analysis
Copy & extract
1 project per TIPP File assigned per
market Resources assigned Pretranslation
Cascading filters rock
Cascading filters rock
Groups per market
Different translators per market
memoQ interface for post-processing
memoQ interface for post-processing
Conclusions
Standardization -> AutomationSeveral parties involved
Bye bye file managementAutomatic TM updates
Still time-out issuesOnly one way to ERP