I first want to say that if your upper management is not behind you in forcing developers to code for internationalization and localization, how can they expect the documentation to be held accountable. There are several advantages of using Common English, however, if you do a good job of creating a style guide that educates your wirters on how to write with Internationalization in mind, you will see that the translations will go smoother. In addition, getting your technical editor to create a very detailed glossary of all the technical terms that can be used, the translators will handle them consistently. You will never be able to produce the translated copy in an acceptable time frame if you are constently getting sections retranslated.
Effective coordination is critical to the success of the translation and keeping the cost down.
The translation of the documentation 9 times out of 10 will be the most expensive portion of the entire translation effort, so keeping the cost down is important. There are several advantages of using Common English, however, if you do a good job of creating a style guide that educates your wirters on how to write with Internationalization in mind, you will see that the translations will go smoother. In addition, getting your technical editor to create a very detailed glossary of all the technical terms that can be used, the translators will handle them consistently. You will never be able to produce the translated copy in an acceptable time frame if you are constently getting sections retranslated. Effective coordination is critical to the success of the translation and keeping the cost down.