|
Localization of PE32/PE32+ files - Selecting a localization method |
 |
 |
 |
|
JPAGE_CURRENT_OF_TOTAL
Selecting a localization method
The author chooses the localization method for PE32/PE32+ applications himself.
All methods have their advantages and disadvantages. Therefore there is no definite answer as to which method to choose.
|
Advantages
|
Disadvantages
|
|
Resource Library
|
1. Small size
2. Installation package can contain a library only for required languages, which reduces its size.
3. Easy to add support for dynamic switching of interface language.
4.Automatic loading of a resource library based on the current language when a VCL library is used (Delphi/C++Builder), utomatic loading of resources from .NET assemblies (.NET applications, forms labeled as “Localizable”), support by other libraries and compilers.
|
1.No support for localization of hard-coded strings.
|
|
Multilingual resource library
|
1. Automatic selection of resources for the current language by OS when standard functions are used in the application.
|
1. No support for localization of hard-coded strings.
|
|
Localized file
|
1. Support for localization of hard-coded strings.
2. Translation is contained inside one file, which ensures reliability of the application.
|
1. Large size, larger than the original file.
2. No support for dynamic switching of language.
|
|
Multilingual localized file
|
Single file. No need to distribute additional files, which increases reliability of the application.
2. Automatic selection of resources for the current language by OS when standard functions are used in the application.
|
1. No support for localization of hard-coded strings.
2. Difficult to realize dynamic switching of language.
|
If you are not the author of the localized application and do not know the localization method it supports, we recommend you to build a resource library that meets the criteria described in the "Resource Library" section. As compared to localized files, the benefit of resource libraries lies in their smaller size. If the localized application does not load a resource library, you can localize the application by creating a localized file – a copy of the original file but with modified resources. If the localized application loads a
resource library, but there are some hard-coded strings that need to be localized, the only localization method is to create a localized file.
|
