single sourcing for a global audience
DESCRIPTION
Whether you are translating your documentation now or plan to in the future, writing your content with a global audience in mind can improve content quality and reduce costs. In this presentation, Product Evangelist Jose Sermeno will provide real-world examples of how companies are using the MadPak Suite to simplify the translation process and lower overall content development costs. Concepts covered will include an overall process description, workflow examples for each of the related tools, common problems to watch out for and best practices for translation management. The applications discussed in the session in Flare, MadCap Lingo, Capture, Mimic and Analyzer. Presented By: Jose SermenoTRANSCRIPT
Welcome to
Single-sourcing for a Global Audience
Presented by: Jose Sermeno
Current: Product Evangelist - MadCap Software *MadPak & MadTranslations (Started with Flare v6)
Previous: Project Lead – Zivtech (Drupal Implementation)
Other Info:
• 10+ yrs Software Application Manager – Windows/Mac/Web
• Open Source Hardware & Software Advocate (Arduino, OpenCV)
• Award Winner for San Diego Community Outreach with Robotics
• Proponent of the Maker Movement
ABOUT ME: JOSE SERMENO
TODAY’S AGENDA
• Best Practices Overview• What hurdles opportunities exist when
translating single sourced multi-channel content
• Why do I care? (not caring costs $$)• How does the MadPak Suite help – Tools
Overview• Questions
BEST PRACTICES:
MAXIMIZE REUSE
MULTI-CHANNELSINGLE SOURCE
USE SINGLE SOURCING ELEMENTS
• Topic Based Authoring• Global Project Linking• Publish to Multiple Channels with 1 Flare Project• Condition any element in/out of a deliverable• Snippets: pre-set chunks of content that you can use in your
project over and over• Variables• Style Sheet Mediums• Single Source / Translate Call-outs from Flat images• Single Source static/interactive Multimedia
FOLLOW OPEN STANDARDS
XML, HTML, CSS,XLIFF, TMX, TBX
FUTURE PROOF YOUR CONTENT
TRANSLATION OPPORTUNITIES
(NOT HURDLES)
USING CONDITIONAL TEXT AND SNIPPETS
CONSIDERATIONS
Example:
– “Model number {variable} is forbidden for use outside
of the United States.”
TEXT EXPANSION
Example:
“FAQ” results in expansion – “Preguntas frecuentes” in Spanish
• Compound nouns - German, Finnish and Dutch
• Responsive writing - design to allow for text re-flow
Avoid fixed-width headers, tabs, buttons and graphics.
• Spanish, French, Italian, Portuguese, Polish, Arabic and Hebrew, will
result in text expansion of +15 to +30%
• Dutch and German can expand +35% or more
• Chinese, Japanese and Korean will generally contract -10% to -55%
• Certain languages like Chinese can expand vertically
TEXT EXPANSION CONSIDERATIONS
Let’s take the phrase “TV marketing strategy”
English = 3 separate words
German = one compound noun: “Fernsehmarketingstrategie”
HERE IS A GERMAN EXAMPLE:
WHY DO I CARE?(NOT CARING COSTS $$)
GOAL:
KEEP DTP COSTS DOWNUNDERSTAND YOUR CONTENTSIMPLIFY QA REDUCE PROJECT TURNAROUNDCREATE A CLEAN TM
HOW DOES THE MADPAK SUITE HELP?
IN TOOLS DEMO
MadTranslations specializes in individual projects or complete end-to-end translation and localization solutions.
Our services include:
• Language Translation• Software Localization• Website Localization
• E-Learning Localization• Project Management• And more
`
@MadCapJose@MadCapSoftware@MadCapJennifer@MadCapMike@MadCapDocTeam
Questions? Thank You!
Jose SermenoProduct EvangelistMadCap Software