RAD Studio |  |

Using Resource DLLs
See Also
Collapse All

The executable, DLLs, and packages (bpls) that make up your application contain all the necessary resources. However, to replace those resources by localized versions, you need only ship your application with localized resource DLLs that have the same name as your executable, DLL, or package files.

When your application starts up, it checks the locale of the local system. If it finds any resource DLLs with the same name as the EXE, DLL, or BPL files it is using, it checks the extension on those DLLs. If the extension of the resource module matches the language and country of the system locale, your application will use the resources in that resource module instead of the resources in the executable, DLL, or package. If there is not a resource module that matches both the language and the country, your application will try to locate a resource module that matches just the language. If there is no resource module that matches the language, your application will use the resources compiled with the executable, DLL, or package.

If you want your application to use a different resource module than the one that matches the locale of the local system, you can set a locale override entry in the Windows registry. Under the HKEY_CURRENT_USER\Software\Borland\Locales key, add your application's path and file name as a string value and set the data value to the extension of your resource DLLs. At startup, the application will look for resource DLLs with this extension before trying the system locale. Setting this registry entry allows you to test localized versions of your application without changing the locale on your system.

For example, the following procedure can be used in an install or setup program to set the registry key value that indicates the locale to use when loading applications:

Copy Code

    procedure SetLocalOverrides(FileName: string, LocaleOverride: string);
    var
    Reg: TRegistry;
    begin
    Reg := TRegistry.Create;
    try
    if Reg.OpenKey('Software\Borland\Locales', True) then
    Reg.WriteString(LocalOverride, FileName);
    finally
    Reg.Free;
      end;
    end;

Copy Code

    void SetLocalOverrides(char* FileName, char* LocaleOverride)
    {
    HKEY Key;
    const char* LocaleOverrideKey = "Software\\Borland\\Locales";
    if (RegOpenKeyEx(HKEY_CURRENT_USER, LocaleOverrideKey, 0, KEY_ALL_ACCESS, &Key)
    == ERROR_SUCCESS) {
    if (lstrlen(LocaleOverride) == 3)
    RegSetValueEx(Key, FileName, 0, REG_SZ, (const BYTE*)LocaleOverride, 4);
    RegCloseKey(Key);
    }
    }

Within your application, use the global FindResourceHInstance function to obtain the handle of the current resource module. For example:

Copy Code

    LoadStr(FindResourceHInstance(HInstance), IDS_AmountDueName, szQuery, SizeOf(szQuery));

Copy Code

    LoadString(FindResourceHInstance(HInstance), IDS_AmountDueName, szQuery, sizeof(szQuery));

You can ship a single application that adapts itself automatically to the locale of the system it is running on, simply by providing the appropriate resource DLLs.

See Also

Creating Resource DLLs

Copyright(C) 2009 Embarcadero Technologies, Inc. All Rights Reserved.
What do you think about this topic? Send feedback!