Three simple steps to localize
Using a different language often means you must consider another character set. Especially if English is your first language, you might think that you need only 128 characters. However, many languages use special characters:
The list is endless.
So how would you feel if you couldn't use characters from your own native alphabet? What if your name is Henry, and you couldn't write your name, because a Russian software developer would not support the letter H as his/her language does not use that letter? Would you write enry instead? Or would you directly uninstall the application?
Use Unicode string handling in your application, whenever possible. This allows you to support all languages and character sets. The Unicode Windows API can help you accomplish this.
If your development environment supports only ANSI character sets, you should ensure that you do not restrict your input to the first 128 characters. For Delphi, and classic VB there are third-party unicode components available. DotNet developers already have unicode.
Sisulizer itself is a unicode application. You exchange data with your translator without the hazzle of conversions. Sisulizer does the job for you. Period.
You can localize both, ANSI and Unicode applications using Sisulizer. No need to change the tool. Sisulizer does it all.