« Back to all posts

Localizing Web Content (Choose Your Own Adventure)

Localizing Web Content: Choose Your Own Adventure

It’s tough enough to localize one project once, but what happens when you have to continually localize or translate new content?  Our previous examples, multimedia and demo data, were one-time examples: these types of content are often produced more slowly and less frequently. But the rules change a little when you need to localize content that’s always changing. So for our last choose-your-own-adventure, we’re focusing on the best practices for localizing recurring types of content, like blog posts and social media updates.

Situation 1: Keeping on top of content

A well-known cloud services company, Stratys, wants to make their customer-help website available to users in Europe and the Middle East. Since their users can write in questions and receive replies from Stratys experts, the website’s content is always being updated. Stratys chooses a localization partner and starts the process of localizing the website. What should they block off on their calendar?

A) A short weekly check-in with their localization partner

B) A couple meetings early in the project arranging and prepping their internal review teams, plus a short weekly check-in with their localization partner

C) Reminders to send the localized content to their in-country review teams

Choice A

Stratys was smart to set up regular meetings with their localization partner—that way, they are able to solve problems as they occur and strategize content as it comes in. Since their website is continually, but not regularly, updated by users, the length of the meeting varies each week. Staying in touch regularly, however, helps Stratys keep on top of their content. However, the regular meetings in the US are turning into a backlog for Stratys’s in-country review teams, who took some time to get started. That’s why Choice B is the best practice.

Choice B

When Stratys stays in regular contact with their localization team and pre-arranges their internal review teams, they’re following the best practices to allow their recurring content to be localized smoothly and consistently. Regular check-ins with a localization partner allow Stratys to make any necessary changes or deliver new content in a timely way. Having the in-country reviewers lined up in advance means that any new content can transfer from Stratys’s localization partner to internal reviewers in a minimal amount of time.

Choice C

If Stratys waits to contact their in-country reviewers until a large batch of their content is localized, they run the risk that their reviewers are bogged down with other responsibilities and delay approval of the content. We’ve collected more best practices on making in-country review a smooth process here.

Situation 2: Automating to reduce time and cost

Rolodeks, a note-taking software startup, is preparing to localize its website and blog for Chinese and Japanese customers. Their blog updates biweekly with articles on industry topics, and each post ends with template language about contact information. Rolodeks thinks part of this localization process could be automated, and they want to find a translation partner who uses automation technology in their work. Should Rolodeks select a translation partner who uses:

A) Translation memory and databases with pre-set filters for content that doesn’t need to be translated

B) A translation management system

C) All of the above

Choice A

A translation partner that keeps translation memory and terminology databases is also a good choice for Rolodeks, since a lot of their blog content is industry-specific. Each newly translated blog post adds to the database and is stored in memory for future reference. Often, translation memory is paired with machine translation, so Rolodeks’s translation partner can automate more and more of the initial translation. This leads to faster translation turnaround and over time, more accurate automated translation.

Choice B

By choosing a translation partner who uses a translation management system (TMS), Rolodeks gets all the benefits of choices A, plus streamlined and automated ways to contact their translation partner and approve changes. Using a TMS means that Rolodeks can put the time they used to spend transferring content manually toward creating new content.

Choice C

In this scenario, both choices are best practices for localizing recurring content. Ideally, you want a translation partner who can leverage all of these technologies to automate as much of the workflow as possible, thus saving you time and money.

To learn more about the translation technologies that we use at Venga, see our new Localizing Engineering eBook or read more to see how we’re using automated technology to create better, faster translations. If you’re interested in what partnering with Venga can do for the adventure of localizing your recurring content, contact us or request a quote.

If you missed them, check out Localizing Multimedia (Choose Your Own Adventure) and Localizing Sales Demos (Choose Your Own Adventure).

Create an out of this world website