The content file (.PDF) of a regular report

The content file is a normal PDF consisting of a number of pages and containing images, icons and fonts to be used in your customized report.

Note: Afterwards, you will have to indicate in the .prefs file what the images and icons are used for and where they can be found in the PDF. Refer to PitStopReportPDFTemplates.

The PDF file usually contains 3 different parts:

One background page
This page is considered to be the most important one because this is what you'll see as a background for each page in the report. The page is normally set on the first page of the content file and can maximum be one page.
The background page forces the page size used for the complete preflight report.
Add here the company logo, the company name and extra info as required.

Tip: To speed up report creation and to reduce the file size of the report, we recommend putting all elements of the background page in one single PDF form object. To do so, you can use the Action Put Selection in Form. For more information about this Action, refer to the Action Manual on the Enfocus website.

Example:
Several icon pages
These pages hold the different icons used in the preflight report:
- Icons in front of the subtitles "Fixes", "Warnings", ...
- Icons in front of fixes, warnings and errors,...
- Icons for hyperlinks to the objects
- Icons for hyperlinks to the product webhelp
You should afterwards identify these icons by entering the page numbers in the .prefs file. Refer to PitStopReportPDFTemplates.
Note:
- The icons are not scaled which means that the way the icon is set on these pages is how they will end up in the preflight report.
- There can be only 1 icon per page, i.e. one single object (an image, a path, a text or a form).
Example:
A font resource page
For faster report generation, when using large composite fonts for languages such as Japanese or Chinese, you can specify a font resource page. Such a page contains PDF text objects with non-embedded composite fonts. If one of these composite fonts should be used in the report, i.e. if the font name is used in the .prefs file to define a font (e.g. the FontName in PitStopReportBody PitStopReportBody), the font resource from this page is used to create the report font.

Note: Keeping this page for other languages, does not slow down the process, so you can just leave it in, even if you don't need it.

Example:

Note: Instead of having 3 parts in one file, you could also create up to three different content (.PDF) files for one .prefs file. However, as checking 3 files instead of one will take more time (hence slow down the preflight report creation), we recommend combining all of them into 1 PDF file.