en kb pf impproof

8/14/2019 en kb pf impproof

1/12

PuzzleFlowBy Examples

Imposition proof

2002-2008 Copyright ACCHSH

8/14/2019 en kb pf impproof

2/12

8/14/2019 en kb pf impproof

3/121

Contents

1 Imposition proof . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

1.1 Problem background . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

1.2 Solution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

1.3 What is needed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

1.4 Workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

1.5 Download section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

8/14/2019 en kb pf impproof

4/122

8/14/2019 en kb pf impproof

5/12

Imposition proof

3

Imposition proof 1

Problem background 1.1

In most types of production it is necessary to generate, print and accept ozalid just

before sending the document to final printing. It allows to verify imposition results

and minimalize costs of possible errors. This document describes an example of

the imposition workflow which supports imposition approval.

Related topics:

Splitting document pages

Detecting page content and marks

Imposition with single page documents

Personalization layers

Splitting document pages

Custom caption font

OPI Exchange

Solution 1.2

Among general modules for imposition and page geometry setup, PuzzleFlow system

provides some tools dedicated for imposition approval. Two modules are particulary useful

there. BoxImposer marks selected page boxes (MediaBox, CropBox, BleedBox, TrimBox

and ArtBox). The second one TwoSidePreview merges two sides of double sided

imposition plates into one, using specified opacity.

What is needed 1.3

Set of modules needed for imposition approval depends on specific features of the pro-

duction. To build a workflow for imposition proof we may need the following modules

(not allobligatory):

BoxImposer TwoSidePreview

8/14/2019 en kb pf impproof

6/12

Imposition proof

4

LayerManager

ColorMapper

Resampler

1.4 Workflow

Creating ozalid is as easy as inserting BoxImposer module between page geometry setup

(PageResizer, BoxResizer, PageScaler, PageOrienter an others) and Imposition module of

the workflow. BoxImposer draws rectangles around box objects of every input page. The

nice feature of this module is that each box mark can be drawn with different line type

and different spot color. Moreover, each box mark is placed on different layer (PDF 1.5

optional content).

If we use double-sided imposition template, we can also add TwoSidePreview module

after the imposition part and Resampler or ImageCompressor in order to reduce size of

the output file.

But what we want to achieve here is to generate two outputs: one for the proofer and

one for the RIP device. For the approval purposes, we need low resolution and page

geometry marking, but the final documents are supposed to have original quality, no

additional marking layers. Also spot colors added temporarily by BoxImposer should be

removed. How to make all this things?

8/14/2019 en kb pf impproof

7/12

Imposition proof

5

It is simple to make two workflows one for the proof and one for the

RIP. Here we show a bit smarter way, that don't impos documents twice.

First of all, lets split our workflow into three queues.

If your version of PuzzleFlow does not support many queues because of

dongle constraints, just create three workflows, each with one queue.

The first queue produce imposed documents with page geometry marking. BoxImposer

module must be applied to pages with the proper geometry. For sake of simplicity, lets

assume here that the page geometry correction is beyond the scope of this workflow.

The second queue takes the output of the first one and produce the proof (reduce the

resolution of images and merges two sides of double-sided plates into one). The third

one takes the output from the same place, removes additional marking layers and sends

approved files to the RIP.

The idea is to hold the jobs until the proof is accepted. The second and

the third queues expect incoming documents in the catalog pointed by first output

8/14/2019 en kb pf impproof

8/12

Imposition proof

6

folder. The same files will be used to generate the proof and final output. The

proofing queue do not delete completed jobs. The RIP queue holds all the jobs by

default. After approval, we just resume the job held on the beginning of the third

queue.

Now lets look at the details of the workflow configuration. BoxImposer module is con-

figured to draw marks around MediaBox, CropBox, BleedBox and TrimBox with default

presets. By default, marks are drawn with spot color of the same name as box object

name. There is also different default line style and color for each page mark.

The only thing we change here is Description field. The LayerManager module configu-

ration bases on these descriptions, so just for simplicity we use short names here.

In the second queue, Resampler module reduce 150dpi and higher resolution to 72dpi in

bitmap data.

8/14/2019 en kb pf impproof

9/12

Imposition proof

7

In most cases, TwoSidePreview module default configuration need not to be changed.

However, we can adjust front and back opacities, work style of the sheet and general

merging strategy.

It is not only BoxImposer that produce optional content (layers). All imposition marks

are placed on additional layer by default. Also the input document may contain its own

layers. Although the optional content is the feature of PDF 1.5, it should work fine on

older devices as well. Devices that do not support layers just flatten all the layers and

treat them as if there was only one main content. However, to avoid any compatibilityproblems, we can manage all the layers in the document using LayerManager.

LayerManager module can be configured like the following:

In this example, each layer we want to remove has its own rule with action Remove andno additional condition. The last rule contains a wildcard * instead of a real layer name

8/14/2019 en kb pf impproof

10/12

Imposition proof

8

and the action Flatten instead of Remove. Layers produced by BoxImposer are matched

by first four layers and, according to specified action, removed from the document. All

other layers, including imposition marks, are supposed to be merged to the main content.

The order of rules on the list is meaningful. For each layer in the document,

the modules takes all the rules sequentially and uses the first rule which match the

layer name. It is worthy to note that names of layers can be expressed by wildcards

and that each rule may have additional, environment-based condition.

The last but not least thing is spot color handling. If we use spot colors to draw box

marks, they still exist in the document, even after removing all the content drawn with

this these colors. The decision whether to use spot colors for marking or not, dependson specific production. If we change the configuration of the BoxImposer to draw marks

with process colors, we can omit the step of color mapping. In other case, the workflow

should involve ColorMapper module which can handle removing unwanted spot colors.

In the example above we use different layer and different spot color for

each box object marking. As mentioned above, using spot colors is optional. We

can use CMYK color instead and omit color mapping step in the third queue. Wecan also use one special marking layer instead of four.

All we have to do is to add special color names produced by BoxImposer to the list and

map all of them to None. In this particular case, CMYK components of spots can beignored.

8/14/2019 en kb pf impproof

11/12

Imposition proof

9

Download section 1.5

Download imposition proofing workflow (about 1Kb) a workflow for fully automated

imposition with two outputs. One for proofing, and the second (conditional) output forripping.

Download sample input (about 11Mb) a sample PDF input file.

Download created proof (about 11Mb) an proof generated out sample.

Download final output (about 11Mb) final output generated out of the sample.

8/14/2019 en kb pf impproof

12/12