Providing fonts for XSL-FO-transformations
Font installation
New fonts need to be copied to the server by terminal.
Preinstalled fonts are in /opt/corpus/css/app/services/xslfop/fonts/
Requirements
- If the directory /opt/corpus/cscs/app/services/xslfop/fonts/ does not yet exist, you must create it to be update safe.
- Now copy your new fonts to /opt/corpus/cscs/app/services/xslfop/fonts/ The fonts should be in format TTF (or maybe OTF)
- Check the permissions and ownership of your new fonts on the server. This should be: -rw-r--r-- 1 corpus corpus
Service configuration
Requirement: If the file /opt/corpus/cscs/app/services/xslfop/fop-config.xml does not exist yet you must copy fop-config.xml from .../css/app/services/xslfop/ to be update safe.
In fop-config.xml you need to edit (line marked with "+" is a new line, remove the "+"):
<fonts>
<directory>/opt/corpus/css/app/services/xslfop/fonts</directory>
+ <directory>/opt/corpus/cscs/app/services/xslfop/fonts</directory>
<auto-detect/>
Hints: In AdminClient the "Services / XSL-FO / Configuration" is only related to .../services/xslfop/config.xml, which is active in standard and needs no further change.
<auto-detect/> finds every font on the machine, so this might affect performance.
<auto-detect/> and <directory/> can be used single wise or in parallel.
Always define a new <directory/> in fop-config.xml where you store your fonts. If later on, someone should deactivate <auto-detect/> for performance reasons, these fonts would not be found any longer.
Finally, click "Update Server Configuration" to activate the changes (even if only a new font was installed and no fop-config.xml changed). As a general recommendation, this should be done in a maintenance window.