If z.B. the license field for the package section is set to GPL-3.0, the GPL-3.0 license must be generated automatically in RTF format. Custom licenses require a manual modification of the WiX Source (wxs) file, but licenses supported by the license field must be automatic. There are many license ids supported, so that perhaps only first support the most common used by the Rust project: Apache-2.0, MIT, and GPL-3.0. You can customize some visual aspects of the interface by simply providing replacement files. You can create standard bitmaps, symbols and license texts, but you can create your own bitmaps, symbols and license text. You can also replace selected files, not all of them. Your paths are stored in variables that you can specify either in the command line or directly in the source code: the file contains text (a whole license!), and the text is well formatted. I tried the code below with UI-CustomDialog.wxs file, but it didn`t work. It shows the stage of the EULA.
The WixUI dialogue library contains standard bitmaps for the context of the home and closing dialogues as well as the top banner of the other dialog boxes. You can replace these bitmaps with their own product brand purposes. To replace standard bitmaps, specify WiX variable values with the file names of your bitmaps, just like when replacing the default license text. There is a well-known problem with rich text control, which is used to display the text of the license file, which can result in the text being displayed empty until the user scrolls down into the control. This is usually caused by complex RTF content (z.B the RTF generated when recording an RTF file in Microsoft Word). When you run this behavior in your configuration user interface, one of the following problems is corrected in most cases: A License Agreement Rich Text Format (RTF) should be generated based on a package`s manifest license field (Cargo.toml) if the -init option is used. The WixUI_FeatureTree dialog box is used in the built-in model because it indicates a dialog box to customize the installation. All integrated dialog boxes for The WiX Toolset have a license dialog box. A generic substitute is used if the is not used or not, but we should be able to use the license information from the package manifest to automatically replace the generic substitute with the package-specific license.
stackoverflow.com/questions/16978501/how-to-create-a-bootstrapper-application-without-a-license-agreement-step If the license file field is used in the manfiest package, it will be used for the license file.rtf, but I`m not sure how the file will automatically be converted to RTF.