Font handling

The fonts in the PDF input file are referenced by PDF specific font names. These font names must be mapped to Windows font names, which in most cases is done automatically. To avoid font problems, do the following before you use the PDFIN filter:

•	Make sure all fonts used in the PDF document are installed on the machine where you run the PDFIN filter.

•	Add the font mapping table pdfinfontmap.tbl to the PDFIN filter configuration.

Note:

You do not have to map embedded fonts.

The font mapping table

The font mapping table pdfinfontmap.tbl should be imported to the resource set that includes the PDFIN filter. The table is located in the following directory relative to the StreamServe installation directory:

Applications\StreamServer\<version>\Common\Modules\Filters

This table contains mappings for the most common PDF font names to Windows font names. The font mapping entries have the following syntax:

"PDF font name" TAB "Windows font name" [,Bold, Italic Weght<value> <Embed>]

where:

•	Weght<value> – An exact value of the boldness.

•	<Embed> – is one of the following:

–	EmbedNo – Never embed the font.

–	EmbedMissing – Embed font when it is not available on the machine where the PDFIN filter is installed.

–	EmbedAlways – Always embed the font.

Example 1

pdfinfontmap.tbl sample

...
"OCRA-Alternate"               "OCRA Alternate"
"OCRB"                         "OCRB"
"OCRB-Alternate"               "OCRB Alternate"
"MICR"                         "MICR"
"HelveticaNeue-UltraLight"     "Helvetica 25 UltraLight"
"HelveticaNeue-UltraLightItal" "Helvetica 25 UltraLight, Italic"

"Bodoni-Bold"	                  "Bodoni, Bold Weight900 EmbedMissing"

...

 

To display the fonts used in the PDF document

1	Open the PDF document in Adobe® Reader®.

2	Select File > Document Properties > Fonts to display the fonts used in the document.

3	Depending on the version of Adobe® Reader®, you may have to click List All Fonts to display all fonts used in the document, and not only the fonts used on the current page.

All PDF font names are now displayed. You must make sure all corresponding Windows fonts are installed.

To add the font mapping table to the filter configuration

1	Open the PDFIN filter in the Filter Chain editor.

2	In Font Mapping File Name, select the pdfinfontmap.tbl resource.

To verify that all fonts are mapped correctly

Run the Project and examine the log. If all fonts are mapped correctly, no error messages are displayed in the log. If a font is not mapped correctly, it is displayed as (4132) <pdf font> not found in the system. In this case, you must make sure the corresponding Windows font is installed, and then map the PDF font to the Windows font in the pdfinfontmap.tbl resource. See The font mapping table.

Example 2

Log showing that all fonts are mapped correctly.

...

(4130) PDFIN: Starting conversion...
(4131) PDFIN: Starting normalization...
(4131) Producer: StreamServer 5.0.0 Build x.
(4130) PDFIN: Conversion completed successfully.

...

 

Example 3

Log showing that the PDF font HelveticaNeue-Light is not mapped correctly.

...

(4130) PDFIN: Starting conversion...
(4131) PDFIN: Starting normalization...
(4131) Producer: StreamServe StreamServer 5.0.0 Build x.
(4132) HelveticaNeue-Light font not found in the system.
(4130) PDFIN: Conversion completed successfully.

...

In this example, the PDF font HelveticaNeue-Light must be mapped to the Windows font Helvetica 45 Light. This means you must add the following line to the pdfinfontmap.tbl resource:

"HelveticaNeue-Light"    "Helvetica 45 Light"

You must also make sure Helvetica 45 Light is installed.