{"id":1614,"date":"2012-06-05T10:53:03","date_gmt":"2012-06-05T17:53:03","guid":{"rendered":"https:\/\/www.phoenixtechpubs.com\/blog\/?p=1614"},"modified":"2012-08-02T10:01:53","modified_gmt":"2012-08-02T17:01:53","slug":"10-steps-to-save-time-and-money-during-translation-2","status":"publish","type":"post","link":"https:\/\/www.phoenixtechpubs.com\/blog\/index.php\/2012\/06\/10-steps-to-save-time-and-money-during-translation-2\/","title":{"rendered":"10 Steps to Save Time and Money During Translation"},"content":{"rendered":"

\"\"<\/a>For companies doing business globally, the availability of properly translated documentation is critical for success. But translation can be expensive, time consuming, and cumbersome, and companies often limit translation or skip it altogether.<\/p>\n

With proper planning, translations costs can be significantly reduced. However this requires more than just extracting the best deal from your translation vendor. It requires proper planning at the time of content creation. Following the steps below can cut your translation cost by 50% or more without diluting the value of your content.\"\"<\/strong><\/p>\n

1. Use Fewer Screenshots <\/strong><\/p>\n

Screenshots are popular because they effectively communicate the user interface and workings of a product. However, if the software is localized, screenshots should be retaken for the localized software. This requires setting up the application with relevant data\u00a0 \u2013 once for every screenshot in every language. On the other hand, some companies do not localize the software and end up with documentation in the translated language but with the screenshots in English. With limited or no screenshots, both of these problems can be minimized.<\/p>\n

2. Keep Word Count as Low as Possible <\/strong><\/p>\n

Translation costs are calculated on the number of words so this one is fairly obvious. But this has to be planned early on \u2013 it is much easier to write succinct material than to reduce words at the time of translation. And fewer words also make material simpler to understand and easier to translate. Lower word count pays dividends for all documents, for all languages, and for all future revisions.<\/p>\n

3. Separate Graphics from Text <\/strong><\/p>\n

Graphics, if done right, can be a great communication tool. And, being a universal language, they do not have to be translated. However, if graphics include text they can become a nightmare. Any text embedded in the graphics must also be translated. Often this requires a complete recreation of the graphic. Avoid the use of text in graphics; label items with numbered callouts and identify graphic elements outside of the illustration.<\/p>\n

4. Do Not Include Slang and Local Jargon <\/strong><\/p>\n

Slang terms will probably not have the desired meaning or context in the target language – or may have highly undesirable meanings! – so must be translated. The translators may not understand the slang well enough to translate without research, adding even more to translation costs. Leave the slang out from the beginning to minimize costs.<\/p>\n

5. Allow for Text Expansion <\/strong><\/p>\n

Translating to other languages usually results in text expansion. Translation from English to German, for example, typically results in text expansion by around 25%. It is much easier to format the document later if there is plenty of room to expand.<\/p>\n

6. Develop a Glossary <\/strong><\/p>\n

Glossaries help translators understand your product and terms. The more the translators understand, the quicker they translate and the fewer mistakes they make.<\/p>\n

7. Use Repetitive Language <\/strong><\/p>\n

If the same content is repeated many times it has to be translated only once. So wherever possible write the same content in the same way, every time. Although this may appear uncreative it reduces the translation effort and cost. For example, if you write \u201cPush the button\u201d the first time, do not write \u201cPress the button\u201d the next time.<\/p>\n

8. Use XML <\/strong><\/p>\n

Use of XML in technical documentation has received much attention lately. See our blog “An Introduction to XML and DITA”<\/a> for more pros and cons of using XML. XML can lead to significant savings in translation of technical documents. One way that XML-based documentation saves money is the ease of reusing content which only needs to be translated once. Another way that XML saves money is that XML includes metadata \u2013 information about the content. For example, metadata can be added to newly updated content to indicate what needs to be translated and what does not – leading to significant savings.<\/p>\n

9. Use a Simple Language <\/strong><\/p>\n

Although this is a best practice to write any technical document, it is doubly important for the ones that have to be translated. For example, if the word \u201cconsider\u201d will suffice, avoid using \u201ctake into consideration\u201d.<\/p>\n

10. Avoid Screenshots <\/strong><\/p>\n

Yes we mentioned this one above. But this is so important that it is worth repeating.<\/p>\n

Andrea is a Senior Technical Writer at Phoenix Technical Publications. Phoenix Tech Pubs has provided complete technical writing and documentation services in the San Francisco Bay Area for over 25 years.<\/address>\n","protected":false},"excerpt":{"rendered":"

For companies doing business globally, the availability of properly translated documentation is critical for success. But translation can be expensive, time consuming, and cumbersome, and companies often limit translation or skip it altogether. With proper planning, translations costs can be significantly reduced. However this requires more than just extracting the best deal from your translation … Continue reading 10 Steps to Save Time and Money During Translation<\/span> →<\/span><\/a><\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[4,159],"tags":[156,154,155],"class_list":["post-1614","post","type-post","status-publish","format-standard","hentry","category-andreas-blogs","category-technical-writing-and-documentation","tag-dita","tag-translation","tag-xml"],"_links":{"self":[{"href":"https:\/\/www.phoenixtechpubs.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/1614","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.phoenixtechpubs.com\/blog\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.phoenixtechpubs.com\/blog\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.phoenixtechpubs.com\/blog\/index.php\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.phoenixtechpubs.com\/blog\/index.php\/wp-json\/wp\/v2\/comments?post=1614"}],"version-history":[{"count":22,"href":"https:\/\/www.phoenixtechpubs.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/1614\/revisions"}],"predecessor-version":[{"id":1883,"href":"https:\/\/www.phoenixtechpubs.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/1614\/revisions\/1883"}],"wp:attachment":[{"href":"https:\/\/www.phoenixtechpubs.com\/blog\/index.php\/wp-json\/wp\/v2\/media?parent=1614"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.phoenixtechpubs.com\/blog\/index.php\/wp-json\/wp\/v2\/categories?post=1614"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.phoenixtechpubs.com\/blog\/index.php\/wp-json\/wp\/v2\/tags?post=1614"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}