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.
How do you know it’s time to move to XML? Consult our handy list of indicators.
Let’s wrap up 2015 with a look back at popular posts from the year.
Scriptorium wishes you the best for 2016!
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?
Technical Writing is only about what software you know! Is that why every where I read any type of document, web page, or article it is FULL of misspellings, incorrect punctuation, and horrible formatting?!!
That’s what started a thread on LinkedIn that encapsulates long-running debates on the skill sets technical writers need. (The thread was removed from LinkedIn sometime after Friday, unfortunately.)
When companies need to change the way they’re producing content, localization and scalability can be two of the biggest motivating factors. If your company’s content is not consistent, you may face significant challenges with translating it into new languages or distributing it via new platforms. A content strategy that embraces consistency and emphasizes planning for the future will help your company navigate these changes more smoothly.
Things have changed since we wrote this! Check out the latest post here with new insights from our team.
This premium post is a recap of a presentation delivered by Sarah O’Keefe at Localization World Berlin on June 4, 2015. It describes how and why to align localization strategy to the customer journey.
The new buzzword in marketing is the customer journey. What does this mean for localization?
“What CCMS should we buy?”
It’s a common question with no easy answer. This article provides a roadmap for CCMS evaluation and selection.
First, a few definitions. A CCMS (component content management system) is different from a CMS (content management system). You need a CCMS to manage chunks of information, such as reusable warnings, topics, or other small bits of information that are then assembled into larger documents. A CMS is for managing the results, like white papers, user manuals, and other documents.
Localization—the process of adapting content to a specific locale—is a critical requirement for global companies. It’s often treated as a necessary evil, but this is shortsighted. The quality of localization efforts affects the company’s bottom line.
More than ever, products and services are sought, purchased, and consumed in multiple language markets. Proper localization practices are critical to drive sales, and they can save you time and money in production.
This article describes best practices for efficient, effective localization.
Everyone wants to know how much an XML workflow is going to cost. For some reason, our prospective clients are rarely satisfied with the standard consultant answer of “It depends.”
This post outlines typical XML projects at four different budget levels: less than $50,000, $150K, $500K, and more than $500K.
The companies described are fictional composites. You should not make any major budgetary (or life) decisions based on these rough estimates. Your mileage may vary. Insert any other disclaimers I have forgotten.
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.