4D v16.3Get database localization |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
4D v16.3
Get database localization
Get database localization
The Get database localization command returns the default language or the language of the database specified by the languageType, expressed in the standard defined by the RFC 3066. Typically, the command returns “en” for English, “es” for Spanish, etc. For more information about this standard and the values returned by this command, please refer to Appendix C: XLIFF architecture in the Design Reference manual. Several different language settings can be used simultaneously in the application. To designate the setting to be obtained, in languageType you can pass one of the following constants, found in the 4D Environment theme:
By default, if you omit the languageType parameter, the command returns the default language (0). The current language of the database can be used to determine the .lproj folder where the program will look for the localized items of the database. 4D automatically determines the current language on database startup according to the contents of the Resources folder and the system environment. How it works is that 4D loads the first .lproj folder of the database that corresponds to the reference language, with the following order of priority:
Note: If the database does not have an .lproj folder, 4D applies the following order of priority: 1. System language, 2. English (if the system language cannot be identified).
See also
|
PROPERTIES
Product: 4D
HISTORY
Created: 4D v11 SQL ARTICLE USAGE
4D Language Reference ( 4D v16) |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||