17.05.2014 Views

PDFlib 8 Windows COM/.NET Tutorial

PDFlib 8 Windows COM/.NET Tutorial

PDFlib 8 Windows COM/.NET Tutorial

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Cookbook A full code sample can be found in the Cookbook topic color/color_gradient.<br />

3.5.2 Pantone, HKS, and custom Spot Colors<br />

<strong>PDFlib</strong> supports spot colors (technically known as Separation color space in PDF, although<br />

the term separation is generally used with process colors, too) which can be<br />

used to print custom colors outside the range of colors mixed from process colors. Spot<br />

colors are specified by name, and in PDF are always accompanied by an alternate color<br />

which closely, but not exactly, resembles the spot color. Acrobat will use the alternate<br />

color for screen display and printing to devices which do not support spot colors (such<br />

as office printers). On the printing press the requested spot color will be applied in addition<br />

to any process colors which may be used in the document. This requires the PDF<br />

files to be post-processed by a process called color separation.<br />

<strong>PDFlib</strong> supports various built-in spot color libraries as well as custom (user-defined)<br />

spot colors. When a spot color name is requested with makespotcolor( ) <strong>PDFlib</strong> will first<br />

check whether the requested spot color can be found in one of its built-in libraries. If so,<br />

<strong>PDFlib</strong> will use built-in values for the alternate color. Otherwise the spot color is assumed<br />

to be a user-defined color, and the client must supply appropriate alternate color<br />

values (via the current color). Spot colors can be tinted, i.e., they can be used with a<br />

percentage between 0 and 1.<br />

By default, built-in spot colors can not be redefined with custom alternate values.<br />

However, this behavior can be changed with the spotcolorlookup parameter. This can be<br />

useful to achieve compatibility with older applications which may use different color<br />

definitions, and for workflows which cannot deal with <strong>PDFlib</strong>’s Lab alternate values for<br />

PANTONE colors.<br />

<strong>PDFlib</strong> will automatically generate suitable alternate colors for built-in spot colors<br />

when a PDF/X or PDF/A conformance level has been selected (see Section 10.3, »PDF/X<br />

for Print Production«, page 253). For custom spot colors it is the user’s responsibility to<br />

provide alternate colors which are compatible with the selected PDF/X or PDF/A conformance<br />

level.<br />

Note Built-in spot color data and the corresponding trademarks have been licensed by <strong>PDFlib</strong> GmbH<br />

from the respective trademark owners for use in <strong>PDFlib</strong> software.<br />

Cookbook A full code sample can be found in the Cookbook topic color/spot_color.<br />

PANTONE® colors. PANTONE colors are well-known and<br />

widely used on a world-wide basis. <strong>PDFlib</strong> fully supports the<br />

Pantone Matching System® (totalling ca. 26 000 swatches),<br />

plus the Pantone® Goe System which was introduced in<br />

2008 with 2058 additional colors in coated/uncoated variants.<br />

All color swatch names from the digital color libraries<br />

listed in Table 3.4 can be used. Commercial <strong>PDFlib</strong> customers<br />

can request a text file with the full list of PANTONE spot color<br />

names from our support.<br />

Spot color names are case-sensitive; use uppercase as shown in the examples. Old<br />

color name prefixes CV, CVV, CVU, CVC, and CVP will also be accepted, and changed to<br />

the corresponding new color names unless the preserveoldpantonenames parameter is<br />

true. The PANTONE prefix must always be provided in the swatch name as shown in the<br />

3.5 Working with Color 81

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!