Font engine logfile

From DISE KnowledgeBase

Jump to: navigation, search

The font engine in DISE will scan all fonts during first startup, or when a re-scan is requested. The scan will create a font list that DISE will use later to start up more quickly. When DIse scans the font paths for files it is common to encounter problems, such as corrupted font files or duplicate typefaces.

All problems and actions will be reported in a log-file named "Fonts.logfile" that is placed in the DISE temp directory (normally %TEMP%\DISE\DISE 8). The log-file is a good place to start if the font you want was not found by DISE.

To get the log-file of a font scan, you need to re-scan the fonts in the Composer Preferences > Fonts tab dialog on the manager or Replay Preferences > Fonts tab dialog on the player.

Common log entries

Duplicate files: (path1/xxx) (path2/xxx)

The same file was found in two different places. Only one of the files will be used. This will not result in any problem, but it can be good for you to know.


Duplicate typefaces: (MyFont,Regular)
# (path1\xxx.pfb) <<< Selected
# (path1\yyy.ttf)

The same typeface was found with 2 different technologies. The font engine will select the preferred technology as specified in the Composer Preferences > Fonts tab (or Replay Preferences > Fonts tab on the player)


# (path1\xxx.ttf) <<< Defined
# (path1\yyy.ttf)

A font file was found with the same typeface as a font that was defined in FontEngine.settings. The defined font will override the found font file.

Error reading font information in file: (path1\xxx.ttf)

The font file was corrupt in some way. The old font engine might have shown it anyway, but the new font-engine will discard the file. If you really need the font, it can be forced to be loaded via the FontEngine.settings file. However, this can compromise both system stability and the appearance of the forced font.


Normally the logfile only contains the text:

Font engine started: 2006-07-26 11:28:55
Reading cached fontlist.