[next] [prev] [prev-tail] [tail] [up]

9.2 The resource string le

When a unit is compiled that contains a resourcestring section, the compiler does 2 things:
  1. It generates a table that contains the value of the strings as it is declared in the sources.
  2. It generates a resource string le that contains the names of all strings, together with their declared values.

This approach has 2 advantages: rst of all, the value of the string is always present in the program. If the programmer doesn't care to translate the strings, the default values are always present in the binary. This also avoids having to provide a le containing the strings. Secondly, having all strings together in a compiler generated le ensures that all strings are together (you can have multiple resourcestring sections in 1 unit or program) and having this le in a xed format, allows the programmer to choose his way of internationalization.

For each unit that is compiled and that contains a resourcestring section, the compiler generates a le that has the name of the unit, and an extension .rst. The format of this le is as follows:

  1. An empty line.
  2. A line starting with a hash sign (#) and the hash value of the string, preceded by the text hash value =.
  3. A third line, containing the name of the resource string in the format unitname.constantname, all lowercase, followed by an equal sign, and the string value, in a format equal to the pascal representation of this string. The line may be continued on the next line, in that case it reads as a pascal string expression with a plus sign in it.
  4. Another empty line.

If the unit contains no resourcestring section, no le is generated.

For example, the following unit:

unit rsdemo;  
 
{$mode delphi}  
{$H+}  
 
interface  
 
resourcestring  
 
  First = 'First';  
  Second = 'A Second very long string that should cover more than 1 line';  
 
 
implementation  
 
end.

Will result in the following resource string le:

 
# hash value = 5048740  
rsdemo.first='First'  
 
 
# hash value = 171989989  
rsdemo.second='A Second very long string that should cover more than 1 li'+  
'ne'  

The hash value is calculated with the function Hash. It is present in the objpas unit. The value is the same value that the GNU gettext mechanism uses. It is in no way unique, and can only be used to speed up searches.

The rstconv utility that comes with the Free Pascal compiler allows to manipulate these resource string les. At the moment, it can only be used to make a .po le that can be fed to the GNU msgfmt program. If someone wishes to have another format (Win32 resource les spring to mind), one can enhance the rstconv program so it can generate other types of les as well. GNU gettext was chosen because it is available on all platforms, and is already widely used in the Unix and free software community. Since the Free Pascal team doesn't want to restrict the use of resource strings, the .rst format was chosen to provide a neutral method, not restricted to any tool.

If you use resource strings in your units, and you want people to be able to translate the strings, you must provide the resource string le. Currently, there is no way to extract them from the unit le, though this is in principle possible. It is not required to do this, the program can be compiled without it, but then the translation of the strings isn't possible.

[next] [prev] [prev-tail] [front] [up]