Gettext/Sources
From Get docs
4 Preparing Program Sources
For the programmer, changes to the C source code fall into three
categories. First, you have to make the localization functions
known to all modules needing message translation. Second, you should
properly trigger the operation of GNU gettext when the program
initializes, usually from the main function. Last, you should
identify, adjust and mark all constant strings in your program
needing translation.
| • Importing: | Importing the gettext declaration
| |
| • Triggering: | Triggering gettext Operations
| |
| • Preparing Strings: | Preparing Translatable Strings | |
| • Mark Keywords: | How Marks Appear in Sources | |
| • Marking: | Marking Translatable Strings | |
| • c-format Flag: | Telling something about the following string | |
| • Special cases: | Special Cases of Translatable Strings | |
| • Bug Report Address: | Letting Users Report Translation Bugs | |
| • Names: | Marking Proper Names for Translation | |
| • Libraries: | Preparing Library Sources |
