|
|
Understanding the lng files
Some content of the scp projects has to be translated in the supported languages. This is important for localized directory names, or text output of some basic scripts. This translation happens with the help of the so called lng files, which are automatically included into the translation process. These files must have the same names as the scp files, in which the translated string is needed, but its extensions are .lng. One example shows this simple behaviour: Module
gid_Module_Prg_Calc_Bin As you can see, this is the definition of a module block. In the user defined installation, there is a user interface for selecting the modules. This cotains a name and a description of each module. And of course these have to be localized. In the module definition you see the line: MOD_NAME_DESC ( MODULE_PRG_CALC_BIN ); MOD_NAME_DESC is a macro defined in macros.inc. There you find: #define MOD_NAME_DESC(id)
\ Therefore this can be resolved to the two macros: ALL_LANG(Name,STR_NAME_
MODULE_PRG_CALC_BIN )
[STR_NAME_MODULE_PRG_CALC_BIN] [STR_DESC_MODULE_PRG_CALC_BIN] The names and descriptions are translated in any supported language. Therefore the scp linker will create a module definition, which looks like: Module
gid_Module_Prg_Calc_Bin You see, that most of the module definition is translation stuff. Finally it is the scpzip that creates installation sets for special languages. Therefore the final result for an english installation set looks like: Module
gid_Module_Prg_Calc_Bin This module definition you can finally find in the setup script in the installation set next to the setup.
|


