Making localization “better”
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?”
Glue strategy: connecting web CMS to CCMS
Web sites are fantastic at content delivery and generally terrible for content authoring. If you’re old enough (like me), you may have experienced the pain of hand-coding HTML or even editing HTML files live on your web server.
Pokémon GO and community documentation
Yes, I’m playing.
Even if you aren’t twitchily checking your phone and resisting the urge to run outside to catch a Pikachu or Gyrados, you’ve probably heard all about the phenomenon of Pokémon GO. One of the most common criticisms of the game is that the in-app documentation is sparse at best. In response, the community banded together and began to document their theories and findings. You can readily find articles covering “eeveelutions,” theories on how to more easily capture Pokémon, and how to capture opposing gyms. It hearkens back to a time of meeting up in schoolyards to swap tips and rumors.
Business case/ROI
Content management
Content reuse
DITA
DITA XML—authors
Localization
Structured content
Translation
Reduce translation costs with XML
$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.
The Rocky Road to Dublin, er, DITA
For LavaCon Dublin, Sarah O’Keefe and I delivered a case study presentation on some of the roadblocks we have encountered in implementing DITA at ADP. This article summarizes the key points of the presentation. The presentation and this blog do not represent the views of ADP, LLC.
When strategy meets the storm
Perfect weather for flying! (image via Flickr: estudiante)
Just before the blizzard that crippled a significant portion of the East Coast, I was returning from a business trip. I did eventually make it home, but the return flight included a bonus three-day layover in Charlotte, NC.
I’ll spare you many of the details, but a few key events and situations really stand out from that trip. The lessons learned are applicable to any corporate strategy, content or not.
Top eight signs it’s time to move to XML
How do you know it’s time to move to XML? Consult our handy list of indicators.
The best of 2015
Let’s wrap up 2015 with a look back at popular posts from the year.
Scriptorium wishes you the best for 2016!
The commodity trap
In a recent post on lean content strategy, I wrote about a focus on waste reduction:
After creating a nice automated XML-based process, waste in formatting is eliminated, and we declare victory and go home. Unfortunately, the organization is now producing irrelevant content faster, and the content organization is now positioned as only a cost center.
Is your content perceived as a commodity?
