InfoMail, Q1-2007
GlobalVision International, Inc.


10 Tips on reducing localization
update costs

1. Use the correct localization process to allow easy leverage and reuse of the previously translated and localized files. For instance, if you are localizing a software application, the ability to localize binary files or leverage dialog box coordinates may be essential to you. When localizing manuals, the ability to support native file formats is also critical. When localizing websites, the ability to handle databases and dynamic htm is essential. Adopt the best localization process from the start, then enhance it as time goes on.
    

2. Build a complete and accurate translation memory (TM) for each language pair, starting from the very first localization task. Your localization assets need to be reusable. Looking for previously translated files, paragraphs, or strings outside of a robust search engine/database environment (provided with a translation memory tool) is error-prone and costly.
   
   It is never too late to build the translation database, even if translation memory tools were not used in the initial localization. Do it as soon as you can.
    

3. Spend the needed time to update your translation databases consistently and accurately with each product update. When changes to the target files take place after the translation database is created, make sure they find their way back to the corresponding translation memories. Doing this will accurately maintain them for the next release, eliminating the need to re-apply the same changes after the next leverage from the TM.
    

4. Implement a comprehensive translation memory strategy that is consistently adopted by all involved in your localization tasks, up front and for all languages. It may take some work to establish the strategy, and more work to maintain and audit it for consistency. But the effort will pay off in the efficiency gained: You’ll be able to confidently reuse the translation data with each product update.
    

5. Delegate the management of your translation memories to one vendor or expert to help maintain efficiency and accuracy. That vendor or person will establish an audit mechanism to check the work of all translators, editors, proofreaders, and localizers, and ensure that the proper process is followed.
    

6. Archive and save the intermediate bilingual files to reuse in the future. With these files, you can then use Context TM (XTranslate) to reduce future review costs.
   
   Leveraging translations one sentence at a time requires translators' intervention and manual checking. With the ability to automatically leverage translations one paragraph at a time, you’ll reduce costs during an update.
    

7. When performing updates on your source files, keep changes down to essentials. For instance, minimize stylistic enhancements and unnecessary edits, as they reduce the frequency of leveraging previous translations. Also, keep terminology changes in check.
   
   Changes in terminology will require a full review of everything associated with the product – the software, help, documentation, marketing collateral, website, and so on – in order to maintain consistency throughout.
   
   So, be cautious of overzealous writers and reviewers. When you change the author or editor of your documents, make sure that they are aware of all localization cost ramifications of changes to the source text.
    

8. Retain the file structure and file naming between releases to enable the use of Context TM (XTranslate) and diff3 tools. By comparing old source to new, these tools can help identify where minor or no changes exist, and apply any changes directly to the previously translated files. You can then use a hybrid top-down/bottom-up localization process to reduce costs. (Refer to InfoMail Q2-2004, Localization Processes, for more on the hybrid top-down/bottom up approach.)
    

9. Identify all files that remain intact from the previous release. These can be reused as-is, eliminating the leveraging, updating, desktop publishing, and QA work associated with each release. When you can reuse previously localized images, files, or documents, you reduce the overall update costs.
    

10. Keep source file formats unchanged for as long as feasible. For instance, if you currently use FrameMaker as your desktop publishing tool, do not switch to another unless the localization cost ramifications are financially justified.
     
    Changing help systems can also increase your updating costs. As you move from WinHelp to HTML help to XML help, markup or formatting tags in your help files will change. This creates fuzzy matches between the new source and the old, even if the text to translate has not changed.
    
    Translation memories maintain the internal tags specific to that tool. Switching to another will induce a fuzzy match due to the change in the internal tags format. A translator must check and correct these changes, adding to the costs. So, if you need to change your source files' formats, do it during major updates to the product and only when needed.