Being a native English speaker and first-time visitor to the incredible country of Japan, I found several takeaways for creating content with translation in mind.
Plus, in this blog, you’ll find delicious pictures of world-class food. (Caution: may cause salivation and a desperate urge to buy a plane ticket. Or is that just me?)
Translation troubles? This podcast is for you! In episode 173 of The Content Strategy Experts podcast, Bill Swallow and special guest Mike McDermott, Director of Language Services at MadTranslations, share strategies for overcoming common content localization challenges and unlocking new market opportunities.
Mike McDermott: It gets very cumbersome to continually do these manual steps to get to a translation update. Once the authoring is done, ideally you just send it right through translation and the process starts.
Bill Swallow: So from an agile point of view, I am assuming that you’re talking about not necessarily translating an entire publication from page one to page 300, but you’re saying as soon as a particular chunk of content is done and “blessed,” let’s say, by reviewers in the native language, then it can immediately go off to translation even if other portions are still in progress.
Mike McDermott: Exactly. That’s what working in this semantic content and these types of environments will do for a content creator. You don’t need to wait for the final piece of content to be finalized to get things into translation.
When organizations replatform from one content management system to another, unchecked technical debt can weigh down the new system. In contrast, strategic replatforming can be a tool for reducing technical debt. In episode 172 of The Content Strategy Experts podcast, Sarah O’Keefe and Bill Swallow share how to set your replatforming project up for success.
Here’s the real question I think you have to ask before replatforming—is the platform actually the problem? Is it legitimately broken? As Bill said, has it evolved away from the business requirements to a point where it no longer meet your needs? Or there are some other questions to ask, such as, what are your processes around that platform? Do you have weird, annoying, and inefficient processes?
— Sarah O’Keefe
Technical debt is “the implied cost of future reworking required when choosing an easy but limited solution instead of a better approach that could take more time,” Wikipedia, “Technical debt.”. Like financial debt, technical debt isn’t always a bad thing. You can use a loan to buy a house right away (at least in the U.S.) and then pay off the debt over time while living in the house. Technical debt allows you to create something quickly instead of doing it exactly right and taking much longer.
Too much technical debt, though, will hamstring your work. The trick is to find the Goldilocks solution.
In episode 170 of The Content Strategy Experts podcast, Bill Swallow and Christine Cuellar dive into the world of content localization strategy. Learn about the obstacles organizations face from initial planning to implementation, when and how organizations should consider localization, localization trends, and more.
Localization is generally a key business driver. Are you positioning your products, services, what have you for one market, one language, and that’s all? Are you looking at diversifying that? Are you looking to expand into foreign markets? Are you looking to hit multilingual people in the same market? All of those factors. Ideally as a company, you’re looking at this from the beginning as part of your business strategy.
— Bill Swallow
You need to translate content into new languages, but it’s not happening fast enough. Projects are delayed, programs can’t launch, and you’re at a loss for how to fix it.
A wise woman recently said, “replatforming structured content is annoying and expensive.” This is doubly so when it comes to localization.
Replatforming nearly always involves content change—the new system may store content differently or require a different format or structure. Although the changes may affect your existing localization process, some of these changes may be for the better.
Employees are (and should be) hired for their knowledge and skill, not necessarily their multilingual skills. In a global organization with many offices worldwide, the result is a diverse team with content developers and contributors that speak many different languages. Collaborating on content development—especially on the same document—can be difficult if employees do not speak the same language fluently (or at all).
A misfire by a German grocery chain entering the US market reminds me of a very important content strategy commandment: Know thy audience.
Bill Swallow discusses the possibilities and the limitations of machine translation tools such as Google Translate.
When is Google Translate good enough and when do you need professional (human) translation?
Machine translation continues to evolve. With artificial intelligence in the mix, machine translations seem almost human. Google Translate is one of the top players in this market, supplying everything from basic text translation to browser-embedded (Chrome) translation to a robust translation API. But even with all of these options, is Google Translate good enough?
There are special considerations when localizing DITA content. In this podcast, Bill Swallow and Simon Bate discuss the conventions available in DITA for localization, and share anecdotes and advice to help you circumvent localization problems.
Do you need to supply translated content? Use this hierarchy of localization needs to shape your localization strategy.
Without centralized localization processes, you will pay more for translated content, provide inconsistent translations, and possibly expose your company to significant legal liability. Here are warning signs your company needs a better localization strategy:
This post is part of a series on the value proposition of localization strategies.
A successful strategy requires more than having the right tools and processes in place. They need to be measured and governed.
This post is part of a series on the value proposition of localization strategies.
When people think of internationalization (IF they think of it), software labels often come to mind—buttons, menus, and other user interface text. But content development can benefit from it as well.
My 2017 trend is the impact of machine translation on content strategy.
This post is part of a series on the value proposition of localization strategies.
Accuracy and accelerated time to market are key success factors in every localization project. Proper terminology management contributes to both of these factors.
This post is part of a series on the value proposition of localization strategies.
The source content you develop is your intellectual property. The translation of that source content is also your intellectual property, regardless of who performs the translation.
This post is part of a series on the value proposition of localization strategies.
You can make localization “better” by taking a look at localization value. Quality and cost are important value factors, but improved time to market returns the greatest value.
Improving time to market for localized products and content is no easy task. It’s not as simple as adding more translators to the effort; that may cause more problems (and more delays). Improving time to market involves moving localization up the project chain, and to do so effectively requires a localization strategy.
This post is the first in a series about the value proposition of localization strategies. You can also see a presentation on this topic at LavaCon this October.
Localization issues are a primary reason companies seek help with a new content strategy. One of the most common questions we hear is, “How do we make our localization process better?”
When we’re asked this question, we turn the question around. What is wrong with your current localization process? What would you like to improve? How do you define “better?”
$0.21 per word.
That’s the average cost in the US to translate content into another language according to Slator, a translation news and analytics site. That number is not speculative; they analyzed the costs per word from over 80 actual proposals gathered by the US General Services Administration (GSA). You can view the source proposals here.
It takes considerable planning and effort to run a successful localization project, from following best practices to evaluating vendors to finding and fixing the weakest link in the localization chain. But the localization process does not end when you receive the translations. Localization testing is necessary for ensuring that your content and products are ready for a distributed global release.
Translating content for foreign markets can be an expensive and time-consuming endeavor. While it’s important to keep costs in check, the critical element to watch is quality. The only sure-fire way to ensure quality in translation is to build it into your source.
