{"id":9234,"date":"2022-07-15T08:06:00","date_gmt":"2022-07-15T08:06:00","guid":{"rendered":"https:\/\/www.oneword.de\/artikel\/translation-oriented-writing-din-8579\/"},"modified":"2026-07-20T06:53:44","modified_gmt":"2026-07-20T06:53:44","slug":"translation-oriented-writing-din-8579","status":"publish","type":"post","link":"https:\/\/www.oneword.de\/en\/artikel\/translation-oriented-writing-din-8579\/","title":{"rendered":"Reduce the risks of translation errors and additional costs through translation-oriented writing"},"content":{"rendered":"\n
\n
\n

At the beginning of July, the new DIN 8579 standard "Translation-oriented writing – Text production and text evaluation" was published. We take a look at the details and explain why authors of technical texts requiring translation cannot avoid this standard.<\/p>\n<\/div><\/div>\n<\/div>\n\n

\n
\n

Technical writers and other authors of technical texts already work with guidelines and standards for technical documentation, including, for example, the IEC\/IEEE 82079-1 documentation standard<\/a>, in-house company style guides and other aids, including software supported tools. However, although IEC\/IEEE 82079-1 formulates recommendations for the translation of instructions, and source text requirements implicitly apply to foreign-language instructions, instructions that conform to IEC\/IEEE 82079-1 are not automatically optimised for translation.<\/p>\n\n\n\n

Although there are already recognised rules and numerous \u2013 in some cases extensive \u2013 handouts about translation-oriented writing, these are too rarely taken into account in practice. This is where the new standard DIN 8579<\/a> for rule-compliant, translation-oriented writing comes in and provides help with many practical examples.<\/p>\n<\/div><\/div>\n<\/div>\n\n

\n
\n

A common standard from experts on both sides<\/h2>\n\n\n\n

A new working group was set up in 2019 to develop the standard. Representatives of the DIN working committees "Translation Services" and "Technical Documentation" came together to provide authors of technical texts relevant to translation with a practical guide for making source texts suitable for translation.<\/p>\n\n\n\n

Both working committees complemented each other perfectly in this working group. With DIN 8579, they have not published another editorial guide but rather a document that is the ideal complement to IEC\/IEEE 82079-1, for example. Each chapter and each point makes clear what explicitly may happen when translating, when using translation technology (CAT tools) or in the final translated text if the recommendations are not followed and provides the reasons. Numerous positive and negative examples provide a concrete idea of what may happen.<\/p>\n\n\n\n

Another positive aspect is that the standard is fundamentally aimed at all stakeholders involved in the translation process: writers, editors, translators, tool manufacturers and machine translation system operators.<\/p>\n<\/div><\/div>\n<\/div>\n\n

\n
\n

Practical benefits in the foreground<\/h2>\n\n\n\n

If text creators take into account that the specialist text they are creating is going to be used internationally and take the translation and translation technologies into consideration when they produce the text, there will be fewer translators' queries, translation errors can be avoided and translation costs and work can be reduced.<\/p>\n\n\n\n

Therefore, the new standard not only covers topics such as formatting, terminology, grammar, syntax and style or the presentation of content, but also far-reaching requirements for the type of assignment, i.e. the interface between text creation and translation (file formats, reference material, etc.) and likewise criteria and help for assessing the suitability of a text for translation or the work required for any pre-editing.<\/p>\n<\/div><\/div><\/div>\n<\/div>\n\n

\n
\n

Conclusion: DIN 8579 was overdue<\/h2>\n\n\n\n

Writing source texts in a way that is appropriate for translation and based on DIN 8579 can lead to fewer misunderstandings and errors in the translation and reduce additional work and necessary reformatting as well as queries. Since texts that are suitable for translation ideally contain no ambiguities, unclear references, inconsistent terminology and many other linguistic and formal pitfalls, they are ultimately also optimised for users who read the instructions in the original language. The standard is therefore multi-talented and a win-win for all languages of an instruction!<\/p>\n\n\n\n

Interested professional users may want to purchase the newly published standards handbook<\/a> "Normen f\u00fcr Terminologiearbeit, Technische Redaktion und \u00dcbersetzen" (Standards for Terminology Work, Technical Writing and Translation). The comprehensive collection contains almost 600 pages of a large number of standards \u2013 including DIN 8579, IEC\/IEEE 82079-1 and ISO 17100 \u2013 that are relevant for translations and other aspects of the translation process, but also for terminology work and technical editing. The manual will be published in September and is already available for pre-order.<\/p>\n\n\n\n

Get in touch with us now!<\/span><\/a><\/div>\n<\/div><\/div>\n<\/div>\n","protected":false},"excerpt":{"rendered":"","protected":false},"author":7,"featured_media":9235,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_nectar_blocks_hide_post_title":false,"_nectar_blocks_transparent_header_effect":false,"_nectar_blocks_transparent_header_effect_color":"light","_nectar_blocks_header_animation":false,"_nectar_blocks_header_animation_delay":0,"_nectar_blocks_header_animation_effect":"fade","_nectar_blocks_page_css":"","_nectar_blocks_page_js":"","inline_featured_image":false,"footnotes":""},"categories":[65],"tags":[],"class_list":["post-9234","post","type-post","status-publish","format-standard","has-post-thumbnail","category-quality"],"_links":{"self":[{"href":"https:\/\/www.oneword.de\/en\/wp-json\/wp\/v2\/posts\/9234","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.oneword.de\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.oneword.de\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.oneword.de\/en\/wp-json\/wp\/v2\/users\/7"}],"replies":[{"embeddable":true,"href":"https:\/\/www.oneword.de\/en\/wp-json\/wp\/v2\/comments?post=9234"}],"version-history":[{"count":4,"href":"https:\/\/www.oneword.de\/en\/wp-json\/wp\/v2\/posts\/9234\/revisions"}],"predecessor-version":[{"id":9510,"href":"https:\/\/www.oneword.de\/en\/wp-json\/wp\/v2\/posts\/9234\/revisions\/9510"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.oneword.de\/en\/wp-json\/wp\/v2\/media\/9235"}],"wp:attachment":[{"href":"https:\/\/www.oneword.de\/en\/wp-json\/wp\/v2\/media?parent=9234"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.oneword.de\/en\/wp-json\/wp\/v2\/categories?post=9234"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.oneword.de\/en\/wp-json\/wp\/v2\/tags?post=9234"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}