The document describes a standards-driven localization workflow developed by Yamagata Europe for a customer that switched from a home-grown CMS to Sitecore. The workflow involves exporting Sitecore content as TIPP packages containing XLIFF files, sending those packages via FTP to a translation management system (memoQ), translating the content, then importing the translated packages back into Sitecore where the translations are reviewed. The workflow aims to provide clean XLIFF, automatically update translation memories, and facilitate the involvement of multiple parties through standards and automation.

1. A standards driven workflow
for Sitecore localization

2. @Fantpmas
Thomas Vackier
Localization Engineer

3. Yamagata Europe
Translating Knowledge
@YamagataEurope

4. Our Customer

5. Used to have a home-grown web CMS
that exported content to Excel

6. They switched to Sitecore

7. Their site is big

8. So is their need for automation

9. We devised an FTP hand-off

10. Proprietary ZIP became TIPP

11. TIPP structure
GUID.tipp
manifest.xml
pobjects.zip
bilingual
tm
term
attachment
Language, task, files
XLIFF

12. 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>
...

13. We wanted clean XLIFF because there is
already too much bad XLIFF out there

14. We also wanted XLIFF to automatically update
TMs after revision in Sitecore
<TaskType>TM-Update</TaskType>

15. 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

16. General workflow
Content is
added
TIPP >
FTP
Imported via API
TIPP >
FTP
TIPP >
FTP
Translat
e in
client
Translations are
imported
Review is done
in Sitecore
Imported via API
TM
update

17. memoQ workflow
TIP
P
ERP
Analysis
Copy & extract
 1 project per TIPP
 File assigned per market
 Resources assigned
 Pretranslation

18. Cascading filters rock

19. Cascading filters rock

20. Groups per market

21. Different translators per market

22. memoQ interface for post-processing

23. memoQ interface for post-processing

24. Conclusions
Standardization -> Automation
Several parties involved
Bye bye file management
Automatic TM updates
Still time-out issues
Only one way to ERP