From Stages version 7.9.7.0 onward, there is a new simpler way to define which font should be used for the creation of PDF files and process visualizations. You only need to choose one of the provided fonts or your own TrueType font and set its filename via a configuration property.

Open the file <Stages Installation Directory>\stages\conf\config.xml (Windows) or /opt/stages/conf/config.xml (Linux) and find the properties section.

In case you are updating an older Stages version: The new “global.font” property replaces the configuration via the properties “pdf.font.list”, “diagram.font” or the even older “diagram.font.list”. Remove these entries if you are currently using them.

The format for the property is as follows:

<property name=“global.font” value=“SourceSansPro-Regular.ttf”/>

The value contains the font file name. If you want to use a custom font, place the TrueType font file in this folder:

Windows: <Stages Installation Directory>\stages\conf\fonts
Linux: /opt/stages/conf/fonts

Alternatively, you can place the font file anywhere and specify the filename with the absolute path.

If you use the “global.font” property, changing the metamodel is no longer required.

The fonts that are installed together with stages are in the following folder:

Windows: <Stages Installation Directory>\tomcat\webapps\stages\fonts
Linux: /opt/stages/tomcat/webapps/stages/fonts

Depending on the charset you need, you can choose one of the following fonts:

Remember to execute bin/update.bat (Windows) or bin/update.sh (Linux) and restart Stages.

Some fonts, even the font “Source Han Sans” installed with Stages, have some rendering issues. This font causes missing text in process visualizations when you use Adoptium Temurin 8 as JDK.

The PDF files generated with this font have incorrect line spacing.

In case you need Chinese characters, we recommend that you provide your own font.