Skip the typical software localization beginner's traps

Conclusion

Don't be shocked about the number of differences in our many global cultures. Most of the differences are easy to address in your application code. Other software companies have tackled these problems, so you don't need to reinvent the wheel.

Many fine tools are available. In particular, the Windows API provides all of the tools you need. Moreover, if you are already using .NET, you are a top priority with Microsoft, because Microsoft knows they must appeal to the global programmer and provide you with the right tools—at the beginning of your software development process, when it matters most.

When you write flexible code, localization is a snap. However, if you have hard-coded some of the items mentioned in this article, you have much work to do. Take the chance to implement this article's recommendations in the beginning of your project. Plan a bit more in advance. This will save you time and money.

Most developers who have hard-coded strings are afraid of converting their application to string resources. Yes, if you have a large application with many strings, this process can cost you a few extra days. However, you will save more time and money when you start the localization process. All your hard work will pay off, as you can process every language and every update easily and efficiently. Remember to ensure that your resource files are Unicode-aware, so that you are prepared for the future.

Software-Lokalisierungsfallen

• Übersicht
• Sprachen
• Zeichensätze
• Codepages
• Zahlen
• Währungen
• Datum
• Zeit
• Listentrennzeichen
• Abmessungen
• Papierformat
• Telefonnummer
• Sortierreihenfolge
• Steuer
• Staaten
• Andere Fallen
• Schlusswort