To write content that is consistent as well as easy to reuse and maintain, technical writers should abide by the DITA authoring rules. Some of them belong to the information model, others to the style guide.
We would appreciate […]
DITA localization can be deployed in several ways, depending on the resources: with a CCMS or a content repository, with a translation management system managed in-house or by the Language Service Provider (LSP), with an internal or an external team of translators, and […]
DITA is a framework for content re-use across multiple information channels. This framework relies on separating content and format, as well as semantic tagging.
Among the options a technical writer can use, many of them require consistency to ensure an optimal user experience:
There is a universal agreement that translated content must be reviewed for quality control, regulatory compliance, and User eXperience. In doing so, the content continuously improves over time, as the corrections are integrated into the translation memory.
There is also an agreement that the review […]
Just when we think the formatting dinosaurs are extinct, we continue to find legacy issues in DITA source content. Many of these issues are relatively easy to fix and make your content more global-ready.
Bold and Italic formatting falls into this category of […]
DITA is intended to maximize re-use and single sourcing, thus simplifying content maintenance and reducing localization costs. Two DITA features enable re-use:
This post explains how to generate localization-friendly keyrefs – we will talk about conditional content […]
According to our inquiries, over 95% of DITA adoption projects are driven by an ROI exclusively funded by savings in localization. It’s indeed harder to factor in enhanced user […]