Technical writing is a process with tried and true steps and requirements. Then there’s a void. Then there’s localization. The void can lead to misalignment and inefficiencies: publishers using structured content methods find themselves losing the benefits of re-use, and watch their forecasted savings miss the target.
In this presentation, we help technical writers and information architects identify how their work can impact positively or negatively the localization downstream. We will look at:
How localization works: a few principles
The information model:
Attributes and elements
Call-outs in images
Conditional text and references
Writing styles, rules and process
Standard Technical English
Using real-world examples from the proof of concepts we have carried out with our customers, we will provide the audience with insight on how linguistic providers manage source content and how to avoid localization mishaps which can lead to corrupted projects, poor quality and inflated invoices.