Your SlideShare is downloading. ×
0
Managing multilingual webcontent
Managing multilingual webcontent
Managing multilingual webcontent
Managing multilingual webcontent
Managing multilingual webcontent
Managing multilingual webcontent
Managing multilingual webcontent
Managing multilingual webcontent
Managing multilingual webcontent
Managing multilingual webcontent
Managing multilingual webcontent
Managing multilingual webcontent
Managing multilingual webcontent
Managing multilingual webcontent
Managing multilingual webcontent
Managing multilingual webcontent
Managing multilingual webcontent
Managing multilingual webcontent
Managing multilingual webcontent
Managing multilingual webcontent
Managing multilingual webcontent
Managing multilingual webcontent
Managing multilingual webcontent
Managing multilingual webcontent
Managing multilingual webcontent
Managing multilingual webcontent
Managing multilingual webcontent
Managing multilingual webcontent
Managing multilingual webcontent
Managing multilingual webcontent
Managing multilingual webcontent
Managing multilingual webcontent
Managing multilingual webcontent
Managing multilingual webcontent
Managing multilingual webcontent
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Managing multilingual webcontent

848

Published on

Presentation from our seminar "MULTILINGUAL CONTENT MANAGEMENT" in Ghent on March 30th together with dotProjects and CrossLang.

Presentation from our seminar "MULTILINGUAL CONTENT MANAGEMENT" in Ghent on March 30th together with dotProjects and CrossLang.

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

  • Be the first to like this

