jefc
Member
Hello,
We are including an RTF file as End-User License Agreement in our directive file as follows:
(where #{pathToEula} is replaced by the absolute file path using a script)
After upgrading to Paquet Builder 2025, the EULA layout is broken as if the RTF file was processed somehow. I also tried using a TXT file, HTM file and markdown file and the result is the same: it looks like it is impossible to include the file as is.
Paquet Builder 2020:

Paquet Builder 2025:

Do you know how to overcome this?
Thanks for your help.
We are including an RTF file as End-User License Agreement in our directive file as follows:
Code:
[Templates]
LicAg=#{pathToEula}
(where #{pathToEula} is replaced by the absolute file path using a script)
After upgrading to Paquet Builder 2025, the EULA layout is broken as if the RTF file was processed somehow. I also tried using a TXT file, HTM file and markdown file and the result is the same: it looks like it is impossible to include the file as is.
Paquet Builder 2020:

Paquet Builder 2025:

Do you know how to overcome this?
Thanks for your help.


