Installation manual

226 Miscellaneous Configuration
Possible Errors
The following errors may be generated. Check the structure of your code to
prevent such errors from occurring.
1. Runtime Font creation check
If you use the font name and no mapping information exists in the INI for the
font, or the font does not exist, the following error will occur. “Font not
supported.: Name'%1' Operation: '%2' Element: '%3'.”
Font not supported. Name: 'FontName' Operation: 'Front-Monochrome
Mass Transfer (300 DPI)-UG_BLACK-Default Process-Default Group'
Element: 'UGDataText3'
2. Possible dccFontMap.ini syntax errors
00400 ImageGen - DCCFontMap Parser:
'C:\Maxsys\cfg\dccFontMap.ini' file has 5 error(s); Please see EventLog
for error details.
DCCFontMap Parser: Section 'missing ttfFile'; cannot find require field
ttfFile
DCCFontMap Parser: Section 'bad syntax'; cannot find required field
ttfName and pointSize
DCCFontMap Parser: Section 'missing ttfName'; cannot find required
field ttfName
DCCFontMap Parser: Section 'Missing pointsize'; cannot find require field
pointSize
DCCFontMap Parser: Section 'DC-OCRA.10PT'; is empty. You should
remove that section or define 3 required fields.
3. Unicode Font Image Generation Errors
If a font has been created with non-standard unicode content, cards may not
print correctly. See “Unicode Font Image Generation Errors” on page 127 for
information about correcting this problem.