Xerox DocuColor 12 Printer with Fiery X12 产品宣传页
6
6-16
Advanced Features of DocBuilder Pro
File management
An awareness of how DocBuilder Pro structures data can help you maintain the
integrity of source documents and create interim copies of work in progress. This
section describes the temporary files that DocBuilder Pro creates at various stages in
the process of imposing a document, and suggests file-management techniques you can
use to preserve your work.
integrity of source documents and create interim copies of work in progress. This
section describes the temporary files that DocBuilder Pro creates at various stages in
the process of imposing a document, and suggests file-management techniques you can
use to preserve your work.
When a workstation on the network prints a source document to the Fiery, the server
creates a spool file containing the same kind of data (PostScript or PDF) that the
workstation sent. The spool file simply records (for subsequent “playback” to a print
engine) the image of every page in the print job, in the order the pages are to be
printed. Unlike the source document, a spool file is quite literal in its record of the
print job—if there are duplicate pages in the print job, the associated data is duplicated
in the spool file as well. Thus, spool files tend to be significantly larger than the source
documents they represent.
creates a spool file containing the same kind of data (PostScript or PDF) that the
workstation sent. The spool file simply records (for subsequent “playback” to a print
engine) the image of every page in the print job, in the order the pages are to be
printed. Unlike the source document, a spool file is quite literal in its record of the
print job—if there are duplicate pages in the print job, the associated data is duplicated
in the spool file as well. Thus, spool files tend to be significantly larger than the source
documents they represent.
To maximize efficient use of server disk space, it is strongly recommended that spool
files not be kept on the Fiery any longer than necessary. The Command WorkStation
operator must delete spool files explicitly.
files not be kept on the Fiery any longer than necessary. The Command WorkStation
operator must delete spool files explicitly.
When you open a spool file in DocBuilder Pro, a temporary file in PDF format is
created on the Command WorkStation hard disk. A PDF spool file is simply copied to
the temporary file; however, when you open a PostScript spool file, DocBuilder Pro
writes a PDF version of the PostScript data to the temporary file. The temporary PDF
file resides on the Command WorkStation hard disk until you close or save the job.
created on the Command WorkStation hard disk. A PDF spool file is simply copied to
the temporary file; however, when you open a PostScript spool file, DocBuilder Pro
writes a PDF version of the PostScript data to the temporary file. The temporary PDF
file resides on the Command WorkStation hard disk until you close or save the job.
When you close the job, the name of the original spooled source file appears with a
new extension (.dbp) as the suggested name in the Save As dialog box. The original
PostScript or PDF remains intact even after the converted file has been edited and
saved in the Imposition window.
new extension (.dbp) as the suggested name in the Save As dialog box. The original
PostScript or PDF remains intact even after the converted file has been edited and
saved in the Imposition window.