TTMSFNCLocalizationLocalizer.LocalizationFolder Property
Folder that is scanned for translation files.
API unit family: TMS.TMSFNCLocalizationLocalizer
Declaring type: TTMSFNCLocalizationLocalizer
Type: string
Syntax
property LocalizationFolder: string;
__property System::UnicodeString LocalizationFolder = {read=GetLocalizationFolder, write=SetLocalizationFolder};
Remarks
The value may start with a prefix token that is expanded when the folder is resolved: {DEPLOY} is the folder files deployed with the application end up in, {APP} is the folder holding the executable, {DOC} the current user's documents folder, {HOME} the current user's application-support folder, and {PF} the Program Files folder (Windows only). Token names are not case-sensitive, and a token that is not recognized is left in the path unchanged. An empty value means {DEPLOY}. After expansion, a path that is still relative is resolved against {DEPLOY}; an absolute path is used as-is. On Windows {DEPLOY} and {APP} are the same folder. They differ on macOS, iOS and Android, where the IDE's deployment places added files inside the application bundle: {DEPLOY} points at them there - Contents/Resources/StartUp on macOS, the bundle root on iOS, TPath.GetDocumentsPath on Android - while {APP} keeps pointing beside the bundle. Use {DEPLOY}, or leave the value empty, for files that ship with the application, and one setting then works on every target.
Use the same folder here as the component that writes the translation data, and make sure it is one the application can write to when anything saves into it: the usual install locations - {APP} under Program Files, and {PF} itself - are read-only for a standard user. Reading translations from {APP} is fine; writing them there is not.
Prefix tokens are expanded in desktop applications only; in web applications the value acts as a base URL and is used as given.