callas pdfInspektor

This configurator drives callas pdfInspektor3 and pdfInspektor4, CLI editions. It is a processor that preflights a PDF file according to specifications. The PDF file itself flows along the “data” output connections, the preflight report flows along the “log” output connections.

Refer to Version requirements for third-party applications for more information on the third-party application required by this configurator.

Keywords

Keywords can be used with the search function above the elements pane.

The keywords for the callas pdfInspektor configurator are:

PDF
PDF/X
preflight
correct
fix
modify
optimize
convert
color
colour
GWG
profile

Detecting the application

This configurator implements the following mechanisms to detect the presence of the corresponding third-party application. See Detecting third-party applications for more information.

Detection mechanism	Comments
Automatic detection at startup	Uses information registered with the operating system when the application is installed (Windows) or checks the default install location (Mac) The configurator first looks for pdfInspektor4, then for pdfInspektor3
Searching from the elements pane	In addition to the above, searches the system program files/applications folder for the application
Manually locating the executable	Select the executable for the command-line version of the application

Detection mechanism

Comments

Automatic detection at startup

Uses information registered with the operating system when the application is installed (Windows) or checks the default install location (Mac)

The configurator first looks for pdfInspektor4, then for pdfInspektor3

Searching from the elements pane

In addition to the above, searches the system program files/applications folder for the application

Manually locating the executable

Select the executable for the command-line version of the application

Connections

This configurator supports any number of outgoing traffic-light connections.

Properties

Property	Description
Name	The name of the flow element displayed in the canvas
Preflight profile	The callas preflight profile to be used to preflight the file; browse for a profile package (*.kfp) shipped with pdfInspektor or saved from Adobe Acrobat, which uses the callas preflight technology (Acrobat 7 corresponds to pdfInspektor3; Acrobat 8 corresponds to pdfInspektor4)
Report type	The format of the preflight report; choices include: Text: plain text file (UTF-8 encoding) intended to be processed by software Compact: plain text file (UTF-8 encoding) intended for human readers XML: XML file with informal schema XMLV2: XML file that formally conforms to the XML schema installed with pdfInspektor4 (available only for pdfInspektor4; for pdfInspektor3 this choice automatically reverts to XML) PDF mask: original PDF file with semi-transparent masks inserted on new layers to visually indicate preflight problems PDF comments: original PDF file with comments inserted to indicate preflight problems. PDF layer: original PDF file with certain text, graphics and image objects separated on different layers; this is more than strictly a report format (see PDF layer report type below) Inventory: PDF document that provides statistics; intended for human readers (see Inventory report type below)
Report language	The human language for the preflight report; choices include: Danish, German, English, Spanish, Finnish, French, Italian, Japanese, Korean, Dutch, Norwegian, Portuguese, Swedish
Max errors per document	The maximum number of errors reported for a document
Max errors per page	The maximum number of errors reported for a page
Allow PDF/X or PDF/A conversion	If set to yes, and the selected preflight profile specifies PDF/X or PDF/A conversion, and the original PDF file can be converted, the configurator moves the converted PDF/X or PDF/A file along the outgoing data connections; otherwise it moves the original PDF file along the outgoing data connections (see PDF/X or PDF/A conversion below)

Text and XML report types

The following extra properties are shown for Text and XML report types; the first property in the table is also shown for the XMLV2 report type.

Property	Description
Include problem details	If set to yes, the report includes all details for objects causing a preflight problem (this corresponds to the “text-long” report format offered in the Switch 06 configurator)
Include page resources	If set to yes, resources such as color spaces and fonts are listed for each page
Include page information	If set to yes, information such as page size is listed for each page
Include document resources	If set to yes, resources such as color spaces and fonts are listed for the document as a whole

PDF layer report type

The following extra properties are shown for the PDF layer report type. They allow specifying which objects should be extracted to separate layers. For example, when the “Separate spot colors” property is set to yes, all objects painted with a spot color are placed on a new layer named for the spot color.

Property	Description
Separate fonts	If set to yes, the report has a separate layer for each font used in the original PDF
Separate ICC profiles	If set to yes, the report has a separate layer for each ICC profile used in the original PDF
Separate spot colors	If set to yes, the report has a separate layer for each spot color used in the originalPDF

Inventory report type

The following extra properties are shown for the Inventory report type.

Property	Description
Include fonts	If set to yes, information on fonts is included
Include colors	If set to yes, information on colors is included
Include shades	If set to yes, information on shades is included
Include patterns	If set to yes, information on patterns is included
Include images	If set to yes, information on images is included
Minimum image size (pixels)	Only information for images larger than this threshold is included (this property value is used only if “include images” is set to yes)
Include form xobjects	If set to yes, information on form XObjects is included
Include XMP	If set to yes, information on XMP metadata is included
Include XMP advanced	If set to yes, advanced information on XMP metadata is included

The Inventory report type does not require a preflight profile. In fact it is invalid to provide a preflight profile when this report type is selected.

PDF/X or PDF/A conversion

For PDF/X or PDF/A conversion to take place, the following three conditions must be simultaneously satisfied:

The “Allow PDF/X or PDF/A conversion” property is set to yes.

The profile selected in the “Preflight profile” property specifies PDF/X or PDF/A conversion.

The incoming PDF file can be successfully converted to the specified flavor of PDF/X or PDF/A.

The configurator’s behavior in various situations is summarized in the following table.

Allow PDF/X or PDF/A conversion	Profile specifies conversion	Incoming file can be converted	Result placed on data connections	Level of success on connections
No	don’t care	don’t care	Original file	Depending on preflight result
Yes	No	don’t care	Original file	Depending on preflight result
Yes	Yes	No	Original file	Error
Yes	Yes	Yes	Converted file	Success or warning