A standards driven workflowfor Sitecore localization
@FantpmasThomas 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 structureGUID.tippmanifest.xmlpobjects.zipbilingualtmtermattachmentLanguage, task, filesXLIFF
manifest.xml<TIPManifest version="1.3">...<OrderAction><OrderTask><TaskType>Translate</TaskType><SourceLanguage>eng-US</So...
We wanted clean XLIFF because there isalready too much bad XLIFF out there
We also wanted XLIFF to automatically updateTMs 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="" ct...
General workflowContent isaddedTIPP >FTPImported via APITIPP >FTPTIPP >FTPTranslate inclientTranslations areimportedReview...
memoQ workflowTIPPERPAnalysisCopy & extract 1 project per TIPP File assigned per market Resources assigned Pretranslat...
Cascading filters rock
Cascading filters rock
Groups per market
Different translators per market
memoQ interface for post-processing
memoQ interface for post-processing
ConclusionsStandardization -> AutomationSeveral parties involvedBye bye file managementAutomatic TM updatesStill time-out ...
Upcoming SlideShare
Loading in …5
×

A standards driven workflow for Sitecore localization

2,017 views

Published on

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.

Published in: Technology, Business
0 Comments
3 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
2,017
On SlideShare
0
From Embeds
0
Number of Embeds
176
Actions
Shares
0
Downloads
24
Comments
0
Likes
3
Embeds 0
No embeds

No notes for slide
  • Localization EngineerTools guyAll-round troubleshooterQA Distiller
  • WewriteWetranslateWeprintWepackage
  • U2 videowallsMedical imagingMilitaryimagingWe&apos;vetranslatingforthemforover 5 yearsnow.
  • Excel isprobablythemostmisusedtool in thehistory of mankind, usedforeverythingbutspreadsheets. And unfortunatelyvery popular with software peoplewhothinkthey&apos;redoingus a favourbychuckingit in Excel.
  • High endcorporate web cms .NETYouknowit&apos;shighend and priceywhenyoudon&apos;tseeanypriceslisted and a list of Partnersonthesite.
  • 11 languagesincluding English.Wetranslateinto 9 languages. Barco does English and dutch in house.
  • FirstobviouscandidateisClayTablet.Webinar, didsometests. Beautiful.But comes at a heftypricetag.Lionbridgedidsomething. Vendorlockin. We&apos;reniceguys, wewantedan open solution.
  • Watched foldersLocal servicesto pick them up.Set up a packageformat. Zip format.
  • Firstheard of TIPP at 1st XLIFF symposium in Limerick viaMicahBlyfromMedtronic.PragmaticbunchcalledInteroperabilityNow. Includes Kilgray, Ontram, XTM, Spartan Software.Tookthespecthatwasalreadypublished, notfinalized.
  • TIPP structurezipwith a manifest XML describes content and alsoTaskWehave a bare-bonesimplementationwithouttm, term and attachment as these are allmanaged in memoQBilingual files are XLIFF.Thiswasthebiggesthurdle in theimplementation, convertingraw Sitecore XML intogood XLIFF.
  • Bad XLIFF: customnamespacestakingovercore XLIFF functions, ruininginteroperabilityEscaped HTML tags, orevenworse, CDATA elements!
  • Clean &gt; correctinlinetagging no escaped HTMLNo customnamespacesSegmentation &gt; done at memoQ side
  • Onlyhavethe XHTMLnamespaceto be abletocorrectly back convert.No escaped HTML, butcorrectlytaggedusing XLIFF conventionsusing g fortagpairs and x forstandalonetags.Everytrans-unitisan input field in Sitecore. Weorginallyplannedondoingsentencebasedsegmentation in theexportfrom Sitecore butthisprovedtodifficulttomanage.Usedlinebreakstohelpsegmentation in memoQIssueshere: Sitecore has plaintextfields in which HTML can be inserted. &gt; Wehaveto catch this at memoQ&apos;ssideusingregextagger.
  • Wentlive in June 2012, almost a year ago.
  • One of thereasons, besidescost and WS API, isthis: cascadingfilters.Alsoability fine tune XLIFF filterAdd a regexfilterBig regex fan
  • One of thereasons, besidescost and WS API, isthis: cascadingfilters.Alsoability fine tune XLIFF filterAdd a regexfilterBig regex fan
  • Flexibility in memoQwithoutchanginganythingontheprogrammingside. Wejustreplacetranslators in thegroups.
  • QA Distiller
  • QA Distiller
  • A standards driven workflow for Sitecore localization

    1. 1. A standards driven workflowfor Sitecore localization
    2. 2. @FantpmasThomas VackierLocalization Engineer
    3. 3. Yamagata EuropeTranslating Knowledge@YamagataEurope
    4. 4. Our Customer
    5. 5. Used to have a home-grown web CMSthat exported content to Excel
    6. 6. They switched to Sitecore
    7. 7. Their site is big
    8. 8. So is their need for automation
    9. 9. We devised an FTP hand-off
    10. 10. Proprietary ZIP became TIPP
    11. 11. TIPP structureGUID.tippmanifest.xmlpobjects.zipbilingualtmtermattachmentLanguage, task, filesXLIFF
    12. 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. 13. We wanted clean XLIFF because there isalready too much bad XLIFF out there
    14. 14. We also wanted XLIFF to automatically updateTMs after revision in Sitecore<TaskType>TM-Update</TaskType>
    15. 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 helpsegmentation in memoQ
    16. 16. General workflowContent isaddedTIPP >FTPImported via APITIPP >FTPTIPP >FTPTranslate inclientTranslations areimportedReview is donein SitecoreImported via APITMupdate
    17. 17. memoQ workflowTIPPERPAnalysisCopy & extract 1 project per TIPP File assigned per market Resources assigned Pretranslation
    18. 18. Cascading filters rock
    19. 19. Cascading filters rock
    20. 20. Groups per market
    21. 21. Different translators per market
    22. 22. memoQ interface for post-processing
    23. 23. memoQ interface for post-processing
    24. 24. ConclusionsStandardization -> AutomationSeveral parties involvedBye bye file managementAutomatic TM updatesStill time-out issuesOnly one way to ERP

    ×