Mapping AFP Fonts to TrueType Fonts, OpenType Fonts, or TrueType Collection Fonts
The extension is specified to differentiate from a mapping to a Type1 font. The extensions
that can be used are .ttf for mapping to TrueType fonts, .otf for mapping to OpenType fonts, and .ttc for mapping to TrueType font collections.
For the mapping to work, AFP2PDF Plus searches for the exact name specified in the
alias.fnt file, such as TrueTypeFont-Name.ttf, OpenTypeFont-Name.otf, or FontName@TrueTypeCollection-Name.ttc, in the folder specified by the TrueType_Directory configuration file. You can specify
the TrueType_Directory in the configuration file as stated in the Mapping AFP Fonts to TrueType Fonts, OpenType Fonts, or TrueType Collection Fonts. If the specified font file is missing from the TrueType_Directory path or the font
name is not valid, AFP2PDF Plus uses the default Times New Roman font.
When mapping using TrueType font collections, you must specify what font from the collection is used. To specify the font, add the name or the 0-based index of the font, followed by the @ character, in front of the file name of the TrueType font collection.
Any code page defined in the Code Page Definition File (cpdef.fnt) can be used when mapping AFP Fonts to TrueType Fonts. Remember that the code page characters must be within the TrueType character set. To use custom character encoding, the mapping must be placed in the Code Page Definition File and the .ucm file must contain the code page identification in the name structure and must be in the Locale Directory.
AFP font to TrueType font mapping in the alias.fnt file
;**** Requested font=font name,Font metric/AFM file name (or 'NULL' for not used) ***** Font1=TrueTypeFont-Name.ttf,NULL Font2=OpenTypeFont-Name.otf,NULL Font3=FontName@TrueTypeCollection.ttc,NULL Font4=2@TrueTypeCollection.ttc,NULL ;******* End User-defined/Custom names ******* EndCharMetrics