MYTH 1: Localization is simply translation
Many people do not realize the level of effort involved in localization, dismissing it as simply translation.
Advances in internet technologies, development tools, authoring tools and platforms have expanded the use of multiple file formats and build environments. Software applications and manuals are no longer based only on Microsoft resource files or Word documents. Java, XML, ASP, PHP, HTML, as well as many other formats have become standard in many applications and products.
Translators are now expected to understand all these different technologies and file formats, and accurately translate only what is needed, without modifying tags, links or code. If errors are made, a significant amount of debugging time is needed to fix and build the international products.
Localization is both an art and a science. Do not underestimate the efforts needed or short-cut the process. It takes experienced engineering and translation professionals to properly implement an efficient translation-reuse process and localize your product.
MYTH 2: Anyone who knows a second language can be a translator
Would you hire anyone who speaks English to be your Tech Pubs writer, or anyone who knows a computer language to be your programmer? Translators are professionals with years of schooling and translation experience. They earn their living doing translations. Most live in the countries that they are translating for and are natives of the language they translate into. They have an excellent command of the languages they translate from and into to ensure consistent, accurate and timely work. Recruiting amateurs to do translation work, even if they know your product or technology well, will lead to inferior results and product delays.
MYTH 3: Lower translation rates reduce overall costs
In localization, it is often the long-term costs that matter the most. Software, help, docs and other texts related to products are constantly changing. With each product release, the localized material needs to be updated and synchronized with the source. Lower upfront translation costs do not necessarily mean lower long-term costs. The following are key factors that contribute to long-term costs:
- Process: Is the latest and most efficient translation-reuse process being implemented? If Translation Memory (search-engine and database) tools are not used, updates will be very time consuming and costly.
- Maintenance costs: Vendors who have lower translation rates may have steep penalties built into fuzzy matches (similar but non-identical matches), repeats and 100% matches. This creates steep overhead costs each time a new revision of your product needs updating.
- Quality: Although low quality translation will have lower initial costs, the long-term costs are significant. Post-translation changes are very costly, particularly if you have incurred production costs for layout, desktop publishing, quality-assurance, duplication or printing.
- Ownership: Do you own your translation memories and databases? If you pay for the work, you should own it all.
To the untrained eye, a translated text appears final regardless of the quality or state it is in. The value in having your source files edited by a proofreader or your software code reviewed by a second developer is the same value you should seek in having translated text checked by a second translator. In the case of translation, the editing cycle will require not only reading through the translated text, but also verifying it against the source. Many vendors with lower rates or higher overhead, will cut corners on editing in an effort to turn a profit. They may not ask a second translator to edit the text and instead perform “cursory checks”, which only require the editor to quickly read through the translated text without ensuring it accurately represents the source. Always ask your translators or translation vendors what levels of review they offer to ensure quality.
Myth 5: The vendor that provides the best translation sample offers the best quality
Asking localization vendors to provide a translation sample is often mistakenly accepted as a lead method to measure vendors’ quality standards. Although in theory the concept makes sense, in reality, it is far from optimal. First, there are a lot more tasks involved in localization than simply translation. Second, translation samples are often done by the most qualified translators who may or may not participate in the actual translation after the project is awarded.
If a sample is requested, you need to make sure that:
- The vendor knows how to manage, parse, prepare, reuse, compile, desktop-publish and QA the required files.
- The translator translating the sample will be the lead translator on the project.