Options and limits of fully automated publication processes

When can you afford the time to think about rationalizing current processes?

"Every day" would be the perfect answer - but you know it's not always easy to find the time ...

Production strategies are queried when costs rise, capacities are no longer sufficient, production turnaround times are too long, or when quality control is imminent. The clock is already ticking away.

Production processes in the difficult field of technical documentation/translation focus on the document. Accordingly, conventional editing, translation and publication processes also involve correction and validating cycles: in an emergency, you can always intervene.

The shortcomings of DTP programs are circumvented, problems due to source text inadequacies after translation ironed out and imperfections in translation memory systems in a number of constellations accepted and compensated for through in-house solutions.

All this can sometimes lead to seemingly complex processes which are fundamentally related. Generally, the target language document is produced seamlessly. However, it is sometimes difficult to separate the costs of the actual work from those of additional modifications or repairs.

Automated processes

Switching from a standard DTP architecture to an automated publication process involves reorganizing and reallocating tasks. No longer are editing, revision and IT departments, translation services and the system house merely driving along the same road; they are sitting side by side in the same vehicle. From the outset, the translator is now responsible for evaluating the quality of the text. Issues which were previously clarified between translators and layout specialists at a later stage must now be sorted out at the beginning of the process in order to avoid problems.

Producing source texts

The editor's work has become far more complex than ever before. The most significant changes are required from the editor. Thinking along the lines of previous DTP conventions is restricting. Real formatting no longer exists, and the order and use of references, indexes, lists and abbreviations require more skill.

Changing processes

The situation regarding merged subsidiaries has changed just as fundamentally, even if everything looks the same at first sight. Language-specific adjustments and localizations should be recognized and managed in the CMS/DMS – if not, the entire automated mechanism will be counteracted in the long run and considerable costs incurred.

Managing editorial problems

Theoretically, fine-tuning during a solution's introductory phase may cause repeated editorial problems, particularly since the localization of content into new target languages sometimes produces constellations which were not, or only briefly, considered at the beginning. System house engineers usually structure the processes based on their native language. The time factor certainly plays a crucial role, and a solution is not easy to find or implement. Such scenarios should be outlined within the context of quality assurance right from the outset and coordinated thoroughly. Here, efficient information management and interaction among users, translation services and the system house are required.

Nothing flows without information

In addition, proven communication channels between editing, translation and locations must be reconsidered. In each case, there are different and new partners, as well as limited options to intervene in the processes (just to make it clear: "It was intended that way!"). Efforts to become independent of service providers often lead to a closer partnership because the technology used in the field of content and translation management is developing rapidly. The clock is ticking away steadily. A reliable alarm clock would be a good idea. A reliable partner would be the perfect solution.
 

Horst Liebscher (euroscript Deutschland GmbH)