No Downloads
Views
Total Views
848
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
16
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide
  • Verwijzen naar introductie Frederik: waarom zouden mensen hun web content aanbieden in verschillende talen? Die beslissing heeft zeer grote consequenties: niet alleen vergt dit initieel een investering, maar ook heel wat inspanning achteraf om de verschillende versies synchroon te houden, zeker bij web content die meestal dynamisch is.Adhv concrete case study gaan we de mogelijkheden overlopen.
  • Telenet kocht
  • Vertalen is niet zo simpel als het eruit ziet. Het is meer dan het documentje dat vertaald moet worden naar een vertaler sturen. Hier is bv geen rekening gehouden met kwaliteitscontrole, beschikbaarheid van de resources, het hele administratieve proces met bestelbonnen en facturen, desktop publishing aangezien de vertaalde teksten uiteindelijk ook door iemand gelezen zullen moeten worden, testing of bijvoorbeeld links nog werken, het aanpassen van eventuele screenshots in de verschillende talen enzovoort.
  • Eenvertaalproces in de realiteitzietereerderzouit, met verschillendefuncties die door verschillendemensenuitgevoerdworden: terminologiebeheer, kwaliteitsbewaking, DTP, project management etc.
  • Het seminarie van vandaag gaat nu specifiek over web content maar de aanpak kan zeker ook geëxptrapoleerd worden naar bv e-learning die gevoed wordt door een knowledge base.Web content is typisch dynamisch waardoor het vaak en snel wijzigt – de lifetime van een online boodschap is doorgaans van korte duur. Dat maakt de uitdaging des te groter: de aanpassingen moeten ook in de verschillende taalversies doorgevoerd worden. Het probleem groeit exponentiël naar gelang het aantal talen.
  • Zoals in alle sectoren is procesoptimalisatie noodzakelijk door middel van het automatiseren van de individuele stappen in het proces.Automation: automating administrative tasks/generating MT output/extracting terminology/aligning legacy data etcIntegration: Open standards/integrateseveral disciplines in order to beable to offer a complete solution to the customerLanguageinfrastructure: avoidthatyourcustomercan run awayafterone project by holding the keys to hislinguisticassets/offer more thanmeretranslation services, butcreate and maintainyourcustomersterminology, host its MT engines, allowthem to track projects in your PM system
  • Intransparante multi-sourcing:Belangrijke nadelen voor het vertaalprocesInconsistentie van de output: verschillen in stijl, terminologieMinder hergebruik van vertalingUiteindelijk betaal je als klant meer voor minder goede kwaliteit
  • The main optimization factors are:1. Direct communication between content owners and linguistic resources2. Linguistic resources are named user: traceability and transparency3. Active cooperation and learning curve: making quality expectations explicite4. Centralized and consistent approach for all vendors5. Beschikbaarheid van vertalers = moeilijk issue
  • Transcript

    • 1. Quick and inexpensive publication ofmultilingual web content viamachine translation, workflow systems and CMS<br />
    • 2. Telenet case study<br />
    • 3. Multilingual website (nl)<br />
    • 4. Multilingual website (fr)<br />
    • 5. Multilingual website (en)<br />
    • 6. What does it take to translate?<br />Translator<br />Content owner<br />Content owner<br />
    • 7. What does it take to translate?<br />2. Pre-process source files<br />3. Convert files to translation format<br />4. Assign translation memories and glossaries<br />5. Analyse DTP work - page count + art + screen shots<br />6. Count words + TM analysis<br />11. Create file structure<br />1. Request translation<br />7. Order confirmation<br />35. Validate<br />Translation projects upon receipt<br />38. Deliver final files<br />39. Archive<br />40. Invoice<br />Client<br />Engineering<br />7. Calculate cost<br />8. Confirm order<br />9. Project scheduling<br />10. Instructions for translators<br />12. Allocate translators<br />13. Allocate reviewers<br />Project<br />management<br />28. Desktop publishing<br />29. DTP QA<br />30. Implement corrections<br />in DTP format<br />32. Publish<br />Project<br />management<br />DTP<br />Translation<br />Functions <br />Tasks<br />14. Extract new terms<br />15. Translate new terms<br />36. Update glossary<br />Terminology<br />Engineering<br />26. Convert files <br />to native format<br />33. Compile<br />34. Functional testing<br />37. Update TM<br />Validation<br />16. Validate new terms<br />24. Validation by subject matter <br />expert<br />Language<br />specialists<br />Project<br />management<br />Translation<br />17. Prepare translation package<br />18. Project communications<br />19. Status reporting<br />20. Financial tracking <br />and reporting<br />22. Review<br />23. QA check<br />25. Receive and implement review comments<br />31. Implement text corrections in TM<br />21. Translate<br />27. Localise artwork/<br />illustrations/screenshots<br />
    • 8. Translating web content<br />Voluminous <br />Momentary<br />User-generated <br />
    • 9. Process optimization<br />Increase productivity in order to reach quick turn-around time<br />Reduce fragmentation and overhead in order to obtain flexibility, transparency and scalability <br /> Automation & Integration<br />
    • 10. Translation technology today<br />
    • 11. Automating the translation process<br />Step 1<br />
    • 12. Translation process (old)<br />
    • 13. Corporate departments<br />Linguistic resources<br />SD Worx resources<br />Customer portal<br />Request<br />Translate<br />Workflow engine<br />Track<br />Revise<br />Collaboration platform<br />Translator workbench<br />Review<br />Editterms<br />Translation process (optimized)<br />
    • 14. Online collaboration platform<br />
    • 15. Project monitoring<br />
    • 16. Automating the translation production process<br />Step 2<br />
    • 17. Translation production (optimized)<br />TMS<br />Corporate departments<br />Linguistic resources<br />SD Worx resources<br />Linguistic assets<br />Request<br />TM<br />TD<br />Post-edit<br />Track<br />Revise<br />Connectors<br />Review<br />Editterms<br />MT<br />
    • 18. Translation reuse<br />
    • 19. Translation production environment<br />Translation Memory + Machine Translation<br />Translation Memory alone<br />
    • 20. Productivity<br />
    • 21. Objectified evaluation (1)<br />
    • 22. Objectified evaluation (2)<br />
    • 23. Learning curve effect<br />
    • 24. The art of post-editing<br />
    • 25. Upload to website and test<br />Task Assignments<br />Return files to web manager<br />Review files<br />Web master<br />Project manager<br />Reassemble files and send to reviewers<br />Translator<br />Reviewer<br />Translate text<br />Distribute appropriate localization kits to appropriate translators<br />Split text & prepare kits for translators<br />Negotiate vendor pricing<br />Export database to XML<br />Prepare project<br />Project turnaround time – Weeks<br />Without TMT<br />With TMT<br />Translation of Knowledge Base<br />
    • 26. <ul><li>1 million source words translated and published in 6 weeks involving 5 post-editors at half of the initially forecasted budget</li></ul>Project turnaround time – Weeks<br />Without TMT<br />With TMT<br />Translation of Knowledge Base<br />
    • 27. Automating change detection<br />Step 3<br />
    • 28. Integrating authoring and publication environment<br />The easy part: initial translation of the Knowledge Base<br />The challenging part: keeping the different language versions up to date<br />
    • 29. Translation automation<br />Corporate departments<br />TMS<br />Linguistic assets<br />TM<br />TD<br />Translate<br />Author<br />CMS<br />Edit<br />Change detection<br />Revise<br />Workflow engine<br />NL<br />EN<br />FR<br />Collaboration platform<br />Translator workbench<br />Manage<br />Editterms<br />Trigger for content to be sent into translation workflow:<br /><ul><li> Periodical (interval)
    • 30. Manual project launch
    • 31. Priority handling</li></li></ul><li>Automating quality control<br />Step 4<br />
    • 32. Quality<br />MT gets better: R&D + customisation<br />Linguistic resources gain experience<br />Direct communication between content owners and linguistic resources<br />Terminology database grows<br />Less overhead = less risk of making mistakes<br />
    • 33. Terminology database access<br />
    • 34. Getting started<br />
    • 35. TMS SaaS<br />Cost effectiveness <br />No upfront investment or commitment in software licenses<br />Reduced translation cost through maximized translation re-use<br />Reduced fragmentation and overhead<br />Efficiency <br />All stakeholders (internal or external) use same tool sets<br />Automated repetitive project steps<br />Speed up content delivery<br />Improved translation quality through global brand consistency<br />Transparency and flexibility <br />Control and ownership of linguistic resources<br />Internal and/or external sourcing<br />Tracking and reporting capabilities<br />Seamless adoption and little change management<br />Scalability <br />Phased approach<br />Expandable<br />Connectors for machine translation and third party software integration<br />
    • 36. Thank you!<br />Nathalie De Sutter<br />Nathalie.de.Sutter@crosslang.com<br />+32 486 515113<br />

    ×