During the draft stage, policy authors create sections and sub sections to write the content that describes a policy. Authors can use different fonts to highlight notes and headings that will help them differentiate the text from other contents in a policy. This also enables policy viewers to search the content in the policy that is relevant only to them. A policy generated in PDF uses built-in fonts by default - Times New Roman, Arial, and Courier. When a policy is created using different fonts, as a policy author you will need to ensure that fonts in the PDF files match with the fonts used in the policy in RiskVision.
If a font is not rendered in PDF, even when it is available in the operating system and RiskVision, perform the following steps to change the font directory location to render fonts correctly in PDF:
- Go to the
%AGILIANCE_HOME%\Tomcat\webapps\spc\WEB-INF\classes\directory and open thepd4font.propertiesfile by using a text editor. - Locate the following property and set the property to point the fonts directory to the location where your operating system is installed. By default, the property is set to as:
font.dir.location=C:\Windows\Fonts
For example, if you have installed your operating system in theD:\directory, then you should set the property to asD:\Windows\Fonts. - Restart the RiskVision Tomcat service. The PDF should now be able to render the fonts correctly.
If a font is still being substituted with a different font after changing the fonts directory location, the font is not available in the operating system, or the PD4ML tool that generates the PDF does not support the font. In both the cases, the fonts in PDF are substituted according to the fallback tables of the font group. To learn how a fallback rule is applied for substituting a font, visit the following URL:
