47
Nexus 10.1 Reference Manual
Nexus RIP Activities
9
293
and (if the option is enabled) their subfolders, will be searched for
these fonts. Note that these folders may contain PostScript as
well as Truetype fonts.
If your customer provides you with PS, EPS or PDF files that don’t
contain embedded fonts, and the necessary fonts are delivered
separately, it is possible to set up a directory on the server to
store these fonts, or to copy the fonts in the default MacFonts
folder.
It may be convenient to change the default directory, or to define
more then one directory for fonts. Adding a new path is achieved
by typing the full path name in the text field area, and pressing the
Add button. The entered name will then appear in the list and be
removed from the text field. Alternatively, the browse button may
be used to locate the required folder through the Nexus Select
Remote Folder Window. The located path will appear in the text
field and can be added as above. Superfluous font folders may
be removed by selecting them in the list and pressing the remove
button.
When all necessary font folders have been added, pressing OK
will complete the process. Pressing cancel will leave the existing
list unaffected. If appropriate, fonts may be grouped into subfold-
ers within a font folder. To be accessible, the Search Subfolders
box must be checked for it. If the same font name is used in dif-
ferent subfolders, Nexus will use the first one that it finds, which
is not necessarily correct!
9.2.2 Color
• Use colors in job
A PostScript file can contain %%CustomColor comments, which
can contain a color name (e.g. PANTONE™ or other special col-
ors), including the CMYK and RGB equivalent. These CMYK val-
ues can be used by Nexus for proofing and trapping, and the
RGB equivalents are used to preview. In normal cases, this value
should be used, so the option should be enabled.
However, in some cases, users may want only values entered in
Color_Lib or User Color_Lib to be used, and would prefer to re-
ceive an error if a color is not found there, rather than using the
info enclosed in the PostScript file. In that case, the option should
be disabled.
If the option is off, the colors from the job are not used and if the
color is not available in the Color Lib it will come up as “unde-
fined”.
With the option on, the colors from the job are used if the color is
not available in the Color Lib. It will not come up as undefined.
41
294
• Fail if RGB
When this option is checked, the interpreter will fail if an RGB im-
age is detected in the Job. Currently, only RGB EPS images are
detected
• Color Mode
When creating PostScript files using Nexus PPDs, it is possible
to define the Color mode through a popup in the PPD. The PPD
option is called Colormodegroup, and shows the same options
as shown here. If however, PostScript code has to be processed
that was not printed using a Nexus PPD, when importing EPS
files into a Nexus workflow or when composite and/or mono-
chrome output is required, it may be necessary to change the
color mode in the interpreter settings.
• Preseparated:
Has to be selected when the PostScript code is known to contain
separated PostScript. Normally this is not necessary, because
this is usually reflected in the presence of comments in the file
(e.g. %% Platecolor Cyan).
• PostScript Controlled:
This is the default setting, and means that whatever color mode
is defined in the PostScript file should be used.
• Composite All Colors:
Select this when composite PostScript has to be processed to
produce all process and spot colors present in the job.
• Composite to CMYK:
Used to convert all spot colors in a composite job to process col-
ors (CMYK). This process is accomplished more efficiently
through the interpreter, than in a later stage during the proof ac-
tivity.
• Composite (Black Only):
Makes a page for every composite input page, selecting only the
black channel of any input colors. For CMYK only jobs, this is
equivalent to just printing the black plate. For jobs, containing
spot colors, it is equivalent to converting the spot colors to pro-
cess before printing just the black plate.
• Composite Monochrome:
This option must be selected to represent the composite input
data as Black only. The conversion takes the relative darkness of
the process colors into account. It emulates the behavior of a
monochrome printer or laser writer.
47
Nexus 10.1 Reference Manual
Nexus RIP Activities
9
295
• PANTONE™ Renaming
Using this options, PANTONE™ separation names can be re-
named, offering 4 possibilities: leave unchanged, change CVx to
CV, change CVx to x, or remove CVx.
• Color Management
The Color Management section in the Interpreter has been ex-
tended, offering all functionality to control color management on
import.
In the Input section, a default profile can be selected for both
RGB and CMYK. The pop-ups below allow the user to define
what profile will be used for what kind of object: For CMYK Lin-
eart and Images, you can choose between No Conversion, De-
fault Profile, Use Embedded Profile or Select Best Profile. For
RGB images and lineart, you have the same options, except for
No Conversion being replaced by Use PostScript Conversion, as
Nexus works internally in CMYK space, so RGB must always be
converted.
Select Best Profile means Nexus will use the embedded profile. If
no embedded profile is used, the Input Profile will be used.
For CMYK Lineart, some specific settings can be made. Of
course, if CMYK Lineart is set to No Conversion, the additional
options are redundant, and will be gray.
You can define how to handle specific types of colors:
•Single Separation Colors: colors having a non-zero value only
in one channel
•Blacks: single separation colors having the non-zero value in
the black separation and Rich blacks, having 100% value for K,
regardless of the value for CMY
•Mixed Colors: colors having a non-zero value for 2 or more
channels).
For every of these colors, you can choose between Apply profile,
Preserve Solids (i.e. not changing the values of solid colors,
whereas solids are colors whose channels are all either zero,
overprint or 100%), or Preserve All, meaning no color manage-
ment will be applied.
In the Output section, the working space can be defined, and the
rendering intent.
9.2.3 Page
• Keep Orientation
The required page orientation is normally specified in the Bander,
Proofer or Separation activities, depending on the requirements
for viewing PSTIs and outputting to the different proofers and im-
age- or platesetters.
42
296
When printing landscape from some applications, the rotation
may be performed by swapping the page dimensions and rotat-
ing all the objects in PostScript. In this case the output will be per-
formed as requested. But if the page rotation is requested using
the orientation parameters in the setpagedevice or set-
pageparams, it will be undone by the interpreter by default.
Checking the Keep Orientation check box will keep this orienta-
tion anyway.
• Set default PS Page Size from %%BoundingBox comment
If switched on, this option allows to use the page size defined in
the %%SetBoundingBox command in the PS file. The option was
added to make it possible to deal with the 0.01% of files from
strange applications that don’t use the setpage command.
• Default Page width and Default Page height
The default page dimensions for the interpreter are rarely re-
quired, because PostScript almost invariably contains a page
size definition. If in a special case, no such definition is available
in the PostScript file, the default size will be used as defined here.
Depending on the preferences settings, it will be shown in inches
or millimeters.
• Slug Params...
NexusRIP has the ability to add slug lines to files on a per-work-
flow basis. The slugs are generated by the Interpreter activity,
and will apply to all downstream outputs.
Typical information contained in a slug line includes job name,
page, separation name, user information, resolution, screen rul-
ing, dot shape, angle family, etc....
A number of formatting options are available to determine how
the slug line has to appear on the file. Note that the slug is phys-
ically added to the file at the time of Interpreting the data, e.g. if a
Make Separation activity is retried with different parameters,
these new parameters will not be included in the slug line.
In essence, the facility involves adding a number of new proper-
ties to a slug record in the interpreter activity. A special patch file
in the RIP (./Nexus/Options/02setpagedevice.ini) checks if any of
these properties are defined and, if they are, makes the required
changes to the page. Some changes, such as margins, affect the
page size and image orientation, whereas others simply add in-
formation to the page.
The Slug Parameters window is opened by pressing the Slug
Params... button in the Interpreter window.
43
Nexus 10.1 Reference Manual
Nexus RIP Activities
9
297
• Load, Save, Defaults
The settings of the Slug Parameters can be saved and loaded,
using the Save and Load buttons. This allows to store your Slug
Parameters and bring them from one system to another, etc. De-
fault resets all changes.
• Left Margin, Right Margin, Top Margin, Bottom Margin
These enable each edge of the image to be extended indepen-
dently in current preference units (e.g. inches). This may be re-
quired to provide space for slug data, or just to ensure that
images are separated on film. Margins may be defined even
when no other marks are put on the film.
• Scale Factor Width, Height
Scaling distortion may be applied to a page independently in
height and width. This scaling will also be applied to margins and
any slug marks put on the page.
• Add Crop Marks, Add Register Marks
These may be added if required by checking the corresponding
boxes. They are based on the style used by QuarkXPress, but
Line Width in points may be controlled. For crop marks to show
on output, sufficiently wide margins must be specified.
• Rotate 90 degrees, Mirror
Page rotation and mirroring are typically defined in the printing
application or within the workflow. However, if this is not possible
or convenient, these transformations can be done as part of this
facility.
• Show as metric
If this box is checked, slug parameters (e.g. page size) can be
output in either metric or imperial units. Note that this is not de-
termined automatically by the preference units and appropriate
labels (e.g. lpcm) must also be specified.
• Job/Page/Separation
Information relating to the job will be shown in the top margin if
this box is checked. Each item of information may be prefixed
with a defined prefix label. If the box is unchecked, the prefix
fields will be invisible. This also applies to other items of informa-
tion.
Where composite output is created, separation information will
be superimposed. All slug text will be output in the defined Font
and Size and at the defined offsets (see below).
31
298
• User Information, Creation Date
If these boxes are checked, Page Size, User ID (if known) and
Creation Date will be output in the left margin with the defined
prefixes.
• RIP Resolution, Output Resolution
If these boxes are checked, resolution values will be shown in the
right margin with the specified prefixes and suffixes. The RIP (i.e.
interpreter) resolution will always be known, but the output reso-
lution will only be available if the Assembler resolution field is un-
locked in the workflow and a PPD option has been made. Unless
this is done, the interpreter will have no access to this property.
The same suffix is used for both types of resolution.
• Screen Ruling, Dot Shape, Angle Family
If a single screen ruling has been defined for a job, and was set
as a PPD option, this may be shown in the right margin with the
specified prefix and suffix. This option is not available when using
object screening, nor if the ruling was locked in the workflow such
that no PPD option was generated. The same constraints apply
to the output of dot shape and angle family. If these parameters
are not available in the PostScript environment they will not be
shown, nor will the prefix labels.
• PostScript Font, Size (points)
All slug text will be output in the specified font at the specified
size. The font must be available and would typically be Courier or
Helvetica. If no slug text is defined, these fields will be disabled.
• Baseline Shift, Indent
These values (in preference units) define the start position within
the appropriate margin for the start of the text. Positive value
would normally be specified so that all text will fall in the defined
margins. Negative values will place text within the page.
30
Nexus 10.1 Reference Manual
Nexus RIP Activities
9
299
• EXAMPLE:
The example below shows a composite PDF output with slug
lines applied. Crop Marks and Register Marks have been added
as well as Creation date, document size and output resolution.
Separation names are overlapping.
9.2.4 Links
• Fail if missing links
When running jobs on an imposition workflow, or on any other
workflow, using link files, it is necessary to locate the already pro-
cessed files from which the link file has been derived. If the fail if
missing link box is checked, and the page referenced in the link
file cannot be found, the interpreter will fail. The PostScript file will
be processed completely however, to ensure that the full list of
missing pages will be displayed on the job error window.
If this option is left unchecked (not recommended), the job will
run, but pages referenced by link files will not be included. In the
job list, a warning will be generated next to the job, but disabling
this option should only be used for test purposes.
• Support static links
Link files (created by any of the Page workflows) contain the full
path of the target page file (which can be OPPO, PSTI or TIFF for-
mat). When processing a job containing one of those links (typi-
cally in an Impo workflow), Nexus would only use the end of the
path (i.e. the filename) and use it in any of the paths defined in the
Interpreter Page Paths if there are any. The first match found this
way, is the one that will be used.
44
300
If no match is found, Nexus can use the full path defined in the
link file (the so called Static Link). If this path is valid and points to
a file, and the Support Static Links option is on, this file will be
used.
If the path does not point to a valid file, an error or warning will be
generated. This option should be switched off to make sure that
only files from the Page paths are used, and an error is generated
if the page files cannot be found there.
• Page paths...
The ripped files, generated through the various page workflows
are stored in one or more page folders, as specified in the re-
spective page workflows and their destination paths. When pro-
cessing imposition and Step and Repeat jobs, containing link
files, the matching pages have to be found. The different page di-
rectories that may have been defined for the interpreter must be
defined through the page paths. The page paths button opens
the Page Search Paths window as shown here. This window be-
haves in exactly the same way as the Font Search Paths window
described earlier. New paths may be added explicitly by typing
them in the text field and pushing the Add button. Browsing to an
existing folder and selecting it may be easier. Afterwards, folders
may be removed or defined as hierarchical. If the checkbox in
front of a path is on, its subfolders will be searched as well.
The default search directory is the Pages folder, automatically
created in the NexusRip folder. For example: D:/Intel_Mac/Pag-
es.
9.2.5 PDF
• Enable PDF Flattener
If this option is on, a 1.4 or 1.5 PDF file will be flattened into a PDF
1.3 file first, before being processed by the interpreter. The inter-
preter automatically takes the optimal parameters to flatten the
PDF 1.4 or 1.5 file.
• Fail If Unimplemented PDF features
If the Interpreter encounters a PDF file containing unimplemented
features, the workflow will fail if this option is switched on.
• PDF overprints
If overprints are used in PDF documents the display in Acrobat
can look different to the output from the RIP. This popup provides
some control over PDF overprints in Nexus.
• Standard:
Uses overprints as they are intended. Even if the overprints are
not shown correctly in Acrobat, the PDF will be separated cor-
rectly by Nexus.
Documents you may be interested
Documents you may be interested
