In the classical documentation scenario, where translation is performed after the original is finished, quality improvements during localization can no longer influence the original because the original has been released to market. The experience and work of localizers and localization editors is not leveraged to its full potential. To unlock this potential, localization must be performed prior to the release of the original. This is the norm for software localization, yet it is not as common for document translations. Using the tools that Biblioso provides, you can maximize your return on investment in localization resources by performing the translation of documentation before the original is finished and released, so localizer feedback can be incorporated into the original as well as in localized versions.
When analyzing documentation changes in regards to their impact on localization, there are two main types:
- Editorial Changes These are changes that impact the logical structure or meaning of sentences, paragraphs, or entire sections, such as correcting a statement within a sentence or rearranging paragraphs. Changes to information occur typically during language and technical editing phases. These changes affect localized versions because the changed meaning must be conveyed in the localized versions as well. Therefore, localization must occur after editing.
- Proofing Changes These are changes that relate primarily to the grammar and linguistic style of the document, such as awkward sentence constructions, typos, missing commas, etc. Language fixes typically occur during the proofreading phase. These changes do not affect localized versions because the underlying information has not changed. Therefore, localization can occur before proofreading.
In a professional documentation project, documents
do not change significantly after the editing processes are completed.
Because the content is mostly permanent after editing, documents can
be localized prior to indexing and production if documentation and localization
is combined. Localized versions are released to market sooner and localizers
can have an opportunity for feedback. In this way, combined projects
result in improved original documentation, concurrently available localized
versions, and higher customer satisfaction in both the national and
international markets. Documentation and content can be released to
multiple markets in multiple languages without the burden and costs
of added localization cycles.
| Biblioso uses both change management and project management when working with combined projects to ensure incorporation of last-minute changes. |
|---|





















