Get a better understanding of software localization and your place in this complex process. 

There is a natural synergy between the technical writer and the localization company. The process of writing documentation for a product and releasing it to the world can be improved when there is better planning and cooperation. When the process is controlled and optimized, significant savings can be realized and time can be saved in bringing the product to market with all related documentation ready. And more, future revisions can be made more cost-effective when those who write the documentation work effectively with those who translate it.

Some companies believe the best way to test a localization company is to ask for a sample translation. Although this may sound logical, it is, in fact, a bad idea for many reasons. The first major issue when asking for a sample is that the translator who handles the sample may not actually be the one who will be assigned the project when the time comes to begin the localization process.

By being familiar with the whole of the documentation cycle, from start to finish, the technical writer can increase efficiency, lower costs, and improve the final deliverables.

When people talk about translation they usually have in mind text written in one language interpreted to another language. This is probably the only point translators agree on.

Imagine that you are going to a restaurant that serves crab. You open the menu excitedly only to discover that the restaurant, instead of putting crabmeat on the menu, is offering "steamed red crap with ginger." Of course, you know what the restaurant owners meant to communicate, and you probably will pass the menu around the table so that you and your party can have a good laugh. However, for businesses of all sizes, understanding the nuances of localization and translation can make the difference between prospering and languishing in a global marketplace.