A Rich Text resource represents a formatted text for use in the installer's user interface, typically for the product's license agreement or installation information. To display a Rich Text resource, you must place a RichText control in the dialog box, then link the control to the desired Rich Text resource.
Tarma Installer controls that accept a Rich Text resource are: RichText
This pane contains the following attributes and options.
| Attribute | Description |
|---|---|
| Name | Enter the name for the Rich Text resource. This name is used in Tarma Installer to refer to the text and must be unique among all Rich Text resources. |
| File path |
Displays the file path for the Rich Text resource. This is optional; if you don't specify a file path, the Rich Text resource is stored inside the Tarma Installer project file. To save the Rich Text resource in an external file, click Save As... to open a standard Save As dialog box that lets you specify the desired file name and location. From then on, the Rich Text resource is stored in that file instead of in the Tarma Installer project file. |
You can edit Rich Text resources in Tarma Installer. By default, Rich Text resources are stored inside the Tarma Installer project file. However, if you assign a File path (see above) to the resource, the Rich Text is stored in that file and the project file only contains the file path to the external resource file. This allows you to edit the Rich Text both from within Tarma Installer and through an external editor.
Be sure to edit it from only one application at the time, and to save any changes before you switch to another editor. In particular:
Tip: If you want to use an external editor to edit a Rich Text file, we strongly recommend that you use the WordPad tool that comes with Microsoft Windows. WordPad uses a limited subset of the RTF syntax that is compatible with the RichEdit controls used by the installers. (In fact, WordPad internally uses that same RichEdit control.) Other RTF-capable word processors may add additional and sometimes very verbose formatting that is ignored at best, and may cause rendering problems at worst.