Localization: 2 How To Use Localization

Your localization workload will vary depending on whether you plan to release your software in other countries. If you don't plan on exporting your software, your only contact with localization will come when you use the common functions that are localized. If you plan on international distribution, you'll be using localization both when writing your geodes and later on, during the translation process, in the following steps:

Use provided routines.
Several GEOS functions have been localized to handle foreign variations, and you should use these whether you plan international release or not. Most of these functions are concerned with "International formats" and character sets.
Plan ahead for ResEdit .
You'll probably use the ResEdit tool if you translate your software into other languages. You'll have to be careful about how you write your programs if ResEdit is to work with them properly. Any text in your geode that the user may see will have to be translated. ResEdit looks only at chunk is in localizable resources. You should also be prepared for the translations of any string to be longer than the original. You may want to provide instructions for translators. You may include these instructions within the body of your source code, close to the strings that will be translated.
Use ResEdit .
The ResEdit tool makes translation easy. It goes through an application's resources and checks all objects for strings and bitmaps, asking the translator to make any fitting changes. The translator never needs to see the source code and doesn't have to know how to program.

GEOS SDK TechDocs |

1 Localization Goals | Next:

3 Preparing for ResEdit