7.5

Table Of Contents
When you install a document on a PlanetPress Suite Workflow Tool server, you should make sure the fonts included in the doc-
ument are actually available on the PlanetPress Suite Workflow Tool server. To install TrueType fonts, use the standard Win-
dows procedure. To install PostScript fonts, use the Install PostScript Font command in your PlanetPress Suite Workflow
Tool.
Run a Document that Uses a Database Emulation
You cannot install a document that uses database emulation on a printer and send a trigger along with the data to have the doc-
ument print. Only PlanetPress Design and PlanetPress Suite Workflow Tools can perform the necessary conversion of the data
before sending it to the document.
In most cases you run a document that uses database emulation in a PlanetPress Suite Workflow Tool. This makes it possible
to automate the execution of the document, and ensures that the data sent to the document always reflects the contents of the
database at the time the document prints. Consult the PlanetPress Workflow Tools User Guide for help printing a document
that uses a database emulation.
You can also use the hard copy preview capability in PlanetPress Design to print the document with all or some of the data-
base. In this case, in the hard copy preview options, you should select Refresh data from database to update the contents of
the sample data file before executing the preview. This ensures the preview reflects the latest changes to the database.
Run Several Documents as a Single Job
If you have several documents to run on a printer, and you are not using the PlanetPress Suite Workflow Tools to print your
documents, you may find it convenient to send a single job to the printer that contains the triggers and input data for all those
documents. The single job has the format:
trigger1data1trigger2data2trigger3data3...
Embedded within this single job are End Of Job (EOJ) strings that permit each document to detect the end of its input data.
These strings prevent each document in the job from treating everything that follows it as its own input data.
You define the EOJ string you want a given document to use. You may choose to define a different EOJ string for each doc-
ument, or to use the same EOJ string for all documents or for all documents of a certain category. The choice you make
depends on your environment and preferred way of working. If you choose a different EOJ string for each document or cat-
egory of document, you must pay close attention to how you construct the single job to ensure you specify the proper EOJ
string for a given document.
You can embed the EOJ strings in the single job in one of two ways: either within the triggers or at the end of input data.
This section describes how to construct a job by embedding EOJ strings within a trigger and how to construct a job by append-
ing EOJ strings to the end of input data. It also includes a procedure that explains how to define an EOJ string for a document.
Troubleshoot Execution Problems
You should also be aware that there are two printer settings that can help you troubleshoot a problematic document.
1. Print PostScript Error
If you enable this setting, the printer prints an error page if it encounters an error during document execution. The
error page reports the offending PostScript command and the status of the print stack. Although these errors are terse,
they are sometimes all you need to pinpoint and resolve the problem. You can set this printer setting from PlanetPress
Design.
2. Print in Hexadecimal Mode
Document Output and Preview
©2010 Objectif Lune Inc - 676 -