TTMSFNCLocalizationCollector.LocalizationFolder Property
Folder the translation data is loaded from and saved to.
API unit family: TMS.TMSFNCLocalizationCollector
Declaring type: TTMSFNCLocalizationCollector
Type: string
Syntax
property LocalizationFolder: string;
__property System::UnicodeString LocalizationFolder = {read=FLocalizationFolder, 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.
Point this at a folder the application can write to. The collector saves the translation data back to this folder, and the usual install locations - {APP} under Program Files, and {PF} itself - are read-only for a standard user, so saving there fails. Prefer {HOME} or {DOC} whenever the data is written at run time; {APP} is appropriate for translations that ship with the application and are only read.
Prefix tokens are expanded in desktop applications only; in web applications the value is used as given.