Three factors for evaluating localization vendors
Localizing content can be a frustrating and expensive effort. In addition to per-word costs and turnaround times, keep these three key factors in mind when choosing a vendor.
Localizing content can be a frustrating and expensive effort. In addition to per-word costs and turnaround times, keep these three key factors in mind when choosing a vendor.
In this webcast recording, Bill Swallow takes a look at intelligent content’s role in global markets, and how the entire content cycle directly affects a business’s bottom line (revenue).
Translating your content can be an expensive and time-consuming process. While there are many cost-saving practices you can employ, perhaps the easiest and most cost-effective practice involves how you manage your images.
Last month I posted about the five gotchas that will affect your translation turnaround time. That post focused on content quality, but I’d also mentioned how “a good LSP” would handle things. This month, let’s take a step back and look at five things that separate the nice LSPs from the naughty ones.
Having worked at two translation companies and on many projects requiring localization, I appreciate just how nimble LSPs (language service providers) can be. Their ability to track down translators with the necessary subject matter expertise and handle a vast array of file formats is truly remarkable. That said, localization efficiency is dependent on you, the content provider.
In this webcast recording Bill Swallow, the manager of the GlobalScript division at LinguaLinx, discusses some of the ways you can cut your localization costs while still delivering quality content.
Update 9/26/2014: Bill now works for Scriptorium.
Out of the box, the DITA Open Toolkit (OT) looks like it’s localization-ready. It handles the XML attribute xml:lang. It contains strings for more than 50 localizations. So it would seem that all you have to do is specify the language in your DITA files and maps and you’re good to go…or are you? In this webcast, I’ll discuss some of the issues Scriptorium has encountered while generating localized output from the DITA Open Toolkit—and how we solved them.
The DITA Open Toolkit comes with support for many languages, but you can always find one that is not yet covered. Fortunately, adding a new language does not require any strange incantations.
STC Intercom, April 2009
A common argument for XML-based workflows is that they automate production and localization tasks. With XML, localization can be reduced to a fraction of its original cost, but how exactly does that happen?
Sarah explores automization in localization and two technology standards used in multilingual workflows: The Extensible Stylesheet Language (XSL) and XML Localization Interchange File Format (XLIFF).
Download the PDF (125 K)
Over the years, I have worked on manuals that were translated, and I have helped clients with their localization processes. Despite those experiences, I’ve never been part of a project in which US English was localized (well, localised) into UK English–until now.
Cherryleaf has adapted material from our Technical Writing 101 book in its new Basics of Technical Authoring self-paced course. Cherryleaf is based in the UK, so the course is tailored for those accustomed to British English, but the content is helpful to any English speaker who wants to learn the basics of technical writing. Cherryleaf has also included exercises so students can get some experience applying the techniques explained in the course content.
(Full disclosure: Scriptorium is compensated for sales of Cherryleaf’s course.)