Linlocalize can use
In a standard generated resourcestring, this is stored as a standard Windows string resource, each string with an assigned number id. These strings are saved in the executable and can be extracted in LinLocalize (by using winresbind). When new resourcestrings are added to the application or existing resourcestrings are removed, the compiler can atrribute new id's to the resourcestrings. The id's are therfore unstable. It is therefore absolutely necessary to update the translations and the resourcefile in each desired language when issuing a new version. This is most easily accomplished by saving the translations in a .glo file, so that once translated strings can be re-used.
Delphi (and Windows) can also generate and use names as id's, in stead of numbers. Delphi generates these names when you ask for the creation of a drc file. Linlocalize can use this file. These named id's will only change if the programmer intentionally changes the resourcestring variable name. Therefore, these id's are stable and generated resourcefiles can be used even after a new compilation. Please be beware to use a unique string for each resourcestrings. Linlocalize can use the named id's and couple these to the correct number id's.
Linlocalize can use the drc file when this is placed in the same directory as the executable that is to be localized. Please note that a drc file can be incomplete when the executable has new resource strings or resourcestrings from another source, currently unavailable to Delphi. It is always best to ensure the creation of a new drc file when recompiling the executable and to recreate a fresh resourcefile when issuing a new version of your executable.
Both methods have their advantages and disadvantages. Please use always the most current drc file and executable for a fresh translation.