EMC ® Document Sciences ®
xPression ®
Version 4.5 SP1
xPublish Output Processing Guide
EMC Corporation
Corporate Headquarters
Hopkinton, MA 01748-9103
1-508-435-1000
www.EMC.com
Legal Notice
Copyright © 2003-2015 EMC Corporation. All Rights Reserved.
EMC believes the information in this publication is accurate as of its publication date. The information is subject to change
without notice.
THE INFORMATION IN THIS PUBLICATION IS PROVIDED “AS IS.” EMC CORPORATION MAKES NO REPRESENTATIONS
OR WARRANTIES OF ANY KIND WITH RESPECT TO THE INFORMATION IN THIS PUBLICATION, AND SPECIFICALLY
DISCLAIMS IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Use, copying, and distribution of any EMC software described in this publication requires an applicable software license.
For the most up-to-date listing of EMC product names, see EMC Corporation Trademarks on EMC.com. Adobe and Adobe PDF
Library are trademarks or registered trademarks of Adobe Systems Inc. in the U.S. and other countries. All other trademarks
used herein are the property of their respective owners.
Documentation Feedback
Your opinion matters. We want to hear from you regarding our product documentation. If you have feedback
about how we can make our documentation better or easier to use, please send us your feedback directly at
[email protected]
Table of Contents
Revision History
Chapter 1
Chapter 2
..................................................................................................................
Introduction
9
................................................................................................. 11
Information Boxes ............................................................................................
11
xPressionHome ................................................................................................
11
EMC Document Sciences Technical Support .......................................................
11
Images
......................................................................................................... 13
Bit Depth .........................................................................................................
Black and White ...........................................................................................
Diffusion Dither Pattern ............................................................................
Halftone Screen ........................................................................................
Grayscale .....................................................................................................
Indexed Color ..............................................................................................
RGB .............................................................................................................
CMYK .........................................................................................................
RGB vs CMYK..............................................................................................
Spot Colors and Highlight Color....................................................................
13
13
14
14
14
14
14
15
15
15
Advanced Features ...........................................................................................
Transparency ...............................................................................................
Clipping Path ...........................................................................................
Transparent Pixels ....................................................................................
Translucency ................................................................................................
Color Management .......................................................................................
Vector Graphics ............................................................................................
Metafile Formats ..........................................................................................
Reproducing Images on Digital Devices .............................................................
How Printers Work .......................................................................................
PDF .........................................................................................................
Halftone Screens ...........................................................................................
16
16
16
16
16
16
17
17
17
17
19
19
Optimizing Images for Your Printing Process .....................................................
File Size and Performance .............................................................................
Bit Depth .....................................................................................................
Image Size....................................................................................................
Cropping Images ......................................................................................
Compression ................................................................................................
Lossless Compression ...............................................................................
Lossy Compression...................................................................................
Right Sizing Files ..........................................................................................
Resampling Images ......................................................................................
Maintaining Consistent Color ........................................................................
Suggestions for Resolution ............................................................................
Scanned Images ............................................................................................
20
21
21
21
22
22
22
23
23
23
24
24
25
Choosing Which Image Format to Use ...............................................................
Supported Image Types ................................................................................
25
25
3
Table of Contents
Chapter 3
4
Some Unsupported Image Types ...................................................................
Image Support vs Feature Support.................................................................
Transparency Support ...............................................................................
PDL Native Support .....................................................................................
PCL .........................................................................................................
xPresso for Adobe InDesign Images ...............................................................
Storing Images in the xPression Repository ....................................................
Images by Application ..................................................................................
Use G4 TIFF for Monochrome Images ............................................................
PDF Images ..................................................................................................
JPEG Images ................................................................................................
JPEGs in AFP and PostScript Output..........................................................
Inline JPEGs in AFP Output ......................................................................
JPEG Rendered in CMYK ..........................................................................
TIFF Images .................................................................................................
EPS Images ..................................................................................................
ICC Color Profile Support .............................................................................
26
27
27
28
29
29
29
31
32
32
33
33
33
34
34
35
35
Picking the Right Format for the PDL.................................................................
How xPression Decides Which Format to Use ................................................
Image Type Limitations ................................................................................
How xPression Determines the Image DPI .....................................................
How to Customize the Image Format Selection ...............................................
Customizing Image Format Selection .........................................................
Customizing Output Stream Image Format Selection ..................................
General Image Type Recommendations for Your PDL .....................................
Bar Code Images ..........................................................................................
36
36
37
37
37
38
38
40
40
Images in xPresso Documents ...........................................................................
Embedding Images .......................................................................................
External Images ............................................................................................
Structuring Relative External Image References ..........................................
Working with Images in Your Document ........................................................
Scaling Images .........................................................................................
Transparency and Opacity in InDesign.......................................................
How xPression Handles Images ........................................................................
The xAdmin Image Utility.............................................................................
Importing an Image to the Image Management Utility ................................
Images in Your xDesign Documents ...............................................................
Images in Your xPresso Documents ...............................................................
Printer Resident Images ................................................................................
Image Optimization in AFP Output ...............................................................
Going into Production ......................................................................................
41
41
41
42
42
42
43
44
44
46
46
46
47
47
48
Using Fonts .................................................................................................
Anatomy of a Font ............................................................................................
Glyphs .........................................................................................................
Font Metrics .................................................................................................
Encoding .........................................................................................................
Single Byte and Double Byte .........................................................................
WINANSI ....................................................................................................
Unicode .......................................................................................................
49
49
49
49
50
50
50
52
Font Formats ....................................................................................................
Adobe Type 1 ...............................................................................................
Issues with Type 1 Fonts ...........................................................................
TrueType (.TTF) ............................................................................................
OpenType ....................................................................................................
AFP Fonts ....................................................................................................
52
53
53
53
54
54
Table of Contents
Chapter 4
Using Fonts ......................................................................................................
Embedding Fonts .........................................................................................
Printer Resident Fonts ...................................................................................
Subsetting ....................................................................................................
User-Created Fonts .......................................................................................
54
55
55
56
56
How xPression Handles Fonts ...........................................................................
The Font Management Utility ........................................................................
Large Character Fonts ...................................................................................
Asian Typography Support .......................................................................
Fonts in Your xDesign Documents .................................................................
Fonts in Your xPresso Documents ..................................................................
Migrating Fonts ............................................................................................
56
57
58
58
59
59
59
Fonts and Page Description Languages ..............................................................
Using Fonts in PostScript Output ...................................................................
Emitter Support ........................................................................................
Force the Use of Type 1 Fonts ....................................................................
Converting TTF and OTF Fonts to Type 1 ...................................................
Using Fonts in PDF Output ...........................................................................
Embedding Fonts in xPublish ....................................................................
Using Fonts in AFP Output ...........................................................................
TrueType Fonts in AFP .............................................................................
Manually Converting TrueType to AFP Outline ..........................................
Bullet Characters ......................................................................................
AFP Foreign Language Support.................................................................
Thai Fonts in AFP Output .....................................................................
Emitter Support ........................................................................................
Converting Type 1 Fonts into AFP Outline Fonts ........................................
Creating AFP Files that Do Not Embed Fonts .............................................
Using Fonts in PCL Output ...........................................................................
Emitter Support ........................................................................................
Using PCL Fonts with xPression ...............................................................
Convert TrueType Fonts to PCL .............................................................
Configuring the PCLFontMapping Property...........................................
Parameters .......................................................................................
60
60
60
60
61
62
62
63
64
65
65
65
66
67
67
68
68
69
70
70
71
71
Fonts and Data Driven Graphics ........................................................................
Converting Fonts to FSD Format....................................................................
71
72
Page Description Languages ......................................................................
AFP .................................................................................................................
AFP Foreign Language Support.....................................................................
Images .........................................................................................................
Images on the Server .................................................................................
JPEG Images ............................................................................................
xPresso for Adobe InDesign Image Fit Options ...........................................
CMYK Images ..........................................................................................
Building TLE Items .......................................................................................
AFP PPD Files ..............................................................................................
Reverse Printing ...........................................................................................
Rotating Pages..............................................................................................
Resource IDs ...............................................................................................
Limitations...............................................................................................
Mixed Orientation AFP Output ....................................................................
Limitations...............................................................................................
Rotated Frames in AFP Output ......................................................................
75
75
76
76
77
77
77
77
77
78
78
78
78
79
79
80
80
HTML .............................................................................................................
80
PCL .................................................................................................................
80
5
Table of Contents
Chapter 5
6
PCL Font Support .........................................................................................
Images in PCL ..............................................................................................
PCL PPD Files ..............................................................................................
81
81
82
PDF .................................................................................................................
Using PDF in xPression ................................................................................
Fonts in PDF ................................................................................................
Embedding Fonts in xPublish ....................................................................
Images in PDF ..............................................................................................
ICC Color Profiles.....................................................................................
Reverse Printing ...........................................................................................
Rotating Pages 180 Degrees ...........................................................................
82
83
83
83
84
84
84
84
PostScript .........................................................................................................
PostScript PPD Files......................................................................................
Reverse Printing ...........................................................................................
Rotating Pages 180 Degrees ...........................................................................
Images in PostScript .....................................................................................
84
85
85
85
85
PPML ..............................................................................................................
86
Text .................................................................................................................
86
TIFF .................................................................................................................
86
......................................................................................................
Adobe Type 1 Fonts ..........................................................................................
Bit Depth .........................................................................................................
Embedding ......................................................................................................
Encoding .........................................................................................................
Font Metrics .....................................................................................................
Glyphs .............................................................................................................
ICC Color Profiles.............................................................................................
Kerning ...........................................................................................................
Lossless Compression .......................................................................................
Lossy Compression...........................................................................................
Page Description Language (PDL) .....................................................................
Pixels ...............................................................................................................
Resolution ........................................................................................................
Spot Color ........................................................................................................
Subsetting ........................................................................................................
Unicode ...........................................................................................................
WINANSI ........................................................................................................
89
Glossary
89
89
89
89
90
90
90
90
90
91
91
91
91
91
92
92
92
Table of Contents
List of Tables
7
Table of Contents
8
Revision History
Revision Date
Description
August, 2015
Updated TIFF Images, page 34.
June, 2014
Initial publication
9
Preface
10
Chapter 1
Introduction
This guide provides in-depth information about managing fonts and images in the xPression output
processing system. Some information relates to specific versions of the server and may not apply
to all versions.
Information Boxes
The following colored boxes alert you to special information in the documentation.
Caution: The caution box warns you that a fatal error, unsatisfactory output, or loss of data may
occur if you do not follow the directions carefully.
Tip: A tip offers suggestions to simplify a task or describes a useful shortcut. They may also describe
an alternate way to use the techniques described in the text.
Note: A note offers information that emphasizes or supplements important points of the main text.
xPressionHome
The term “xPressionHome” refers to the location where xPression was installed on your server. By
default on Windows servers, the location is C:\xPression, but your installer may have selected
a different location during installation. Please consult with your administrators or IT personnel to
determine the location where they installed xPression. Throughout the xPression documentation, we
will refer to this location as “xPressionHome”.
EMC Document Sciences Technical Support
For more information or to solve a problem, you can contact EMC Document Sciences Technical
Support in one of the following ways:
Online Support: https://support.emc.com
Telephone Support:
11
Introduction
United States: 800-782-4362
Canada: 800-543-4782
Worldwide: +1-508-497-7901
For additional worldwide access numbers, visit:
http://www.emc.com/collateral/contact-us/h4165-csc-phonelist-ho.pdf
12
Chapter 2
Images
The simplest definition of a digital image is that it is a rectangular array of pixels. The pixel is the
smallest and most basic unit of a digital image. Think of a piece of graph paper, where each square
can be a color. A pixel plays the same role in a digital image.
When images are represented on an imaging device at a particular size, they acquire resolution. The
resolution of an image is the number of pixels per unit measure when displayed on a particular
imaging device.
For example, if you display a 100 x 100 pixel image at a size of 1” by 1”, the image resolution would be
100 DPI (dots per inch). The same image could be scaled to 2"x2" and would then have the resolution
of 50 DPI. Notice that the image itself does not have resolution, it only acquires resolution when
displayed at a particular size. Some image formats include the image size in their definition, but this
concept is artificial and exists only because it is convenient for many applications.
Digital images are represented as raster images or vector graphics. Raster graphics represent images
as a collection of pixels. Vector graphics use a series of drawing commands in a page description
language designed to draw the graphic at the resolution of the output device.
Bit Depth
If a pixel is a square on a piece of graph paper (that represents your image) then Bit Depth, page 13 is
the number of colors you can use to fill that square. With a binary image (1-bit per pixel), you have
only one color - black (the paper is white). With a CMYK image (32-bit per pixel), you can use
up to 4,294,967,296 different colors.
Black and White
The smallest type of image is the binary image where one bit is used to represent each pixel. With this
type of image, photographic gray tones can be reproduced using several methods.
13
Images
Diffusion Dither Pattern
Dithering scatters different colored pixels in an image to make it appear as though there are
intermediate colors in images with a limited color palette.
Halftone Screen
The more common way to represent shades of gray in a black and white raster format is the halftone
screen. Halftone is a technique that simulates continuous tone imagery through the use of equally
spaced dots of varying size. This image has been reproduced using a halftone screen.
Grayscale
Grayscale images are composed exclusively of shades of neutral gray, varying from black at the
weakest intensity to white at the strongest. Grayscale images use 8-bits per pixel. Each pixel is
defined as a black value between 0 and 255. Grayscale images are distinct from black-and-white
images in that they have many shades of gray in between black and white.
Indexed Color
Indexed color also uses only 8-bits per pixel, but adds color. Indexed color works by creating a palette
of colors (256) and only using those colors in the image.
When creating indexed color, the palette (the complete set of colors available) determines the color
fidelity. Programs that create indexed color files can either use a standard palette (like the standard
256 color palette used by Windows) or an adaptive palette. To create an adaptive palette you must use
a program that analyzes the colors in the image and picks the 256 that will best represent the image.
In all indexed color images, the original RGB or CMYK values are replaced by the closest palette value
using dithering when necessary. Indexed color files can be grayscale, RGB or CMYK depending upon
what values are in the palette. Successful use of indexed color depends upon the use of color in the
image and the skill of the developer who created the algorithm for picking the palette of colors to use.
RGB
The RGB color model is native to devices like televisions and computer monitors. It is called the
Additive model, because you start out with black, and if you add 100% of Red, Green, and Blue you
get white.
In this model, each pixel is defined by 3 8-bit quantities representing red, green, and blue. 128, 128,
128 would be a gray color. 0,0,0 would be black, and 255, 255, 255 would be white.
This is not the native color model for printing, and thus must be converted to CMYK before it can be
printed. As you will see in RGB vs CMYK, page 15, this is a highly subjective process.
14
Images
CMYK
In a CMYK image, each pixel is represented by 4 8-bit values, each representing the colors Cyan,
Magenta, Yellow and Black.
This is the native color model for printing and is used for most print applications. There are color
models with more colors that use additional colors (to more faithfully reproduce blues, flesh tones
etc.), but they are not supported by xPression. CMYK is called the subtractive color model because
the paper starts out white, and by adding transparent ink, less and less light is reflected from the
paper to your eye.
RGB vs CMYK
RGB color can reproduce basically the same range of colors as CMYK with only 75% of the data, so
why use CMYK? RGB to CMYK is more like a translation than a direct conversion. This translation is
much like translating from one language to another.
• As with language, some meaning (color) can be lost in the translation
• As with language when you translate RGB > CMYK > RGB you will not get the same value you
began with
• As with language, the translation may be different depending upon who translates it (Photoshop,
the printer, or xPression image converters)
Spot Colors and Highlight Color
Both RGB and CMYK color models use a number of colors in combination to recreate all colors.
Spot or highlight color models do not attempt to recreate all colors, instead each color is printed
with its own ink.
Spot color is used when a process color (CMYK equivalent) is not sufficient. For example, if you are
Coke, there is a specific "Coke Red" color that is required. If you are printing a color brochure, you
will use CMYK plus a spot color in "Coke Red." The spot color will only be used when printing the
logo or other things that you specifically want in that color.
Even though 5 colors are being used, the 5th color is NOT used in combination with CMYK, is used in
specific spots to provide an exact color match. It is not uncommon in high-end print applications to
use many spot colors in addition to CMYK. When generating output, each highlight or spot color is
given its own 8-bit image (256 shades).
In offset printing there are a number of ink vendors who sell specific colors of ink (For example,
Pantone and Focoltone). PMS (Pantone Matching System) colors are very commonly used as spot
color. When offset printing, you can use black plus one spot to be equivalent to digital highlight color,
also at a much lower production cost.
15
Images
Advanced Features
There are a number of advanced features that are available when reproducing images. These features
are extensions of the basic concept of an image and are not available in all client applications, print
streams or image formats. For a list of features and their support across image formats and PDLs,
see Image Support vs Feature Support, page 27.
Transparency
Image transparency is the ability to define a portion of an image so that it does not appear, allowing
the background to show. Transparency allows the background to completely show through.
Images are rectangular arrays of pixels. If your image is not rectangular, you need transparency
to avoid displaying the full rectangular image.
This feature is not supported by every image format or by every page description language.
Clipping Path
In PostScript you can define an enclosed area (a path) that will be preserved while the rest of the
image is cut off or clipped.
Transparent Pixels
Certain pixels within the image can be designated as transparent. Where these pixels appear, the
image is transparent and the background shows through.
Translucency
Translucency is where various objects can be layered using the opacity setting available in
applications like Adobe InDesign.
This feature is not supported by xPression. The reason is that this is not a natural function provided by
any print stream. The work around for this feature is to montage images in a program like Photoshop.
Color Management
Color management is the controlled conversion between the color representations of various devices
(such as digital cameras, monitors, TV screens, film printers, computer printers, and offset presses)
and corresponding media.
16
Images
The primary goal of color management is to obtain a good color match across devices such as printers
and monitors. This goal is accomplished by measuring the response of each color managed device
and compensating for its inaccuracies when displaying colors. Each managed device has an ICC
(International Color Consortium) profile that describes its response.
Vector Graphics
Vector Graphics use a series of drawing commands in a page description language to draw the
graphic. Vector graphics are always images at the resolution of the output device (for PDF, the
computer monitor). In a PDF file, you could zoom to 2000% and never see the effects of pixelization
(the ability to see stair stepping or large pixels in an image). For this reason, vector files are called
"resolution independent." The benefits of vector graphics are also apparent when printing documents
at high resolution.
Raster images have a fixed number of pixels. As you enlarge them, the pixels become larger and the
resolution (the number of pixels per unit measure) goes down. For this reason raster images are
called "resolution dependent."
CAD (Computer Aided Design) programs, Adobe Illustrator, CorelDraw and other programs can
create vector graphic files. Outline fonts are also examples of vector graphics.
Metafile Formats
Certain programs allow you to combine vector graphics and images in a single file. These formats are
called Metafile formats. The most well known are WMF (Windows Metafile), PostScript, and PDF.
Reproducing Images on Digital Devices
The majority of xPression users produce electronic documents or documents for print on digital
printers. This section will discuss the issues related to maintaining the balance between production
efficiency and image quality for these devices.
How Printers Work
In this section, we will walk through the process that illustrates how printers receive, process, and
produce xPression documents.
First, xPression produces an output file in one of several page description languages (PDLs) such as
PDF, PostScript, AFP, or PCL. The file is sent to the printer through a batch or transactional process.
These files are then converted into binary images at the device resolution for each color to be printed.
This process is called rasterization. In PostScript, this process is performed by the RIP (Raster Image
17
Images
Processor). The rasterization or RIP process merges all images, vector graphics, and text into a single
image that can be fed to the marking engine.
For example, if you have a 600 DPI Black and white printer, the result of the RIP process is a 1-bit
image at 600 DPI. For a full color printer, it would be 4 1-bit images corresponding to C, M, Y, and K
marking engines. Next, the file is rasterized.
This image is transferred to the marking engine. In a laser printer, a laser aimed at a photo-sensitive
drum writes the image onto the drum of the printer. Each pixel is reproduce by having a laser shine
or not shine at a point on the drum. This changes the magnetic qualities of the drum. As the drum
turns it picks up magnetized plastic powder called toner.
Paper is charged with a reverse polarity so that it attracts the powder, and the paper passes by the
drum magnetically transferring the toner to the paper. The paper is then heated to a very high
temperature in a fusing unit to melt the toner onto the paper.
18
Images
PDF
PDF is viewed using Adobe Acrobat. Acrobat is an RGB RIP. It takes PDF files, which are in a metafile
format, rasterizes them to screen resolution in RGB, and displays them on your monitor. When
printing from Acrobat, the print driver converts the PDF into a PDL appropriate for your printer.
Halftone Screens
On most digital print devices, each color is defined by a 1-bit image. As a result, the image can
only contain ink or not contain ink.
19
Images
In order to simulated shades of gray, a process called halftoning or screening is
used.
The device pixels are divided into halftone cells, and some number of those pixels are colored to
approximate tints of the color being imaged.
In the sample above, the halftone cell is 8x8 pixels (64 total pixels). The cell on in the lower left hand
corner has 32 pixels colored black and is representing 50% black. Because there are 64 total pixels, this
scenario can only represent 64 shades of gray.
The following list contains tips for using halftone screens:
• When producing a screened photographic image, the effective resolution can be no higher than
the screen frequency (typically between 60 and 130 lines per inch (LPI)) as a halftone cell can
represent only one pixel of an image.
• The number of colors that can be represented in a halftoned image are directly related to the
LPI of the screens used to reproduce them.
• The higher the LPI of the screen, the smaller the halftone cell in device pixels, and the fewer the
shades of gray that can be reproduced.
• Despite the fact that we save images with 256 colors or gray shades, digital printing can not
reproduce 256 shades of any color because of limits imposed by screens and by the devices
themselves.
Optimizing Images for Your Printing Process
By default, xPression does a great job of optimizing the performance and quality of images used in
documents. In general, you don’t have to think too much about how they function, they just work.
There are particular jobs and particular images that require fine tuning. Usually, there are two major
issues to consider: File size and image quality. Larger file sizes do not always equate to better quality.
This section will focus on how to optimize file size for performance and quality.
20
Images
File Size and Performance
In PDL files, the image is usually the largest component and contributes most to the file size. Images
slow down every document creation and management process:
• Creating the PDL file (xPublish)
• Storage of the files (Network disk space)
• Spooling (Network bandwidth and maybe making another copy of the big files)
• Processing at the Printer (Printer or server in front of the printer)
• Archiving output (Archive system)
• Retrieval of archive output (Viewer)
In most workflows, large image file sizes affect performance in many different areas for each output
file. If you are using many images, it makes sense to attempt to optimize them.
In general, handling large images will hurt the performance of any digital system, so it is always
in the interest of users to ensure your images are detailed enough to be good quality, and compact
enough to lessen the impact on performance. There are three major things that effect image file
size: Bit depth, image size, and compression.
Bit Depth
Bit depth effects file size in a linear way. For example:
Binary (1-bit per pixel) = 1 MB
Grayscale or indexed color (8-bit per pixel) = 8 MB
RGB Color Image (24-bit per pixel) = 24 MB
CMYK Color image (32-bit per pixel) = 32 MB
As the bit depth is increased, the size of the file also increases based on the number of bits per pixel.
Image Size
Image size effects the file size in a non-linear way. For example, if you had a binary image sized to
8.5” x 11” at 300 DPI, the total number of pixels can be calculated as follows:
8.5 x 11 x 300 x 300 = 1.05 MB
If we double the resolution we make the file four times bigger.
8.5 x 11 x 600 x 600 = 4.02 MB
21
Images
Cropping Images
One way to reduce image file size is to ensure that the image is cropped tightly. This also ensures that
the image is not larger than expected when used in a document. In some cases (such as with a scanned
image), there may be a lot of extra white space around the actual image that doesn’t need to be
included. Cropping the image ensures that only the necessary image data is included in the image file.
Compression
Compression has both performance advantages and disadvantages. It can dramatically reduce file
sizes, but also requires more processing time to perform compression and decompression.
With xPression, we have optimized compression and decompression so that in most cases the
performance benefits of compression outweigh the processing time required. There are two basic
types of image compression: Lossless and Lossy.
Lossless Compression
Lossless compression refers to compression techniques in which no data is lost. The PKZIP, ZIP, and
TAR compression technologies are example of lossless compression. For most types of data, lossless
compression techniques can reduce the space needed by only about 50%. These compression schemes
encode redundant data with a description of that data. For example:
000000000000000000000000000000000000000000000
Lossless compression can compress this redundant string in this way: 32 zeros
When Lossless compression decompress the string, it is reproduced exactly. If you think of images
like faxed documents, there is a lot of white area that will compress very well. If you try the same
thing with the following string, you will notice that compression is not as effective:
010101010101010101010101010101010101010101010
In fact, when compressing non-repetitive data, file sizes can actually be larger after compression
than before.
22
Images
Lossy Compression
Refers to data compression techniques in which some amount of data is lost. Lossy compression
technologies attempt to eliminate redundant or unnecessary information. When you compress and
decompress data with lossy compression, you may retrieve data that is different from the original,
but close enough to be useful in some way.
Lossy compression is most commonly used to compress multimedia data (MP3, video, JPEG). While
you lose data, the benefits to file size are substantial.
Lossy compression is most effective on photographic images, but the loss of quality may be more
noticeable when trying to produce line art and text.
Right Sizing Files
The general procedure for handling performance issues is to build the system as quickly and
efficiently as possible, then test the performance. If the performance is not sufficient, you can look for
ways to improve it. This is the case when dealing with images in xPression.
However you must also consider the scale and lifetime impact of a job. If the job is large in scale or
long in duration, a few excessively large images could have a very high lifetime impact and should be
dealt with despite the fact that they meet initial performance requirements.
Resampling Images
xPublish has the ability to resample images to a lower resolution, which results in smaller file sizes.
Resampling is done at the Output Definition level. You can resample images for AFP, PostScript,
PDF, and TIFF Output Definitions.
Output Definitions are one of the three components that make up an output stream. By resampling
images in your Output Definition, you can control which documents are affected by creating multiple
streams. The primary use case for this feature is that it allows you to build a document for output in
high-resolution print (300-600 DPI) and then create a stream for PDF that is at a lower resolution (for
example, 96 DPI). This dramatically decreases file sizes for PDF. The downside is that image quality
and color fidelity may suffer. Use this feature with caution.
Additionally, ICC profiles are not honored when the image is resampled. Do not use resampling with
images that use ICC profiles. For more information, see Color Management, page 16.
23
Images
Maintaining Consistent Color
The biggest problem in maintaining consistent color is the subjective nature of the conversion
between RGB and CMYK color. This will not be an issue for most images, but if high-fidelity color
is needed, follow these suggestions:
• Use only RGB or only CMYK color. By eliminating this conversion, you ensure the colors will
always be consistent.
• Always include images that can be handled natively by the PDL. If you start with the image type
that is native to your PDL, that image type will be available when producing your documents.
This ensures your colors remain consistent because there is no need for xPression to do an
automatic conversion of your images.
• ICC profiles are only honored in certain situations. For more information, see ICC Color Profile
Support, page 35.
• Do not use the resampling feature if you are using images with ICC profiles, they will not be
honored.
Suggestions for Resolution
Image resolution is usually the first setting to adjust when tuning for performance. As a general
guideline, the resolution for photographic images usually never needs to be more than 200 DPI. To
determine an acceptable resolution for your images, print a representative image at 100, 125, 150,
175, 200, 225, and 250 DPI. Compare the images and choose the lowest resolution that meets your
requirements.
In many instances, it can be hard to tell the difference between images above 125 DPI. However, this
will be different for different types of images. For example, if you are reproducing images that
contain text and line-art, the resolution will need to be higher, but typically the bit depth can be
lower. For these files your test can range from 175 DPI to 400 DPI or higher depending the quality of
your printing process.
Recommended DPI for color images (not line art) are as follows:
• 150 DPI Acceptable Quality
• 200 DPI Good Quality
• 250 DPI Better Quality
• 300 DPI Best Quality
• 300–600 DPI only for very high-end offset and laser printing processes
Recommended DPI for line art (scans of text, very fine line art) are as follows:
• 150 DPI Fax Quality
• 200 DPI Good Quality
• 250 DPI Better Quality
• 300 DPI Very Good Quality
• 300–600 DPI High-end Quality
24
Images
Scanned Images
A common practice for getting images into digital form for publishing is to scan them. When you
scan images, it is important to consider the following:
• Scanned image DPI doesn’t have to equal the printer DPI. This can result in images that are much
larger than necessary. For example, if your printer DPI is 1200, you should still scan images in
at no more than 300 DPI (or the lowest DPI that gives the required quality). If you scan all the
images in at 1200 DPI, that is 800 DPI more information contained in each image than is most
likely necessary to get quality output.
• Images should be scanned at the DPI required for the output. Lower DPI images can’t be resized
later to work for a higher DPI output. Resizing a 72 DPI image to 300 DPI will not improve the
lack of detail in the edges of the image that appears in the 72 DPI image.
• If the image is to be used in print output, don’t scan the image at 72–96 DPI. This DPI range
doesn’t have enough resolution to create acceptable print output.
• If an image is to be used in print and archive output, scan the image at the acceptable print DPI,
then save a lower resolution copy of the image for the archive output.
Choosing Which Image Format to Use
As we have learned, all images are rectangular arrays of pixels. Why should there be more than one
file format for storing them? Different formats are better for different types of images, and also for
different types of output devices. As a result, we have to perform a multi-dimensional analysis to
resolve the issue.
When deciding what image format to use in your xPression documents, consider each output type
that may be created with the document. Choosing an image format that is supported for each of
the required output types is a good idea. For example, JPEG images are supported for almost all
xPression output types, so it’s a good choice for documents that will be output in several formats.
Supported Image Types
There are many things to consider when it comes to using images in your documents. Before you
make any decisions, it is important to know what image formats the xPression Publish publishing
engine supports for each output format.
If the output format doesn’t support an image format, xPression will attempt to convert it to a
supported format. For more information, see Picking the Right Format for the PDL, page 36. When
talking about image support in xPression, there are two types of support: direct and indirect. Directly
supported image formats are supported by the output format, and are passed directly through to the
publishing engine. Indirectly supported image formats are supported by the output format only if
compressed in a specific fashion. For indirectly supported image formats, xPression will extract the
necessary data and embed it, which may impact performance.
The following table details the xPression image support for each supported output format.
25
Images
Image Format
AFP
DOCX
BMP
Unsupported Directly
Supported
EPS
Unsupported Unsupported Unsupported Unsupported
Unsupported
Directly
Supported
GIF
Unsupported Directly
Supported
Directly
Supported
Unsupported
Indirectly
Supported
Unsupported
JPEG (JFIF)
Directly
Supported
Directly
Supported
Unsupported
Directly
Supported
Directly
Supported
PDF
Unsupported Unsupported Unsupported Unsupported
Directly
Supported
Unsupported
PNG
Unsupported Directly
Supported
Indirectly
Supported
Unsupported
TIFF (Group
4)
Directly
Supported
Unsupported Unsupported Directly
Supported
Directly
Supported
Directly
Supported
TIFF
Indirectly
Supported
Unsupported
Unsupported
Indirectly
Supported
Directly
Supported
Directly
Supported
TIFF
(Grayscale)
Unsupported
Unsupported
Unsupported
Unsupported
Directly
Supported
Directly
Supported
TIFF (Color)
Unsupported
Unsupported
Unsupported
Unsupported
Directly
Supported
Directly
Supported
Directly
Supported
HTML
PCL
PDF/PPML
Directly
Supported
Unsupported
Unsupported Unsupported
Directly
Supported
Unsupported
PostScript
(Monochrome
)
Note:
• xPression uses EPS images, not PostScript (PS) images. If you attempt to import PS images
through xAdmin, xPression will create an exception. If you have PS images you want to use
with xPression, please recreate them as EPS.
• xPublish does not support AFP Highlight color. If xPublish encounters an AFP highlight color
image, it will be converted to black and white.
• xPression supports only one type of CMYK image.for AFP output: CMYK TIFF images using
LZW compression.
Some Unsupported Image Types
The following image formats and types are not supported.
Image Type
Description
Animated GIFs
Animated GIFs are not supported. Animated GIFs are comprised of a number
of images in the same file. The animation effect occurs when an application,
like Internet Explorer, switches between the images. If you import an animated
GIF, xPression extracts only the first image in the sequence.
26
Images
Image Type
Description
EPS Image with TIFF
Proof/Preview
If you import an EPS image that contains a TIFF proof or preview, xPression
will only import the TIFF image because the TIFF proof precedes the EPS
image in the file. xPression will treat the image as a TIFF and not as an EPS.
Certain Compressed TIFFS
xPression only supports the following compressions: Uncompressed, Huffman
RLE (CCITT 1D), Group 4, LZW and PackBits compressions.
Image Support vs Feature Support
This chart shows some popular image formats and the features that xPression can support in each
when the image is used as an external image. In some cases, if the image is embedded in a document,
the host for the design tool may not support the feature. For example, in xDesign and xPresso for
Word, a CMYK image embedded in the a document will be converted to RGB by Microsoft Word.
For more information on transparency, see Transparency Support, page 27.
BW
Grayscale
Indexed
RGB
CMYK
Spot
Transparency
JPEG
no
√
no
√
√
no
no
EPS
√
√
√
√
√
√
See
Transparency
Support
PDF
√
√
√
√
√
√
√
GIF
√
√*
√
no
no
no
√*
TIFF Color LZW and √
Packbits
√
√
√
√
no
no
TIFF Mono LZW, G4, √
No Compression
no
no
no
no
no
no
TIFF Huffman RLE
√
no
no
no
no
no
no
PNG
no
√
√
√
no
no
√
BMP
√
√
√
√
no
no
no
* GIF grayscale and transparency are only supported for PDF output. The image may not output
correctly in other output types.
Transparency Support
27
Images
Support for transparency in EPS images is limited according to the output format:
• APF. AFP doesn’t support EPS, and converting EPS to a supported format for AFP will probably
cause transparency to be lost.
• PostScript. Transparency is supported for PostScript output from xDesign, xPresso for Adobe
InDesign, and xPresso for Word.
• PDF. PDF doesn’t support EPS, but does support transparency in other image formats. If
transparency is need for images in PDF output, consider using another image format.
TIFF does support transparency; however the transparency that it produces is not supported by
xPression. TIFF is a very open, flexible format that allows just about anything to be stored within it.
Most applications, including xPression, support only a subset of what TIFF can do.
PDL Native Support
Ideally, it is best to choose image formats that are native to the output stream you are creating. When
the format is native to the output stream, the image can be copied without decoding into the PDL.
When utilizing the xPublish content stamp feature with images, you must choose a format that is
supported natively by the PDL. The following table identifies which image types and features are
natively supported for each PDL.
PDL Support
Color / Feature Support
PDF
PS
AFP
PCL
BW
Gray
Indexed
Color
RGB
Color
CMYK Spot
Color Color
Transparency
TIFF G4
√
√
√
√
√
no
no
no
no
no
no
TIFF
Huffman
RLE
√
√
√
no
√
no
no
no
no
no
no
TIFF LZW
and Packbits
√
√
√
√
√
no
no
no
no
no
no
TIFF
uncomp
√
√
√
√
√
no
no
no
no
no
no
JPEG
√
√
√
no
no
√
no
√
√
no
no
EPS
no
√
√
no
√
√
√
√
√
√
√
GIF
√
no
√
no
√
√
√
no
no
no
no
PDF
√
no
no
no
√
√
√
√
√
√
√
TIFF Color
LZW
√
no
no
no
√
√
√
√
√
no
no
PNG
√
no
no
no
no
√
√
√
no
no
√
BMP
no
no
no
no
√
√
√
√
no
no
no
28
Images
PCL
PCL 5 does not support color, and only supports black and white TIFF images. To get images to
output in PCL, you must start with a G4 Tiff image.
xPresso for Adobe InDesign Images
When images are embedded in an xPresso for Adobe InDesign document, a conversion automatically
occurs during the packaging process. Only those images that are embedded are converted, images
that are externally referenced are not converted during packaging. The InDesign snapshot function is
used to convert every embedded image to PNG and JPEG; EPS images are also converted to PDF.
Each different image format is contained in the package. For all output formats, except PCL, this
conversion provides a supported image format for the xPression Publish publishing engine.
Storing Images in the xPression Repository
When you save an image in an xDesign document, upload an image to the xPression Repository
through xAdmin, or import an image through a PDPX, xPression stores the image in a particular
format, or series of formats. The following charts shows how xPression stores your images. Formats
highlighted in bold indicate that the format is the original file placed in the document.
Image
Color
Sub
-Type
Format(s) Stored in the
xPression Repository
TIFF
Mono
Huff RLE
G4
Mono
LZW
Mono
Binary
Mono
G4
G4
Mono
G3
G4
Color
JPEG
BMP
RGB
EPS
RGB
PNG, JPEG
BMP, PNG, G4 (if BW), JPEG (if
color)
JPEG
EPS, JPEG, PNG, PDF
CMYK
JPEG
RGB
JPEG
CMYK
PDF
RGB
PDF, EPS, PNG, JPEG
CMYK
29
Images
Image
Color
GIF
Index
GIF, PNG, G4 (for BW), JPEG
(for color)
PNG
RGB
PNG, G4 (for BW), JPEG (for
color)
30
Sub
-Type
Format(s) Stored in the
xPression Repository
Images
Images by Application
The following table describes image requirements and suggested formats to fulfill the requirements.
Requirement
Suggested
Comments
Black and white
CITT G4 TIFF
This is a very standard, compact way to store
monochrome images.
Small file size
CITT G4 TIFF is the format used by fax machines.
256 colors (8 bit)
GIF
This is a compact, web oriented format. It is suited
for lower color fidelity applications with electronic
formats.
PNG
This is a compact RGB format that supports
transparency.
Small file size
Photographs
Electronic output
It is ideally suited for electronic outputs, but will not
maintain transparency in PostScript, and is limited
to RGB color.
Transparency
High Quality Color
JPG
Photographs (RGB,
CMYK)
High Quality Color
JPG is lossy, meaning that its file size is reduced by
removing parts of the image.
JPG is very compact and a great format for
photographs.
EPS
Line art, photographs,
clipping paths, etc.
This format is only supported by PostScript and
some AFP devices.
This is the only format suitable for images
applications that require clipping paths.
All color models
When making PDF a PNG version of the EPS file is
created. This PNG file will support clipping paths if
they are contained in the EPS file.
Alpha channels are not supported for transparency.
CMYK or other color
models
JPEG or EPS
In EPS, any color model can be used, provided it is
supported by the output device.
RGB
JPEG, EPS, or
PNG
Cropping
All
Cropping is supported
Rotation
All
Image rotation is supported.
Scaling
All
Scaling is supported
31
Images
Requirement
Suggested
Comments
Transparency
EPS with
clipping path
This is the only format that will work for
transparency in PostScript.
When EPS files with clipping paths are used for
PostScript, an RGBA PNG file is created for use in
PDF. The RGBA (A is for alpha and indicates alpha
channel support) allows for transparency in the PDF
stream for EPS images.
All other methods of defining transparency are not
supported in PostScript.
Translucency
All
Translucency is not supported.
Opacity
All
Opacity is not supported.
Use G4 TIFF for Monochrome Images
For single bit images, G4 TIFF is the most popular option. It offers excellent compression and
universal compatibility. Importantly, most output devices have specific hardware acceleration to
support this format, increasing performance at the printer where it really counts. The PCL Emitter
only accepts G4, LZW and uncompressed monochrome TIFF files.
PDF Images
PDF support in xPression output can be classified in two categories: PDF images (less than a page)
and full- or multi-page PDFs. PDF images are supported for use in PDF, PostScript, and PPML output.
The following table details how each type of PDF can be included in a document for each xPression
design tool.
Design Tool
PDF Images
Multi-page PDFs
xDesign
Universal Content Image
External Image
External Content
Universal Content
xPresso for Adobe
InDesign
InDesign Place Function
From an ECM Repository
Image Variable
Universal Content Image Item
Place PDF Function
Universal Content Item
xPresso for Word
Word Insert Function
From an ECM Repository
Image Variable
Universal Content Image Item
Universal Content Item
32
Images
Note: (1) In xPresso, if you insert a multi-page PDF file using an image variable or through online
mode, only the first page of the PDF will be inserted in the document as an image. (2) If you include a
PDF image in a document that is published to an output format that doesn’t support PDF, a supported
image format that was created during an image conversion will be used. For more information, see
Picking the Right Format for the PDL, page 36.
When you insert a multi-page PDF through universal content, you can denote which pages of the
PDF are to be inserted into the document. Universal content also enables you to define TOC options,
formatting options, and inclusion conditions.
JPEG Images
Please review the following topics about JPEG support:
• JPEGs in AFP and PostScript Output, page 33
• Inline JPEGs in AFP Output, page 33
• JPEG Rendered in CMYK, page 34
JPEGs in AFP and PostScript Output
If the JPEG (.jpg, .jpeg) image has an irregular format, the xPublish publishing engine will not be
able to use it to produce PostScript or AFP output. A JPEG image is “irregular” if it contains one
of the following:
• More than one SOI (Start of Image: FFD8) tag. This tag should appear only once at the beginning
of the file.
• More than one SOS (Start of Scan: FFDA) tag. This tag indicates the beginning of the image scan.
You can use a utility such as IrfanView (http://www.irfanview.com/) to re-save irregular JPEG
images, and then use the newly saved images in your document.
Inline JPEGs in AFP Output
xPression uses AFP Function Set 11 to embed JPEG images inline. Note the following limitations
when you insert inline JPEG images for AFP output:
• The JPEG images must be 24–bit RGB.
• Function Set 11 is not be supported by all IBM InfoPrint systems and printers. Please contact your
vendor to ensure that Function Set 11 is supported.
• xPression uses "Scale to Fit" to scale an image to fit the frame size, but some InfoPrint systems and
printers may not support "Scale to Fit". In that case, you have to manually resize the image to
the same size as the frame.
33
Images
JPEG Rendered in CMYK
Internet Explorer 8 does not support JPEG images rendered in CMYK mode. Images must be
rendered in RGB mode if you are using Internet Explorer 8 with xReponse, xRevise, or the xDesign
Online Editor.
TIFF Images
The xPression Publish publishing engine currently supports four types of TIFF images:
• Bi-level images (monochrome images)
• Grey scale images
• RGB full color images
• Separation images (CMYK only)
The following types of TIFF images are not currently supported:
• RGB palette images
• YCrCb images
• CIE Lab images
• JPEG embedded images
Note: If you are using a multiple-page TIFF image as universal content in your document, the page
size the TIFF image is always Letter in the outputs.
The following table details xPression TIFF image support.
Image Types
Features
Compression
Method
Bi-level
Grey
scale
RGB
CMYK
No compression
Yes
Yes
Yes
Yes
CCITT 1D (Modified Huffman)
Yes
N/A
N/A
N/A
CCITT G3
1D
Yes
N/A
N/A
N/A
2D
Yes
N/A
N/A
N/A
Fill Bits Before
EOL
Yes
N/A
N/A
N/A
Uncompressed
Mode
No
N/A
N/A
N/A
Normal
Yes
N/A
N/A
N/A
Uncompressed
Mode
No
N/A
N/A
N/A
Pack Bits
Yes
Yes
Yes
Yes
LZW
Yes
Yes
Yes
Yes
CCITT G4
34
Images
Image Types
Features
Bits Per Sample
Fill Order
Color Presentation
Planar or interlaced
Image Data Storage
Bi-level
Grey
scale
RGB
CMYK
1
Yes
N/A
N/A
N/A
2
N/A
Yes
Yes
Yes
4
N/A
Yes
Yes
Yes
8
N/A
Yes
Yes
Yes
16
N/A
Yes
Yes
Yes
Normal
Yes
N/A
N/A
N/A
Reversed
Yes
N/A
N/A
N/A
Black is one
Yes
Yes
N/A
N/A
White is one
Yes
Yes
N/A
N/A
Planar (for example, RRRGGGBBB)
N/A
N/A
Yes
Yes
Interlaced (for example,
RGBRGBRGB)
N/A
N/A
Yes
Yes
Stripes
Single Strip
Yes
Yes
Yes
Yes
Multiple Strips
Yes
Yes
Yes
Yes
No
No
No
No
No
No
No
No
Tiled
Extra Samples (Transparency)
EPS Images
Be aware of the following issues with EPS images:
• If an EPS image cannot be opened in GSVIEW, it will not be converted successfully by the
xPression system.
• If you use an image variable to point to an EPS image, the image will disappear when previewing
it as PDF in an xPression client application.
ICC Color Profile Support
Embedded ICC color profiles in EPS, JPEG and PDF files can be passed through xPression to printer
drivers or RIP processors. xPression can’t pass ICC color profiles in TIFF images. For the supported
image types, xPression can pass the profile, but the profile can’t be used by xPression to match color.
xPression has no knowledge of the type of printer or RIP processor that will be used, and therefore,
can not resolve color matching.
Passing ICC profiles is supported in EPS files when output to PostScript; or when converted to PDF
or JPEG by xPresso for Adobe InDesign, and then output to PDF. You must ensure that “pdf” and
“jpeg” appear at the beginning of the image list for PDF output in the configuration file.
35
Images
Passing ICC profiles is supported in JPEG files when output to PostScript and PDF, and in PDF files
when output to PDF.
Any kind of conversion or processing on the image by the xPression Server will break the ICC color
profile, especially the Resample Image to Output Resolution function.
Picking the Right Format for the PDL
It is true that xPression will do image conversion. However, if you really want to optimize image
usage, then you should start with the image format that is best suited for your output. In this section
we will show you how xPression decides which image format to use for your output PDL, we will
show you how to customize this format selection, and give you some recommendations on which
image type to use for your output PDLs.
The following table details which format each unsupported image is converted to for each output
format. An entry of “N/A” means the image format is supported for the output format (so no
conversion is necessary); an entry of “None” means the image is not supported, but no image
conversion occurs.
Original Image
AFP
DOCX
HTML
PCL
PDF/PPML
PostScript
BMP
JPEG
N/A
N/A
None
JPEG
JPEG
EPS
JPEG
JPEG,
PNG
JPEG,
PNG
None
PDF, JPEG,
PNG
N/A
GIF
JPEG
N/A
N/A
None
N/A
JPEG
JPEG (JFIF)
N/A
N/A
N/A
None
N/A
N/A
PDF
JPEG
JPEG
JPEG
None
N/A
JPEG
PNG
JPEG,
Group 4
N/A
N/A
None
N/A
JPEG
TIFF (Group 4)
N/A
JPEG
JPEG
N/A
N/A
N/A
TIFF
(Monochrome)
Group 4
JPEG
JPEG
Group 4
N/A
N/A
TIFF (Grayscale)
None
JPEG
JPEG
None
N/A
N/A
TIFF (Color)
None
JPEG
JPEG
None
N/A
N/A
How xPression Decides Which Format to Use
When you place any image into the xPression Repository, xPression automatically generates an image
format compatible with Web output to support previewing the image from xAdmin. For publishing
on the Server xPression selects an image format that is best suited for the output type.
The image type that is used during publishing is controlled by a setting in the DCPI.properties
configuration file, located in the xPressionHome directory on the xPression Server. Each output
36
Images
format has a parameter in the file that contains a list of supported image formats. The order of the
image formats determines the order xPression will select an image format to publish.
The following table shows xPression’s default image format selection for each output type.
PDL
Default Image Selection
AFP
PDF, JPG, JPEG, GIF
DOCX
PNG, JPG, GIF, BMP
Email and HTML
PNG, JPEG, JPG, GIF, BMP
PCL
TIF, TIFF
PDF
TIF, TIFF, PNG, PDF, JPG, JPEG, GIF, BMP
PostScript
PDF, EPS, JPG, JPEG, TIFF
TIFF
TIF, TIFF, PDF, PNG, JPG, JPEG, GIF, BMP
Image Type Limitations
Some image types that are supported by xPression are not supported by all output types. The
following limitations apply:
• PDF supports all image types supported by xPression
• PostScript supports all image formats supported by xPression except PNG.
• PCL supports Group4 only.
How xPression Determines the Image DPI
For raster images (TIFF, GIF, BMP, JPG) xPression determines the DPI resolution of auto-generated
images by attempting to use the image resolution value embedded in the image. If the value is not
embedded in the image, xPression uses the default resolution of 72 DPI.
For PDF and PostScript images, xPression converts these images to raster images, assigning DPI
values as follows:
• 300 DPI for Print images
• 96 DPI for Web images
How to Customize the Image Format Selection
You can customize how xPression selects image formats for your PDL in two ways. First, you can
customize the default image format selection for each PDL by editing the configuration file on your
server. This change affects the entire xPression system. Secondly, you can customize the image
format selection for individual output streams. These output stream settings override the default
preferences set in the configuration file.
37
Images
Customizing Image Format Selection
You can customize the default image format selection method by editing the DCPI.properties file
for your server. The DCPI.properties file is located in the xPressionHome directory (by default,
C:\xPression). The changes made to this file affect the entire xPression system, but will be overwritten
by any preferences you set in the individual output stream.
The DCPI.properties file contains seven properties that enable you to specify the image format
selection preference:
• ImagePreferenceForPDF
• ImagePreferenceForPS
• ImagePreferenceForAFP
• ImagePreferenceForTIFF
• ImagePreferenceForHTML
• ImagePreferenceForDOCX
• ImagePreferenceForPCL
To edit the file:
1.
Navigate to the xPressionHome directory.
2.
Locate and open the DCPI.properties file in an editor.
3.
Locate the following section in the DCPI.properties file.
#
BarcodeResolution=72
#
# Image format preference for different output type. When a image
# is selected or created the format preference will be concerned.
#
#ImagePreferenceForPDF=tif;tiff;pdf;jpg;jpeg;png;gif;bmp
ImagePreferenceForPS=eps;jpg;jpeg;tif
ImagePreferenceForAFP=jpg;jpeg;gif;tif;tiff;group4
ImagePreferenceForHTML=png;jpg;jpeg;gif;bmp
ImagePreferenceForPDF=tif;tiff;pdf;png;jpg;jpeg;gif;bmp
ImagePreferenceForPCL=tif;tiff
4.
Locate the property for your output PDL. For example, for PostScript:
ImagePreferenceForPS=eps;jpg.jpeg;tif
5.
The first image format listed in the value of the property is the first image xPression attempts to
select for the output PDL.
6.
Change the order as needed and save the DCPI.properties file when completed.
Customizing Output Stream Image Format Selection
You can customize the image format selection method at the output stream level in xAdmin.
38
Images
The Image Preference button enables you to reorder
the image format preference for your output stream
.
The preferences defined here overwrite the default image format selection preferences defined in the
DCPI.properties file, and apply only to the documents in the output stream.
To set the image preference for the output stream:
1.
Start xAdmin and click xPublish Output Management.
2.
In the xPublish Output Management menu, click Stream Definitions.
3.
Locate the Image Preference button and corresponding text box.
4.
Click Image Preference. The Image Preference pop-up box appears.
The Image Preference pop-up box enables you to select and order output formats
.
39
Images
5.
The Available Images list contains all available image types. The Images list displays all image
types you have selected for the current output stream. To move image types from the Available
Images list to the Images list, select the image type and click Add.
6.
Once you have all of your image types in the Images list, you can order the images by selecting
them and clicking the Move Up and Move Down buttons. Images at the top of the list are
selected first, images at the bottom of the list are selected last.
7.
When finished, click Open. The selections you made appear in the Image Preference text box.
8.
Click Save.
General Image Type Recommendations for Your PDL
The following table provides general image type recommendations for your PDL.
xPresso for Word
xPresso for InDesign
xDesign
AFP Black and White High
Speed
G4 TIFF
G4 TIFFs as external
images
G4 TIFF
PCL
G4 TIFF
G4 TIFFs as external
images
G4 TIFF
AFP Color
JPEG
JPEG
JPEG
PostScript
EPS / JPEG
EPS / JPEG
EPS / JPEG
PostScript with
Transparency
EPS
EPS
EPS
PDF
JPEG
PDF, JPEG or PNG if
you need transparency
PDF or JPEG
Bar Code Images
When xPression generates a bar code in document output, the bar code is actually an image.
Currently the third-party tool used to create the bar codes only supports RGB color, and doesn’t
support CMYK. Although the bar codes may look black and white, they are actually RGB color, which
may cause issues with some bar code readers.
You can force black and white images for bar codes by setting the TiffG4ImageasBarcode parameter
in the xPression Server DCPI.properties file to “true”. When this parameter is set to “true” (the
default), Tiff G4 will be used as the bar code image format. If this parameter is set to “false”, the
ImagePreferenceForOutputFormat parameter (also located in the DCPI.properties file) will be used to
determine the bar code image format. The ImagePreferenceForOutputFormat parameter controls all
the images in an output stream, the TiffG4ImagesasBarcode parameter controls only bar code images.
Note: The PNG image format is not supported for PostScript output, so it is important to ensure that
PNG is not listed as the image preference in the ImagePreferenceForPS parameter.
40
Images
Images in xPresso Documents
You can include images in your xPresso for Adobe InDesign and xPresso for Word documents in
one of two ways: by embedding the image in the document file, or by referencing an external image.
The method you choose depends on your situation, and may differ document by document, or even
image by image within a document.
Embedding Images
You embed images in your xPresso for Adobe InDesign or xPresso for Word document when you
place images in the document using the InDesign “place” function or the Microsoft Word Insert
Picture function, or when you choose to embed an image placed from a server ECM repository (using
the Place From server option). In InDesign, just placing the image doesn’t embed it into the InDesign
document, it will have a link to the file. If you want to embed the image in the InDesign document,
you must select Embed File from the Links panel after you place the image.
Whether the image is inserted, placed, or embedded, the image file is included in the document
package during the packaging process, eliminating the chance for missing image errors at publish
time. Embedding images relies on the images being available at design time.
External Images
You can insert external images through an image variable, through a universal content image, or by
placing a reference to a image contained in an ECM server repository. Image variables are inserted
into your document through xPresso for Adobe InDesign or xPresso for Word and point to data that
contains the path and file name of an external file. Universal content images enable you to place
an image that is stored locally or on a network, on the xPression Server, or you can use a variable
reference. The image file is incorporated into the document at publishing time on the xPression
Server. When you place an image from an ECM server repository, you can choose to insert a reference
to the image. You can also specify if you want to use only the version of the image that you placed, or
have the xPression Server pull the latest version of the image at publish time.
The image file is incorporated into the document at publishing time on the xPression Server. When
using image variables or universal content images, you don’t need to have the image available at
design time, your data just needs to contain the image path and name. Images can also change over
time without needing to update the document (if they fit in the same space). Because the images are
inserted at publishing time, and not included in the package, it is possible to get errors if images are
missing, or incorrectly named or referenced.
You can structure your external image references for image variables either by using a relative path,
or an absolute path. In both cases, you must ensure that the images exist on the client and the server
in the correct location. If you specify the entire path, you must also ensure that the exact same path
exists on the client and on the server. For more information, see Structuring Relative External Image
References, page 42.
41
Images
Structuring Relative External Image References
You can structure your external image references for image variables either by using a relative path,
or an absolute path. In both cases, you must ensure that the images exist on the client and the server
in the correct location. If you specify the entire path, you must also ensure that the exact same path
exists on the client and on the server.
External images referenced through relative paths must reside in the image directory on the xPresso
for Adobe InDesign or xPresso for Word client computer, as well as in the image directory on the
xPression Server.
The default image directories are:
• xPresso for Adobe InDesign client:
— Windows XP: [Drive:]\Documents and Settings\All Users\Application Data\xPresso
\[version#]\xPresso for InDesign\CS[#]\Images
— Windows 7 & Windows 2008: [Drive:]\ProgramData\xPresso\[version#]\xPresso for
InDesign\CS[#]\Images
— Macintosh: [xPresso for InDesign Install Directory]\xPresso\image
• xPresso for Word client:
— Windows XP: [Drive:]\Documents and Settings\All Users\Application Data\xPresso
\[version#]\xPresso for Word\office20[##]\Images
— Windows 7 & Windows 2008: [Drive:]\ProgramData\xPresso\[version#]\xPresso for
Word\office20[##]\Images
The directory location on the server is defined in the xPRSConfig.xml file, which is found in the
[xPressionHome]\ directory.
To use a relative path, you’d structure the reference in your data like this: <image>logo.jpg<image>.
The logo.jpg image must be located in the default image directory on the client and the server in order
for it to be found during previewing (on the client) and publishing (on the server).
Working with Images in Your Document
When you add images to your xPresso for Adobe InDesign or xPresso for Word document, you
can scale them, rotate them, and crop them as necessary. Images can be rotated arbitrarily at any
angle. Images can also be cropped within a frame, so that only the part of the image that you want
to show will appear in the output.
Scaling Images
When you insert images into your document, you can scale and rotate them in any way you like
interactively using the design tool interface. When you insert external images through image variables
42
Images
or universal content, the scaling is done at publishing time when the image is placed in the document.
You can choose from the following scaling options for image variables and universal content images:
• Original Size. Places the image in the frame at its original size (100%).
• Fill Content to Frame. Scales the x and y size of the image to completely fill the frame.
• Fit Content Proportionally. Scales the image to the size of the graphic frame while maintaining
proper aspect ratio. This method is lossless, meaning that the image will be stretched or
compressed in both width and height so that the image can be displayed as large as possible and
in the correct proportions.
• Fill Frame Proportionally. Scales the image to the size of the graphic frame, while expanding (or
compressing) the measurement (width or height) that reaches the bounds of the frame first until
the other measure is exactly the width or height of the frame. The resulting image is proportional
and fills the entire frame, but some of the image content will be cropped by the graphic frame.
Transparency and Opacity in InDesign
In Adobe InDesign, opacity is the amount of transparency that exists in an image. If an image has
100 percent opacity, it is not transparent at all. As you decrease the amount of opacity, it becomes
more transparent.
xPresso for Adobe InDesign supports transparency, as defined in InDesign, only in PDF and PPML
output. Transparency is supported in PostScript output through the use of EPS images.
InDesign enables you to assign a transparency value on two different levels. On the first level, you
can set transparency on a frame or group of frames. On the second level, you can set transparency
separately on the frame border, frame background, and frame content (text and image within the
frame). The transparency value specified defines how transparent the object should be.
The transparency settings defined in InDesign are different than alpha channels that you would find
within an image, such as a PNG image. xPresso for Adobe InDesign supports only the specified
transparent value (which will be constant throughout the object) as defined in InDesign. Alpha
channels, where the value will be different on different positions of one object, are not supported.
xPresso for Adobe InDesign supports all the options on the Effects dialog box for Transparency:
• Basic Blending Mode. Specifies how the colors in transparent objects interact with the objects
behind them. Each of the 17 blend modes is supported.
• Basic Blending Opacity. Determines the opacity of an object, including stroke, fill, text, image
and group. The value ranges from 0 to 1, with 0 making the object invisible, and 1 making the
object opaque. Any value between 0 and 1 makes the object transparent.
• Isolate Blending. Limits the blending to specific objects. When blending is applied to an object,
the colors blend with all the objects beneath it. The Isolate Blending option confines the blending
to within the selected group, preventing objects beneath the group from being affected.
• Knockout Group. Makes the opacity and blending attributes of every object in the selected
group visually block out (knock out) underlying objects in the group. Only objects within the
selected group are knocked out; objects beneath the group are still affected by the blending or
opacity applied to them.
43
Images
xPression does not control the final presentation of transparency in the output; the result is controlled
by the viewer used to display the PDF file. Transparency is supported in Adobe PDF version 1.4 and
above. Acrobat Reader 8 or newer is required to see transparency in xPresso for Adobe InDesign
PDF output.
Note: A frame that contains transparency can only be snapshot using PDF for the snapshot image
type. Using a raster image type for a snapshot of a frame that contains transparency is not supported.
For more information on the snapshot function, see the xPresso for Adobe InDesign User Guide.
How xPression Handles Images
In the xPression environment, images can be stored in several locations.
• The xPression Repository - Most images are stored in the xPression Repository and managed
through the Image Utility in xAdmin. You can directly upload images to the xPression Repository
through xAdmin, let xPression automatically upload images to xAdmin after they are used in an
xDesign content item, or import an ECM Documentum image to the xPression Repository through
xDesign. xPresso for Adobe InDesign and xPresso for Word also have access to the xPression
Repository for placing images in documents.
• Documentum xPression Repository - If you are licensed for Documentum Edition, you also have
the option of storing images in the Documentum xPression Repository. xDesign, xPresso for
InDesign, and xPresso for Word can all have access to the Documentum xPression Repository
for placing images in documents.
• An ECM repository- You can store images in additional Documentum Docbase or FileNet
repositories. xPression will pull the image from the ECM repository when it is viewed or
published.
• On the file system - You can insert images as external image references. This enables you to store
your images on directory accessible by the xPression server.
The xAdmin Image Utility
To access the image utility, click Image Utility from the xAdmin Resource Management menu. The
Image Utility enables you to add, update, preview, and delete images. From the image utility list, you
can complete the following actions.
Element
Description
Add
Enables you to add a new image family to the xPression Repository.
Update
Enables you to update an existing image family. Select the image family you want to
update, and click Update.
Preview
Enables you to preview an image in the xPression Repository. Select an image format
and click Preview.
44
Images
Element
Description
Delete
Select one or more image families and click Delete to permanently remove them from
the xPression Repository.
Image Family Name
List
Click the image family name to access the image family options.
45
Images
Importing an Image to the Image Management Utility
When you import an image into the xPression Repository, you are really setting up an image family
for the different versions of the image you might need.
To add a new image:
1.
From the Image Management Utility page, click Add.
2.
The Add Image Family page appears. You can specify the family name and specify an optional
web format. Supply a name for the image family. The name must be between 1 and 255
alphanumeric characters in length. The name must be unique and is case-sensitive.
3.
In the Import Local Image box, supply the path and file name of the image you want to import.
You can use the Browse button to select an image from your file system, or type the fully-qualified
path and filename for the image.
4.
The Web Format box enables you to control which image is used for HTML, e-mail, or PDF
documents. For example, you may want to use a JPEG image or a GIF image of a particular
resolution. If you do not select an image for Web format, xPression automatically converts your
image for web use unless the original image is already in a suitable format. xPression sets the
resolution for auto-generated Web images at 100dpi.
You can use the Browse button to select an image from your file system, or type the fully-qualified
path and filename for the image.
5.
Click Save to upload the selected image to the xPression Repository.
Images in Your xDesign Documents
Images in xDesign documents can originate from four different locations. First, you can upload
images to your xPression Repository through xAdmin, and then insert them into your images
as needed. Secondly, you can insert images directly into an xDesign content item from your file
system. When xPression saves the content item in xDesign, it automatically uploads the image to
the xPression Repository. Third, you can retrieve images from an ECM Documentum Docbase and
insert them into your content item by reference, or import them into your document and xPression
Repository. Finally, you can insert images as an external reference. This enables you to store images
on a network accessible directory and simply reference that path in your xDesign content item.
Images in Your xPresso Documents
You can include images in your xPresso documents by embedding static images directly in to
your document, or by including a reference to an external image through an image variable or a
universal content image, or by a reference to an image in an xPression or ECM repository. For more
information, see Images in xPresso Documents, page 41.
46
Images
Printer Resident Images
Some printers enable you to store images in the printer memory. Storing an image in the printer
memory increases printing performance because the image does not need to be downloaded from the
xPression Repository. xPression enables you to use this feature by matching your Printer Resident
Images with the images in your xPression Repository.
This feature applies to xDesign and xPresso for InDesign content. The printer resident images can
only be used as UC in the documents created by xPresso for InDesign. You do not have to perform
any specific actions in xDesign to use printer resident images. Simply insert your images into your
document and ensure that your image has been added to the xPression Repository.
This feature appears in Printer Definitions, which are configured through the xPublish Output
Management menu in xAdmin. In the Printer Resident Image section, you add images to the list,
define their location in your printer memory, and map them to image families from your xPression
Repository.
For each image that you store on the printer memory, you must store a copy of that image in the
xPression Repository. xPression uses the xPression Repository version for viewing and editing
purposes. Then you must map your printer resident images to the images in your xPression
Repository.
Adding an image to this list does not actually load the image onto the printer. You must use your
printer’s import functions to load images to the printer prior to producing your documents.
Image Optimization in AFP Output
When image optimization is turned off in an xAdmin printer definition, images are repeatedly
embedded into the output file, increasing the file’s size. For AFP output, only TIFF Group 4 and 8–bit
JPG images are supported for embedding in the output file, all other image types will be discarded.
47
Images
Going into Production
Before you place your xPression document into production, take a pass through the following image
check list:
• Are all the image formats used in the document compatible with the output type?
• Do all the images have the appropriate DPI for the output type?
• Are all the images appearing as expected when previewing the document through the design
client?
• Have all external images been placed in the correct location on the server?
48
Chapter 3
Using Fonts
Placing type on a page is a very complex process. All systems that handle documents have a special
mechanism to deal with type and typography. Each font consists of a series of hundreds or even
thousands of unique little pictures. Each page of text may contain thousands of these little pictures.
In order to support this rather complex concept, all page description languages (PDLs) and computer
operating systems have a special mechanism specifically designed to optimize handling of characters
of text.
This section will explain the notions required to support setting of type, how they are described in
font files, and how they are processed by xPression using various PDLs.
Anatomy of a Font
A typeface or font is a very complicated composite object that is made up of a lot of parts. This
section will look at the various pieces and how they together provide all of the information necessary
to describe a typeface.
Glyphs
Glyphs are the shapes given in a particular typeface to a specific symbol. It is a particular graphical
representation of a character. Think of a font as a lot of very carefully drawn little drawings. The
glyph is this little drawing. Different fonts have a different number of glyphs. For example, a font can
contain a full western character set as well as a full Chinese character set.
Latin, or Western European languages use a small number of characters, typically less than 30.
Chinese and Japanese languages use many thousands of characters.
Font Metrics
Font metrics define information such as character width and height. Applications that use fonts
generally stack characters up against each other. Typically the space defined by the font metric is
wider than the actual glyph, otherwise characters would touch or overlap.
Font metrics tell applications how much space a character occupies.
49
Using Fonts
All applications that set type must know this information to determine when to break lines, and
where to place the characters relative to each other.
Also included in font metrics are kern pairs. Kerning is the adjustment of the spacing between two
specific characters when they appear together. The classic example is AW.
Kerning can be positive or negative. In the fi kern pair, space is added between the characters.
Kerning is not currently supported by xPression.
Encoding
Encoding is the association of a number with a glyph in a font. Characters in text are represented
by numeric values. When you press a key on a keyboard, you are really entering a number into the
computer. The computer takes that number and using the encoding of the font, matches it up to a
little drawing of a character for you. This is encoding.
Single Byte and Double Byte
Computers use binary numbers to store everything. The standard unit is the "Byte." This is an 8-bit
quantity that can store 256 values. For Western languages, 256 is plenty of characters to represent
most documents, but the Chinese and Japanese languages require thousands of characters. For these
languages, we need to count higher than just 256, and therefore we need to use a bigger unit than a
byte to store it. If we use 2 bytes we get 216 or 65,536 unique numbers to use to identify characters.
With xPression we can use single byte, double byte encoding, or both.
For single byte fonts xPression uses WinANSI code page 1252 encoding, for large character sets
xPression uses Unicode encoding.
WINANSI
Windows-1252 is a character encoding of the Latin alphabet used by default in the legacy components
of Microsoft Windows in English and some other Western languages. This chart shows how each
hexadecimal number can be associated with a glyph.
50
Using Fonts
51
Using Fonts
The following table shows the advantages and disadvantages in using WINANSI encoding.
WINANSI
Advantages
Disadvantages
Supported by most page description
languages such as PostScript, PDF, AFP,
PCL
Only supports 256 characters
Supported by most software packages
that process output from page description
languages (such as xTest, Emtex and
others)
May not support some special bullet characters
even for western European languages
Supported by even the oldest printers
Text is readable in PDL output files (you
can read words in output to help with
troubleshooting)
Unicode
Unicode is an industry standard allowing computers to consistently represent and manipulate text
expressed in any of the world’s writing systems. The standard itself describes quite a few concepts,
the most important for the purposes of this document is the ability to address and manipulate about
100,000 characters in any of the world’s writing systems in a standard way.
The following charts show the advantages and disadvantages in using Unicode encoding.
Unicode
Advantages
Disadvantages
All characters in any font can be
supported
Unicode fonts can be very big (20 MB vs 50k for
small character set fonts)
Can be used for any writing system
including Korean, Japanese and Chinese
Two bytes need to be used to address each
character (text is not readable in any PDL)
Performance may be very slightly slower
because of additional processing time for
double byte characters
Font Formats
There are three main font types supported by xPublish. This section will discuss those formats,
their history and features. All of the font formats supported by xPublish are outline fonts. Outline
fonts use Bézier curves, drawing instructions, and mathematical formulas to describe each glyph.
The glyphs are stored as scalable drawings that allows fonts to be scaled to any size and used at
a variety of rotations.
52
Using Fonts
xPublish supports the following font types:
• Adobe Type 1, page 53
• TrueType (.TTF), page 53
• OpenType, page 54
Adobe Type 1
xPublish supports Type 1 fonts for PDF and PostScript. Type 1 fonts were developed by Adobe as
the initial native font format for PostScript and the Apple LaserWriter in 1985. Type 1 fonts are
composed of two files. One contains the glyphs, and the other the font metrics. PFB, PFM and AFM
files are used to store Type 1 fonts on all platforms except Macintosh. The Type 1 format supports 256
characters, and is not capable of describing large character set fonts.
File Type
Description
PFB - Printer Font
Binary
Contains glyphs, widths for characters, and basic encoding. This file can be
transformed into a PFA file (Printer Font ASCII) that is the actual font format
that is utilized by PostScript printers.
PFM - Printer Font
Metric
This is a binary file used by Windows and other systems that contains the font
metrics for the font.
AFM - Adobe Font
Metric
This is an ASCII font metric file that contains all of the font metrics for the
typeface.
Issues with Type 1 Fonts
There are a number of issues with Type 1 fonts that initiated the second generation of PC fonts:
• The Type 1 font format was originally proprietary and encrypted. The industry needed an open
standard which Adobe eventually published, but by then TrueType fonts had been born.
• Font and font metric files are different and not compatible between Mac and PC.
• Managing font and font metric files separately really does not make sense.
• Type 1 fonts cannot contain more than 256 characters.
TrueType (.TTF)
xPublish was designed to use the same TTF fonts used in the Macintosh and Windows operating
systems. TTF fonts are the xPublish master format. TrueType was originally developed by Apple
Computer in the late 1980s as a competitor to Adobe’s Type 1 fonts used in PostScript. TrueType
fonts solve all of the previously stated issues. A single binary file contains glyphs, font metrics, and
can contain very large character sets. They can be used on all platforms without modification or
conversion.
53
Using Fonts
OpenType
xPublish supports OpenType fonts for AFP, PDF, and PostScript. xPublish also supports TTF fonts
in an OpenType wrapper. OpenType was initially developed by Microsoft, later joined by Adobe
Systems. OpenType was first announced in 1996, with a significant number of OpenType fonts
starting to ship in 2000-2001. Adobe completed conversion of its entire font library to OpenType
around the end of 2002 and now only sells fonts in this format.
Note: The OpenType font ZapfDingbatsStd.otf is not supported for TIFF output because it is
not supported by Multivalent, an open source tool used by xPression. EMC Document Sciences
recommends replacing it with the Wingdings font.
AFP Fonts
xPublish also supports the AFP fonts that meet the following characteristics.
• Must be an AFP Outline font
• Must have been created from TrueType font masters stored in the xPression Repository
• Supports double-byte (Unicode) through TTF fonts and single-byte through AFP Outline fonts
• Fonts must use the Latin alphabet
See Using Fonts in AFP Output, page 63 for more information.
Using Fonts
Fonts are external resources required to reproduce documents. For a document to be reproduced
properly, the fonts need to be available at the device that is trying to reproduce the document.
This could be a computer viewing a document in PDF form or a printer creating paper
output.
In a typical workflow, fonts need to be available in several areas:
1.
Fonts should be available to the authoring tool (client) so that they can be defined as part of
the document.
2.
They need to be installed on the xPression server to to enable the server to use them when
composing output.
3.
Finally, they need to be available to the printer (or viewer).
For the client and the server (items 1 and 2 above), the solution is simple. Fonts used in documents
need to be installed in both locations.
54
Using Fonts
For printing output (item 3 above), there are two strategies.
1.
Embedding fonts - Including the font in the print stream so that there are no external
dependencies (embedding fonts). You can also embed fonts while using subsetting.
2.
Printer resident fonts - storing a version of the fonts in the printer memory
Embedding Fonts
In order to transport documents with reliable fidelity, it is necessary to reduce dependencies on
external files such as fonts. This can be done by embedding fonts within the document itself.
Documents that contain embedded fonts can be reproduced faithfully by using the embedded fonts.
When rendering the document, the font is extracted and fed to the font machinery of the rendering
mechanism (PDF, PostScript, AFP, etc.). When embedding fonts, the output files must contain fonts
that can range from 20k to 20MB depending on the number of characters.
Embedding Fonts
Advantages
Disadvantages
File can be rendered faithfully anywhere
and any time in the future.
Increased output file size.
No environmental dependencies.
Increased processing time.
Fonts are included one time for the entire
output file.
You can also embed fonts while using subsetting.
Printer Resident Fonts
Most printers have a mechanism that allows you to install fonts on the printer so that they are
available even if the printer is powered down and restarted. Fonts installed in this manner are
called printer resident fonts. If a font is known to be printer resident, then it does not need to be
embedded in the output file.
Printer Resident
Fonts
Advantages
Disadvantages
File sizes are reduced because fonts are
not included.
Fonts must be actively managed on printer(s).
Printer processing time is reduced
because the font need not be reconstituted
and passed to the font mechanism.
Multiple printers must be kept in sync.
Unable to handle multiple versions of a font for
different jobs.
Most printers substitute fonts when fonts are
missing - you may not notice until it is too late
that a font is not working properly.
55
Using Fonts
Subsetting
With the introduction of TrueType fonts, it became possible to define many thousands of characters
within a single font. This was designed to support Asian and other large character sets. The
problem is that some of these extensive character sets can be in excess of 20 MB when embedded in
a print stream. For example, if you needed to print a page that contained a single character of the
ArialMTUnicode font and you did not use subsetting, you might end up using 20 MB of font and 500
bytes of page description because it would embed the entire font when only one character is needed.
Subsetting embeds only the glyphs used instead of embedding the entire font. For example, many
Unicode fonts contain Arabic and Chinese characters. If you are producing a document in German,
you do not need to include these characters.
Subsetting
Advantages
Disadvantages
Can significantly reduce file size.
Text in PDF files can not be edited because only
some of the characters for the font are available.
Only the characters used in the job are
included in the print stream - this creates
the most efficient output files.
Some 3rd party applications that read print
streams will have problems. For example, if
you change the page order by placing page
10 at the beginning of a document. It may be
counting on characters that were downloaded
with page 7 to be available.
User-Created Fonts
If your user-created fonts have license restrictions, you can set the OnFontNotSupported or the
OnFontNotFound parameter in the xPressionPublish.properties file. For more information, see
xPressionPublish.properties in the Administering the xPression Server guide.
How xPression Handles Fonts
In the xPression environment, fonts are stored in three locations:
• The xPression Repository - All xPublish fonts are stored here as a reference. These fonts are
your master set and are not used in production.
• The xPublish machine - xPression uploads a copy of your fonts to a semi-permanent disk cache
located on the machine that processes your documents. Fonts are uploaded when they are first
used and persist until deleted or updated. These fonts are used for production.
The semi-permanent disk cache resides in your xPression installation directory. This path is
defined in xPressionPublish.properties located in the xPression installation directory.
• The client machine - Fonts are stored on the client machine for editing and viewing.
Each time xPression publishes a document, the fonts on the xPublish computer are checked against
the fonts located in the xPression Repository. If the needed fonts do not reside on the xPublish
computer, xPression uploads the fonts from the xPression Repository. xPression also updates the
56
Using Fonts
fonts if the xPression Repository contains a newer version of the fonts. The fonts remain on the
xPublish server indefinitely until updated by xPression or specifically removed by the user. The
fonts are reused for subsequent jobs.
The following table summarizes xPression font support for AFP, PDF, and PostScript output. For
information about PCL font support, see Using Fonts in PCL Output, page 68.
Font Type
AFP
PDF
PostScript
TrueType
Yes
Yes
Yes
OpenType
(New Type 1)
Yes
(.tff only)
Yes
Yes, except
Bitmap fonts
AFP Outline
Yes
No
No
Old Type 1
(Windows or Mac Type 1)
No
Yes
Yes
Double-Byte
Yes
Yes
Yes
Note: OTF and Type 1 fonts are not supported in dynamic charts.
The Font Management Utility
The xAdmin Font Management Utility enables you to manually upload, update, and delete fonts
from the xPression Repository. This utility manages fonts for the xPublish composition engine, not
for the CompuSet composition engine. The Font Management Utility is located in the Resource
Management section of xAdmin.
Note: The Font Management Utility supports loading TrueType fonts; loading Type1 fonts is not
supported.
To add a new font to the xPression Repository through the Font Management Utility:
1.
From the Font Management Utility, click Add.
2.
xPression displays the Add a New Font page. Type the path to your font file or click Browse to
navigate to the file.
3.
Click Save to add the font to the xPression Repository.
Before you can load an AFP font, the font’s TrueType equivalent must be loaded using the previous
steps.
To add a new AFP font to the xPression Repository through the Font Management
Utility:
1.
Access the Font Utility page in xAdmin.
2.
Select the check box next to the font in the list that is the TrueType equivalent of the AFP font
you are adding.
3.
Click Add AFP. The Font Utility: Add AFP Font page appears.
4.
Browse to locate the AFP outline font (.oln).
57
Using Fonts
5.
Browse to locate the code page (.cdp).
6.
Select whether (yes) or not (no) to replace an existing font.
7.
Click Save to add the font to the xPression Repository.
Large Character Fonts
The xPublish publishing engine supports large character (also called double-byte) fonts for AFP, PDF,
and PostScript output as long as the fonts are TrueType. For AFP output, the symbol font is not
supported. Arabic languages are not supported.
Asian language groups, including Simplified Chinese, Traditional Chinese, Japanese, and Korean
(CJK) fonts are supported, with the following limitations:
• The following CJK-specific composition features are not supported:
— Auto-adjust space between CJK and Latin (number) characters
— Hanging punctuations
— Special text alignments
— Top-to-bottom text direction
— Phonetic characters
— Enclosed characters
— Horizontal in vertical
• Only Unicode BMP is supported; therefore, only part of the characters in CJK fonts are supported
• Korean justification logic is not supported
• Japanese multi-baseline output is not supported
• There may be some differences in line height and spacing between Chinese output on the server
and what you see in the design tool.
• Chinese fonts are not supported for use in dynamic charts.
If you are publishing Traditional or Simplified Chinese output, you must ensure that there is at least
one Traditional or Simplified Chinese font available for use by the publishing engine. xPression will
use Courier New by default if no Chinese font is found, which will not produce desirable output.
Microsoft Word provides multiple baseline alignment options. xPression supports only Baseline
for Chinese characters.
Asian Typography Support
Microsoft Word provides several Asian typography options. The following table details xDesign’s
and xPresso for Word’s support of the options.
58
Using Fonts
Option
Support
Line Break: Use Asian rules for controlling first and last
characters
Not Supported
Line Break: Allow Latin text to wrap in the middle of a
word
Not Supported
Line Break: Allow hanging punctuation
Not Supported
Character Spacing: Allow punctuation at the start of a
line to compress
Not Supported
Character Spacing: Automatically adjust space between
Asian and Latin text
Supported
Character Spacing: Automatically adjust space between
Asian text and numbers
Supported
Character Spacing: Text alignment
Only Baseline supported
Options: First and last character settings
Only Standard supported
Options: Kerning
Not Supported
Options: Character spacing control
Only Do not compress supported
xPression doesn’t compress punctuation; therefore, the same punctuation of the same font and size
will always have the same width. Also, xPression doesn’t allow punctuation to exceed the paragraph
margin. Because of these limitations, you may see a difference in line breaks between the document
in xDesign, and the published output.
Fonts in Your xDesign Documents
If you insert a new font into an xDesign document, xPression will automatically upload that
font to your xPression Repository when you save your content item in xDesign. If you open an
xDesign document that contains fonts that are not available on your client computer, xDesign will
automatically download the needed fonts from the xPression Repository.
Fonts in Your xPresso Documents
The fonts from your xPresso documents reside in a folder on your client. The fonts are not included in
the PDPX package used to import the document to the server. The fonts for your xPresso documents
must be manually uploaded to the xPression Repository through xAdmin.
Migrating Fonts
When you export or migrate xDesign documents, you have the option to include your fonts in the
PDPX package. Please be aware that the fonts will increase the size of your PDPX package. Fonts
included in the PDPX package are automatically uploaded to the xPression Repository upon being
migrated or imported to the xPression server.
59
Using Fonts
When you export xPresso documents, the fonts are not included in package. The fonts for your
xPresso documents must be manually uploaded to the xPression Repository through xAdmin.
Fonts and Page Description Languages
Page Description Languages (PDLs) are languages for describing the layout and contents of a printed
page. While operating systems have mostly standardized on TrueType, OpenType and Type 1 fonts,
PDLs have not. This section describes in detail how our emitters handle fonts.
Using Fonts in PostScript Output
The PostScript language provides direct support for TrueType, OpenType and Type 1 fonts. Not all
PostScript printers support all of the formats and features properly. If you have one of the following,
there may be issues when using fonts:
• Older devices
• Non-Adobe devices
• Transforms
• Post-processing software
These programs usually have problems with support for embedded TrueType Glyphs and large
character sets. Type 1 fonts work on every PostScript device, and they have small character sets.
PostScript printers have a standard set of printer resident fonts that vary with manufacturer, but
usually include Times, Helvetica, Courier, Symbol and Zapf Dingbats.
Emitter Support
By default the xPublish PostScript emitter uses large character sets (Unicode) and embeds TrueType
Glyphs. Large character set fonts are downloaded using subsetting. Any new characters required
for a page are emitted after the last page, and before the page in which they are used. xPression
provides an interface that enables users to define the fonts that are not embedded. xPublish supports
rotation of type in any increment.
Force the Use of Type 1 Fonts
Because Type 1 fonts work on every PostScript device and have small character sets, the easiest
solution for most problems is to exclusively use Type 1 fonts. To force the use of Type 1 fonts, you can
convert your TTF fonts to Type 1 fonts using the procedure below. The resulting .PFB file, along with
the .AFM file, must then be placed in the PSFontPath directory on the server.
Note: The base file name of a converted font file must identically match the base file name of the
original TureType font; otherwise, xPression will not detect the converted Type 1 font, and will
60
Using Fonts
continue to use the TrueType font instead. For example, if the TrueType font name is arial.ttf, then
the converted font files should be named arial.afm and arial.pfb.
Clients (such as Microsoft Word or Adobe InDesign) can then use the TrueType or OpenType version
of the font, while the Type 1 font version will be used when making PostScript output. As long as the
Type 1 font has been created and installed, it will be used when making PostScript output.
Converting TTF and OTF Fonts to Type 1
This section provides you with the instructions necessary to convert TTF and OTF
fonts to Type 1 using software available for download at no cost.
1.
First, you must download TTF2PT1. TTF2PT1 is a font converter that converts fonts from the True
Type format (and some other formats supported by the FreeType library) to the Adobe Type1
format. You can download the program from the following web site:
http://gnuwin32.sourceforge.net/packages/ttf2pt1.htm
Download the Binaries and the Dependencies zip file.
2.
Next, unzip the TTF2PT1 binaries zip file to a directory on the computer where the font
conversion will be performed.
3.
Next, unzip the dependencies zip file to the same directory.
4.
You should see a sub-directory named Manifest. Copy the files from that directory to the /bin
directory. The /bin directory is where the executable file is located.
The directory structure should resemble the following image.
5.
Launch a command prompt and navigate to the bin directory you have just created.
61
Using Fonts
For this example, we created a ttf2pt directory located at C:\ttf2pt
.
6.
For each font you wish to convert type the following line (or put them all in a batch file) and
press Enter:
Ttf2pt1 -b <font path and name>
where <font path and name> is the path and file name of the True Type font you want
to convert.
If you copied your Arial font to the temp directory, your command would look like this:
ttf2pt1 -b c:\temp\arial.ttf
You should now have a .PFB and a .AFM file in the c:\temp directory.
Using Fonts in PDF Output
The PDF format provides direct support for TrueType, OpenType and Type 1 fonts. xPression
supports rotation of type in any increment. The PDF emitter will embed fonts in TrueType,
OpenType, and Type 1 formats. The emitter will always embed subsets for fonts to reduce file size.
Embedding Fonts in xPublish
We have expanded the range of characters that can be used without being embedded in an output
PDF. Originally, xPression enabled you to publish a PDF without embedding fonts if all the characters
were within the ASCII range(0-256). Any character that fell outside of that range was embedded.
Now the supported range is expanded to code page 1252. If the character is outside of this range, it
will have to be embedded.
If you want to publish a PDF with no embedded fonts, you must do the following
two steps:
1.
Ensure that all characters fall within the supported range as outlined above.
2.
Set the following two parameters in the DCPI.properties file.
LargeCharacterSet=false
62
Using Fonts
EmbedFont=false
Using Fonts in AFP Output
AFP does not directly support Type 1 fonts. Type 1 fonts must be converted to AFP outline fonts
before they can be used. The AFP language provides for direct support for TrueType and OpenType
fonts as defined by MO:CDA v6, started in 2004. However, in order to use True Type and OpenType
fonts, the spooler (PSF, InfoPrint Manager, Prisma, and so on) and the printer must also support
them. AFP only supports rotation of type in 90 degree increments. AFP does not support kerning,
although it does support letter spacing.
There are several different supported ways to use fonts in your xPression AFP output:
• TrueType fonts can be used, if your printer supports them. There is no conversion necessary, but
some preparation is required. See TrueType Fonts in AFP, page 64 for more information.
• TrueType fonts can be converted to Type 1 using the procedures described in Converting TTF
and OTF Fonts to Type 1, page 61, and then converted to AFP outline fonts using the procedures
described in Converting Type 1 Fonts into AFP Outline Fonts, page 67. For more information,
see Manually Converting TrueType to AFP Outline, page 65.
63
Using Fonts
• xPression can automatically convert TrueType fonts to AFP outline fonts. To automatically convert
TrueType fonts, ensure that the Embed Fonts in TrueType Format option is NOT selected on
the output definition.
If Embed Fonts in TrueType Format is NOT selected the font will be converted to an AFP outline
font automatically if the following conditions are met:
— The AFP codepage IS in the AFPFontCache folder
— The TrueType font IS in the expected location
— The font is NOT identified in dcpi.properties
xPression supports the use of AFP fonts that meet the following characteristics:
• Must be an AFP Outline font
• Must have been created from TrueType font masters stored in the xPression Repository
• Supports double-byte (Unicode) through TTF fonts and single-byte through AFP Outline fonts
• Fonts must use the Latin alphabet
TrueType Fonts in AFP
TrueType fonts can be used in AFP output (if the printer and spooler support them), so there is no
need to convert the fonts to AFP outline format, but some preparation is required. First it is necessary
to take some steps to prepare the environment.
To prepare the environment to use TrueType fonts:
1.
In xAdmin, open Resource Management, and then open the Font Utility. Delete any font
mappings that reference AFP outline fonts.
2.
In xAdmin, open Publish Output Management, and then open Output Definitions. Open the
output definition to be used with the document and remove any fonts listed in the Do Not
Embed Font List.
3.
Use Windows Explorer to open the \xPression\Publish\AFPFontCache folder and remove any
AFP outline fonts that are stored there.
4.
Ensure that the appropriate TrueType fonts are loaded in \Windows\Fonts .
Support for embedded TrueType fonts must be enabled at the AFP printer. This is an option on some
AFP printers. It is also possible to use TrueType fonts without embedding. See Creating AFP Files
that Do Not Embed Fonts, page 68.
When the environment is prepared, and the document using the special fonts is referenced and saved
in xDesign, xPression will automatically populate the TrueType fonts in the Font Management Utility,
located in xAdmin’s Resource Management page. xPression will also place copies of the TrueType
fonts in the \xPression\Publish\FontCache folder.
When publishing to an output profile that references the output definition modified above, the
TrueType fonts will be embedded in the AFP output file.
64
Using Fonts
Manually Converting TrueType to AFP Outline
If your AFP printer doesn’t support TrueType fonts, and you don’t want xPression to automatically
convert the fonts, you can manually convert TTF fonts to AFP outline fonts. Manually converting the
fonts gives you more control over the process, and enables you to name the resulting fonts.
To convert TTF to AFP outline:
1.
Upload your TTF fonts to the xPression Server, using the steps in The Font Management Utility,
page 57.
2.
Convert the TTF fonts to Type 1 using the procedures described in Converting TTF and OTF
Fonts to Type 1, page 61.
3.
Convert the Type 1 font to AFP outline using the procedures described in Converting Type 1
Fonts into AFP Outline Fonts, page 67.
4.
Upload the AFP font to the xPression Server, using the steps in The Font Management Utility,
page 57.
Bullet Characters
If you are using xPublish as your publisher to produce AFP output and need to create a bulleted
list, you must use the T1001252 codepage because the recommended codepage, T1001148, does
not include a bullet character.
AFP Foreign Language Support
The AFP emitter provides the ability to convert TrueType fonts into AFP Outline or bitmap fonts.
During the outline font conversion process, the AFP emitter creates custom code pages in order to
support the required Unicode characters in a reduced AFP Outline font.
When converting to outline fonts, in order for bold or italic to be supported, you must start with a
bold or italic TrueType font. For example, to get a bold outline font, you can use arialbd.ttf (Arial
Bold), or to get an italic outline font, you can use ariali.ttf (Arial Italic). Bitmap fonts don’t have this
limitation, they can simulate bold and italic styles from normal fonts.
The following languages are now supported for AFP output:
• Traditional Chinese
• Korean
• Vietnamese
• Tagalog
• Japanese
Note: Some English characters can’t be output in AFP when using the MingLiu (mingliu.ttc) font.
This is a limitation of JDK versions jdk16_18 and jrockit_160_17_R28.0.0–679. To avoid this issue,
ensure that you are using jdk1.6.0_20, jdk1.5.0_14, or jrockit_160_14_R27.6.5-32. Additionally, the
65
Using Fonts
outline conversion of Mingliu is not currently supported well; it is recommended that you use
a bitmap conversion with this font.
When you publish double-byte characters like CJK, you now have the option to convert TrueType
fonts into AFP Outline or bitmap fonts, and embed them into the output file during the publishing
process. You can make your selection while defining an AFP output definition in xAdmin. For
more information, see the xAdmin User Guide.
Thai Fonts in AFP Output
xPression supported the ability to include special Thai (Unicode) characters in AFP output. A
Thai TrueType font, AFP outline font, and codepage must be available to use this feature. Prior to
implementing Thai fonts for AFP output ensure that:
• There is no AFP definition for the font. To verify this, log on to xAdmin, open Resource
Management, and then open Font Utility.
• The font and codepage are not defined in the FontMapping key in Dcpi.properties. Dcpi.properties
is located in the <xPressionHome> installation folder on the xPression Server. For more
information, see the Administering the xPression Server guide.
• You place the codepage file in <xPressionHome>\Publish\AFPFontCache.
To enable using Thai fonts in AFP output:
1.
In xAdmin open the output definition for the AFP output.
2.
Select AFP for Format.
3.
Clear the Embed fonts in TrueType format check box.
4.
Type the name of the code page that was placed in the appropriate AFP font directory in the
Default CodePage field.
5.
Click Save.
The Thai font will be used as appropriate for AFP output. The following characters in AFP are
supported:
• Thai Graphic Characters (BA100000 ~ BZ500000)
• Latin Graphic Characters (LA010000 ~ LZ300000)
• Numeric Decimal Graphic Characters (ND010000 ~ ND102000)
• Numeric Fraction Graphic Characters (NF000000 ~ NF210000)
• Arithmetic Special Graphic Characters (SA000000 ~ SA870000)
• Phonetic Chinese Graphic Characters (SB010000 ~ SB420000)
• Currency Special Graphic Characters (SC010000 ~ SC220000)
• Diacritic Mark Special Graphic Characters (SD110000 ~ SD978000)
• Control Representation Special Graphic Characters (SE010000 ~ SE340000)
• Format Symbols Special Characters (SF010000 ~ SF970001)
• APL Symbol Special Graphic Characters (SL010000 ~ SL870000)
66
Using Fonts
• Miscellaneous Symbols Special Graphic Characters (SM000000 ~ SM990000)
• Supplementary Symbols Special Graphic Characters (SS000000 ~ SS890000)
• Various Symbols Special Graphic Characters (SV010000 ~ SV550000)
• Punctuation Special Graphic Characters (SP010000 ~ SP6100Z0)
If Embed fonts in TrueType format is NOT selected, the font will be converted to AFP automatically
if the following conditions are met:
• The AFP codepage IS in the AFP folder
• The TrueType font IS in the expected location
• The font is NOT identified in dcpi.properties or xPRSConfig.xml
Emitter Support
If your AFP device supports TrueType and OpenType fonts, and your documents only contain
TrueType and OpenType fonts, then fonts are embedded and used transparently. Type 1 fonts must
be converted to AFP outline format.
Converting Type 1 Fonts into AFP Outline Fonts
In order to convert Type 1 fonts to AFP Outline, you will need to use the InfoPrint Type Transformer
provided by Ricoh, or a similar utility. This utility can be downloaded from the IBM Website
(http://www-01.ibm.com/support/docview.wss?uid=psd1P4000840). We will use the InfoPrint Type
Transformer to demonstrate the procedure. Your steps may be different.
To convert fonts using InfoPrint Type Transformer:
1.
Start InfoPrint Type Transformer. The Type Transformer application appears.
2.
Select the typefaces to convert. From this page you should point to the .PFB file you wish
to convert to AFP Outline.
3.
Next, select the character filters.
4.
Make sure you select the code page 1252, and click Open.
5.
Convert the font by providing a job name. The resulting fonts can be found in a subdirectory of
the program installation directory. The font file will have the extension .OLN.
6.
Load the font on the xPression Server. For more information, see The Font Management Utility,
page 57.
67
Using Fonts
Creating AFP Files that Do Not Embed Fonts
You can create an AFP file that only references the fonts used, but does not actually embed all of the
font data, which increases file size. The font resources must be available on the printer. The method
for accessing those font resources when the AFP file is sent to the printer must be implemented
to use this procedure.
If your printer supports TrueType fonts and you intend to use TrueType fonts only, then the only
font requirement is the TrueType (.ttf) version of the font that you want to use. If you intend to use
AFP outline fonts, then you will need the AFP outline (.oln) version of the required font as well as
the TrueType version.
To create an AFP file without embedding fonts:
1.
Import the TrueType font into xAdmin with the Resource Management Font Utility. Refer to the
xAdmin User Guide for instructions on using the Font Utility.
2.
If using AFP outline fonts, load the AFP outline fonts by choosing Add AFP and use the Browse
buttons to navigate to the location of the desired AFP CharSet File and the corresponding AFP
CodePage File. Ensure that the same codepage is selected that was used to create the outline font.
3.
From Publish Output Management select Output Definitions and then select the Output
Definition that you want to use.
4.
Under Do Not Embed Font List click Add and select the font that you do not want to embed.
Repeat as required for all fonts that should not be embedded. If using TrueType fonts only, then
only TrueType fonts need to be added. If using outline fonts, then the corresponding outline font
must be added as well as the TrueType font. This will prevent the fonts from being accessed from
the FontCache folder for the TrueType fonts and the AFPFontCache folder for the AFP outline
fonts.
Important: Ensure that the correct AFP codepage is selected for each outline font that should not
be embedded.
Using Fonts in PCL Output
xPression supports PCL 5. This version does not directly support TrueType, OpenType or Type 1
fonts, nor does it support large character sets. It supports the ISO Latin 1 and WinANSI character
sets. The ISO Latin 1 character set is smaller than the WinANSI character set (and it does not contain
all of the bullet characters). PCL only supports rotations in 90 degree increments.
In PCL, fonts are not selected by a font name; they are selected by describing the font characteristics.
PCL fonts have the following characteristics: symbol set, spacing, height, pitch, style, stroke weight,
typeface and orientation.
Font Characteristic
Description
Symbol Set
This is a character encoding, like ASCII or ISO Latin1. In PCL, the symbol set
19U is the ANSI or Windows Character set.19U is the recommended symbol set
for both xPression and Autograph.
68
Using Fonts
Font Characteristic
Description
Spacing
Spacing is either proportional or fixed. In fixed-spaced fonts, the widths of all
the characters in the font are the same. In proportional spaced fonts, the widths
of each character may vary.
Height
The point size in which to print the font.
Pitch
This characteristic describes the number of characters printed in a horizontal
inch. Pitch applies only to fixed-spaced fonts.
Style
Style defines three characteristics: posture (upright, italic), width (condensed,
normal, expanded, and so forth), and structure (solid, outline, shadow, and
so forth).
Stroke Weight
The thickness of the strokes that compose the characters. For example, stroke
weight may be medium or bold.
Typeface
This characteristic identifies the design of the characters in a font, i.e., how the
characters look. For example, how Arial looks compared to Times New Roman.
A typeface is usually specified by a two to five digit identification number.
Orientation is just rotation. PCL has the usual four rotations for fonts.
Orientation
The rotation of the font.
Emitter Support
The PCL emitter assumes that all PCL printers contain the following resident fonts:
• Arial
• Arial Narrow
• Helvetica
• Helvetica Narrow
• Times New Roman
• AvantGarde
• Bookman
• Century Schoolbook
• Courier
• Courier New
• Garamond
• NewCenturySchlbk
• Palantino
69
Using Fonts
Using PCL Fonts with xPression
TrueType fonts cannot be embedded in PCL output directly. Rather, they must first be converted to
PCL soft fonts and copied to the location identified in the PCLFontPath command in DCPI.properties.
In addition, you need to specify the new PCL soft fonts in the PCLFontMapping command in
DCPI.properties.
To use TrueType fonts in PCL output:
1.
Convert the TrueType font to a PCL soft font using the PCL Font Converter. See Convert
TrueType Fonts to PCL, page 70.
2.
Copy the new PCL soft fonts to the location identified in the PCLFontPath command of
DCPI.properties.
3.
Specify the new PCL soft fonts in the PCLFontMapping command in DCPI.properties. See
Configuring the PCLFontMapping Property, page 71.
Convert TrueType Fonts to PCL
To use other fonts, they must be converted to PCL format. xPression ships with the Autograph Font
Converter that can be used to perform this conversion.
The conversion should be made using the 19U character set which is a subset of the WinANSI
character set. The converted fonts should be placed in the directory specified by the PCLFontPath
property in the Dcpi.properties file. This file is located in the xPressionHome directory (C:\xPression
by default).
Once the PCL font is found in this directory, it is used by the PCL device instead of the TrueType,
OpenType or Type 1 font.
Design clients (Microsoft Word or Adobe InDesign) can still use the TrueType, OpenType or Type 1
version of the font. As long as the converted PCL font is installed on the server, it will be used
when printing PCL.
70
Using Fonts
Configuring the PCLFontMapping Property
To use PCL fonts with xPression, you must specify how your PCL fonts correspond to the TrueType
fonts used in the editor. This is accomplished through the PCLFontMapping property in the
DCPI.properties file. The PCLFontMapping property converts the use of TrueType fonts to the use of
PCL fonts located on the printer or in the directory specified by the PCLFontPath command.
The PCL emitter will only use PCL fonts that are defined by the PCLFontMapping property in the
DCPI.properties file and that exist in the directory defined by the PclFontPath property. If one of the
TrueType font families listed in Emitter Support, page 60 is used but not defined in DCPI.properties,
then the PCL emitter will assume that the user wishes to use a printer resident font with the same
font family name. Otherwise, the PCL emitter will substitute the printer resident version of Arial.
Because PCL fonts are selected by describing the font characteristics, you must map the TrueType
fonts to a description of the font characteristics.
The PCLFontMapping syntax is: PCLFontMapping=font1;font2;font3;...;
where each font consists of seven parameters and each font is separated by a semi-colon. For example:
PCLFontMapping=0,,16602,19U,0,Arial,0;1,,16602,19U,0,Arial,1;2,,16602,19U,0,Arial,2;...;
Parameters
p1 - Font Index ID Number. The unique (and arbitrary) font index ID number. For each font listed,
the value of p1 must be sequential. This value is supplied by the user.
p2 - PCL Font name. This is the name of the file containing the PCL soft font in the PCLFontPath
directory. For a printer resident font, leave this name blank. The path is given by the PCLFontPath
command and the file extension is always ".sft", so the path and file extension should NOT be
specified here.
p3 - The PCL font typeface. This value is NOT required for embedded fonts. For embedded fonts,
simply set the typeface equal to the id number. It is required for printer resident fonts.
p4 - The PCL font symbol set.
p5 - The PCL font pitch. 0 = a proportional spaced font; 1 = a fixed space font
p6 - The TrueType font name. Use the English name for the TrueType font. Use the family name
not the full font name to avoid errors.
p7 - The TrueType font type ID. 0 = regular; 1 = bold; 2 = italic; 3 = bold italic
Fonts and Data Driven Graphics
xPression charting is accomplished using licensed components from a third party (Corda). xPression
charting offers an interactive, WYSIWYG user interface, and a wide variety of chart types. Because the
charting engine is from a third party, it handles fonts and images differently than the rest of xPression.
Corda does not support the fonts installed on the host computer or server. Corda requires
its own set of fonts in a proprietary format based upon the SVG font format. These fonts
71
Using Fonts
have the extension FSD, and will be referenced as FSD fonts. Corda font files are stored in
<xPressionHome>\Publish\Corda\Resources\lib\fsfiles.
You can use Corda Builder to convert TrueType (TTF) fonts to the FSD format. If you require a font in
a chart that is not a TTF, you must convert to font to TTF, then use the Corda font conversion utility
to convert the font to FSD.
The TrueType version of the font should reside in the TrueType font directory on the server. The
directory is determined by the “TtfFontPath=” property in the dcpi.properties file located in the
xPressionHome directory on your server.
Note: Chinese fonts are not supported for use in dynamic charts.
Converting Fonts to FSD Format
To convert a TTF font to the FSD format:
1.
Start Corda Builder.
2.
Click the File menu and select Font Converter.
3.
The Corda Font Converter appears.
4.
In the Conversion Options section, locate the Output folder option. This option enables you
to define the destination directory for the converted fonts. Specify a location or take note of
the default location.
5.
From the Font list, select the font you wish to convert and click the Convert button.
6.
The fonts are converted and placed in the output folder. These fonts can now be used in Builder
to design, build and test your charts.
7.
In order to use these fonts on the server, they must be manually copied to the proper directory.
72
Using Fonts
The directory is determined by the "CordaFontPath=." property in the xPressionPublish.properties
file located in the xPressionHome directory on your server.
8.
Ensure that the TrueType versions of the fonts are located in the proper directory on the server.
The directory is determined by the “TtfFontPath=” property in the dcpi.properties file located in
the xPressionHome directory on your server.
Additionally, the Corda font file (.fsd) must be copied to the following directory:
<xPressionHome>\Publish\Corda\Resources\lib\fsfiles\
73
Using Fonts
74
Chapter 4
Page Description Languages
A page description language (PDL) is a language that describes the appearance of a printed page in a
higher level than an actual output bitmap. xPression supports the following PDLs:
• AFP
• HTML
• PCL
• PDF
• PostScript
• Text
• TIFF
AFP
With version 4.5, xPression introduces a new, more robust AFP emitter. The old AFP emitter (4.2
AFP) is still supported in version 4.5, but it will not be supported in future versions of xPression.
Also, the old emitter does not support any new features for 4.5. To enable the old AFP emitter, use
the EnableOldAFPEmitter property located in the xPressionPublish.properties file. Both emitters
can exist at the same time.
The new and improved AFP emitter uses an AFP output structure that differs from the old emitter.
This improved structure results in a slight increase in output file size. The structure change involves
the inclusion of a “Begin Document” tag at the beginning of each document instead of enclosing each
output file with only one Begin/End Document tag.
The new AFP emitter supports all features of the old emitter and also supports these new features:
• Support for double-byte character sets.
• Support for many more AFP printer features through your PPD file. See the xAdmin User Guide
for more information.
• Support for Page level TLEs. See the xAdmin User Guide for more information.
• xPression can convert images that are in the wrong format for AFP. You can configure xPression’s
response based on your preferred outcome. See the Administering the xPression Server for more
information.
75
Page Description Languages
AFP (Advanced Function Presentation), is an IBM architecture and family of associated printer
software and hardware that provides document and information presentation control independent of
specific applications and devices. xPublish supports “Comment” or NOPS AFP.
Note: In some cases when viewing AFP output with a viewer, rather than direct output, the following
error may occur:
1323: The character set 'CZAH8H' was not found in the 'CSDEF.FNT file. The
default character set will be used.
Not all AFP viewers have been tested, but this error has been noted in all viewers that have been
tested. To avoid the error it is recommended that AFP output be verified by sending the output to
the printer.
For information about AFP fonts, see Using Fonts in AFP Output, page 63.
AFP Foreign Language Support
The xPression AFP emitter has been enhanced in order to better support foreign languages. The
AFP emitter now provides the ability to convert TrueType fonts into AFP Outline or bitmap fonts.
During the outline font conversion process, the AFP emitter creates custom code pages in order to
support the required Unicode characters in a reduced AFP Outline font. AFP outline fonts don’t
support bold or italic styles.
The following languages are now supported for AFP output:
• Traditional Chinese
• Korean
• Vietnamese
• Tagalog
• Japanese
When you publish double-byte characters like CJK, you now have the option to convert TrueType
fonts into AFP Outline or bitmap fonts, and embed them into the output file during the publishing
process. You can make your selection while defining an AFP output definition in xAdmin. For
more information, see the xAdmin User Guide.
Images
See the following topics on images in AFP output:
• Images on the Server, page 77
• JPEG Images, page 77
• xPresso for Adobe InDesign Image Fit Options, page 77
• CMYK Images, page 77
• For image type recommendations for AFP, see General Image Type Recommendations for Your
PDL, page 40.
76
Page Description Languages
• For a list of natively supported image types for AFP, see PDL Native Support, page 28.
• To customize the image format selection for this PDL, see How to Customize the Image Format
Selection, page 37.
Images on the Server
When you place any image into the xPression Repository, xPression automatically generates an image
format compatible with Web output to support previewing the image from xAdmin. To see a table
describing what image format is used for full-color, highlight color, and black and white images, see
How xPression Decides Which Format to Use, page 36.
JPEG Images
If the JPEG (.jpg, .jpeg) image has an irregular format, the xPublish publishing engine will not be
able to use it to produce PostScript or AFP output. A JPEG image is “irregular” if it contains one
of the following:
• More than one SOI (Start of Image: FFD8) tag. This tag should appear only once at the beginning
of the file.
• More than one SOS (Start of Scan: FFDA) tag. This tag indicates the beginning of the image scan.
You can use a utility such as IrfanView (http://www.irfanview.com/) to re-save irregular JPEG
images, and then use the newly saved images in your document.
xPresso for Adobe InDesign Image Fit Options
The xPresso for Adobe InDesign Image Fit options are not support for xPression with AFP or PCL
output.
CMYK Images
xPression supports only one type of CMYK image.for AFP output: CMYK TIFF images using LZW
compression.
Building TLE Items
AFP TLEs are defined at the output stream level in an output definition. xPublish configuration of
TLEs is done entirely through the output definition page in xAdmin. The output definition enables
you to define the name of a TLE, the TLE level, and the TLE value. To apply these TLEs to your
documents, simply publish the document with a stream that uses the output definition that contains
77
Page Description Languages
your TLE settings. If you want to define different TLE values or publish the same document without
TLEs, you will need to create separate output definitions for each scenario.
Note: (1) Only EBCDIC characters are supported in TLE items. (2) Variables are not supported in TLE
items when imposition is used in the output. (3) Non-latin characters are not supported.
AFP PPD Files
Printer definitions use your print device PPD file to identify all of the features and settings
supported by the device. PostScript printers have their own description files, which should have
come with the printer. For AFP printers, you can use one of the supplied PPD files, located in
xPressionHome\publish\ppd:
• Afpgeneral.ppd — for use with the new AFP emitter only.
• Afpbwcs.ppd — for black and white cut-sheet AFP printers.
• Afpbwrf.ppd — for black and white roll-fed AFP printers.
• Afpccs.ppd — for color cut sheet AFP printers.
• Afpcrf.ppd — for color roll-fed AFP printers.
Reverse Printing
When creating AFP output on the xPression Server, you can use the Reverse Printing feature. When
this feature is enabled, the order of the printed documents in the output stream will be reversed. For
example, instead of printing pages 1, 2, and 3, it will print in reverse order 3, 2, and 1.
For more information, see the xAdmin User Guide.
Rotating Pages
When creating AFP output on the xPression Server, you can use the Rotate Pages 180 feature on the
stream definition. When this feature is enabled, the pages in the output stream will be rotated 180
degrees. When used with AFP, the rotation value you specified in the content stamp definition will be
ignored. For more information, see the xAdmin User Guide.
Resource IDs
xPression uses Resource IDs internally to manage resources, such as images and fonts, when
publishing AFP output. By default new resource IDs are unique within a single document only, but
xPression provides an option to ensure that the same resource ID is used across multiple batch runs.
Unique identifiers supports combining multiple AFP print files into a single file, and thereby realize
greater postal discounts and reduce printer setup time.
78
Page Description Languages
Caution: The following property must be present in Dcpi.properties, even if the feature is not
used. If the property is missing AFP jobs will fail with a java.lang.NullPointerException error.
This feature is controlled by a single new property in Dcpi.properties:
UseUnifiedResourceIDForAFP=false
This feature impacts the auto generation of AFP outline fonts, so it is necessary to clear any
existing AFP fonts and their history prior to using this feature and whenever the value of
UseUnifiedResourceIDForAFP is changed. To clear existing AFP fonts:
1.
Locate and open TTF2AFPMAP from xPressionHome/Publish/AFPFontCache.
2.
Remove all existing fonts and associated histories.
3.
Save the modified TTF2AFPMAP file.
The next time AFP output is published the fonts will be regenerated with the new name.
When UseUnifiedResourceIDForAFP is TRUE the feature is invoked. Set the value of this property
to FALSE to suppress the feature and avoid the possibility of unexpected changes in output. For
example, if the document was developed and published successfully with prior versions, set this
property to FALSE to ensure output consistent with the prior versions.
To support using unified resource IDs, DDG and barcode images are embedded inline so that
resource IDs are not required for these images.
Limitations
The following restrictions and limitations apply to the unified resource ID feature:
• This feature applies to xPublish documents only.
• This feature relies on auto-increment ID by repository, so resource IDs are not carried to other
xPression Repositories, such as when migrating documents to other environments.
• DDG and barcode images must be JPEG. To ensure that JPEG is used, specify “JPEG” as the
image preference in dcpi.properties under ImagePreferenceForAFP or in xAdmin under Stream
Definition.
• Regenerating InDesign packages will change the name of images stored in the package, and so
will cause the resource ID for AFP to change as well.
Mixed Orientation AFP Output
xPression supports portrait and landscape page layouts in AFP output. Some printers also support
landscape page layout. The SimulateLandscapePageOnPortraitPaper in dcpi.properties ensures that
the desired orientation can be produced on any printer. Refer to Administering the xPression Server
for information on dcpi.properties.
79
Page Description Languages
SimulateLandscapePageOnPortraitPaper can be either TRUE or FALSE. When TRUE landscape pages
(pages that are wider than they are tall) are rotated 270º CW. When FALSE pages are not rotated.
The default value is FALSE.
Limitations
The following limitations apply:
• Simulates landscape orientation on portrait paper by rotating 270º CW only: other rotations are
not supported.
• This feature does not rotate content stamps.
• This feature does not support Tumble Page.
Rotated Frames in AFP Output
The AFP emitter was enhanced to support xPresso for Adobe InDesign frame rotation.
• The AFP emitter supports the following frame rotation values: 0, –90, 180, 90. If the frame is
rotated to a different value, the frame will not be rotated in the AFP output.
• The AFP emitter does not support filled frames that are rotated, but does support filled frames
that are not rotated.
• When nesting frames, embedded text and tables can only be rotated by the frame that directly
contains the text or table. Also, the tables or text can only be rotated to the four rotation values
listed above.
HTML
To customize the image format selection for this PDL, see How to Customize the Image Format
Selection, page 37.
PCL
PCL (Printer Command Language) is a PDL developed by HP as a printer protocol and has become
widely used. Originally developed for early inkjet printers in 1984, PCL has been released in varying
levels for thermal, matrix printer, and page printers. xPression supports PCL 5.
Note: If blank pages are generated during publishing of PCL output, the generated blank pages
will not be shown in the PCL Reader viewer.
80
Page Description Languages
PCL Font Support
PCL 5 does not directly support TrueType, OpenType or Type 1 fonts, nor does it support large
character sets. It supports the ISO Latin 1 and WinANSI character sets. The ISO Latin 1 character set
is smaller than the WinANSI character set (and it does not contain all of the bullet characters). PCL
only supports rotations in 90 degree increments.
TrueType fonts cannot be embedded in PCL output directly. Rather, they must first be converted to
PCL soft fonts and copied to the location identified in the PCLFontPath command in DCPI.properties.
In addition, you need to specify the new PCL soft fonts in the PCLFontMapping command in
DCPI.properties.
The PCL emitter assumes that all PCL printers contain the following resident fonts:
• Arial
• Arial Narrow
• Helvetica
• Helvetica Narrow
• Times New Roman
• AvantGarde
• Bookman
• Century Schoolbook
• Courier
• Courier New
• Garamond
• NewCenturySchlbk
• Palantino
To use other fonts, they must be converted to PCL format. xPression ships with the Autograph Font
Converter that can be used to perform this conversion.
Images in PCL
See the following items about image support for PCL output:
• The xPresso for Adobe InDesign Image Fit options are not support for xPression with AFP
or PCL output.
• PCL 5 does not support color (black and white only), and only supports black and white TIFF
images. To get images to output in PCL, you must start with a G4 Tiff image.
• To see a table describing what image format is used for full-color, highlight color, and black and
white images, see How xPression Decides Which Format to Use, page 36.
• For image type recommendations for PCL, see General Image Type Recommendations for Your
PDL, page 40.
81
Page Description Languages
• For a list of natively supported image types for PCL, see PDL Native Support, page 28.
• To customize the image format selection for this PDL, see How to Customize the Image Format
Selection, page 37.
•
PCL PPD Files
Printer definitions use your print device PostScript Printer Description (PPD) file to identify all of the
features and settings supported by the device. Markers identify places in the document where you
would like to implement a feature or set of features.
Document Sciences supplies a PPD file for PCL printers, Pclbw.ppd. It is located in the following
xPressionHome subdirectory: <xPressionHome>\xPRS\xPRS_home\PPD
Use this PPD file for general purpose, black and white PCL printers.
PDF
The Portable Document Format (PDF) is a file format created by Adobe Systems for document
exchange. PDF is a fixed-layout format used for representing two-dimensional documents in a
manner independent of the application software, hardware, and operating system. PDF captures
formatting information from a variety of desktop publishing applications, making it possible to
send formatted documents and have them appear on the recipient’s monitor or printer as they were
intended.
With version 4.5, xPression introduces a new, more robust PDF emitter. The PDF emitter used
in version 4.2 is still supported in xPression 4.5, but will not be supported in the next version of
xPression. Users should migrate to the new PDF emitter and use the old PDF emitter to comparison
test.
The old emitter is not enabled by default. To enable the old emitter to work alongside the new
emitter, update the EnableOldPDFEmitter property in xPressionPublish.properties located in your
xPressionHome directory. When both emitters are enabled in xAdmin, the old emitter is labeled “4.2
PDF” and the new emitter is labeled ”PDF”. You can still use existing “4.2 PDF” Output Definitions
when the old emitter is disabled, but you cannot create new “4.2 PDF” Output Definitions.
See the xAdmin User Guide for more information about creating PDF output.
82
Page Description Languages
Using PDF in xPression
When creating PDF output in xPression, you cannot use Printer Resident Images because the format
does not use a physical printer to produce the output. However, you can add the following properties
to your PDF output:
• Encryption - You can encrypt your PDF to enable or prohibit the recipient of the PDF from
performing certain functions with the file.
• Document Properties - such as Title, Author, Creation date, and more.
• Viewer Preferences - Control the way the Acrobat viewer displays the PDF file.
• PDF bookmarks - The PDF Bookmarks feature is not supported for documents that use imposition.
• Compress Fonts in the PDF - This option compresses embedded fonts. File size is reduced but
processing time is longer.
To learn about these features, see the xAdmin User Guide.
Note: If you want to create PDF/A output in xPression and have a large amount of customer data for
your document, select the Individual print file for each customer option in your output definition;
otherwise, an out-of-memory error might occur. For more information about the Individual print file
for each customer option, see xAdmin User Guide.
Fonts in PDF
The PDF format provides direct support for TrueType, OpenType and Type 1 fonts. xPression
supports rotation of type in any increment. The PDF emitter will embed fonts in TrueType,
OpenType, and Type 1 formats. The emitter will always embed subsets for fonts to reduce file size.
If you use Type 1 fonts with PDF/A or PDF/X output, the PDF will be published, but your PDF may
fail to pass a PDF/A or PDF/X compliance test.
Embedding Fonts in xPublish
We have expanded the range of characters that can be used without being embedded in an output
PDF. Originally, xPression enabled you to publish a PDF without embedding fonts if all the characters
were within the ASCII range (0-256). Any character that fell outside of that range was embedded.
Now the supported range is expanded to code page 1252. If the character is outside of this range, it
will have to be embedded.
If you want to publish a PDF with no embedded fonts, you must do the following
two steps:
1.
Ensure that all characters fall within the supported range as outlined above.
2.
Set the following two parameters in the DCPI.properties file.
LargeCharacterSet=false
EmbedFont=false
83
Page Description Languages
Images in PDF
PDF is viewed using Adobe Acrobat. Acrobat is an RGB RIP. It takes PDF files, which are in a metafile
format, rasterizes them to screen resolution in RGB, and displays them on your monitor. When
printing from Acrobat, the print driver converts the PDF into a PDL appropriate for your printer.
To see a table describing what image format is used for PDF output, see How xPression Decides
Which Format to Use, page 36. For image type recommendations for PDF, see General Image Type
Recommendations for Your PDL, page 40. For a list of natively supported image types for PDF, see
PDL Native Support, page 28. To customize the image format selection for this PDL, see How to
Customize the Image Format Selection, page 37.
The PDF emitter does not convert your images to the required color space for your PDF type. If you
are publishing PDF/A or PDF/X, ensure that your source image matches the color space required
by your output PDF type. For example, if you are publishing in PDF/A-1b, you should ensure all of
your source images use CMYK instead of RGB.
ICC Color Profiles
ICC color profiles embedded in images are supported in PDF but not in other streams. ICC color
profiles are not honored when images are resampled. For this reason, do not use Resampling with
color managed images.
Reverse Printing
When creating PDF output you can use the Reverse Printing feature. When this feature is enabled,
the order of the printed documents in the output stream will be reversed. For example, instead of
printing pages 1, 2, and 3, it will print in reverse order 3, 2, and 1.
For more information, see the xAdmin User Guide.
Rotating Pages 180 Degrees
When creating PDF output you can use the Rotate Pages 180 feature. When this feature is enabled,
the pages in the output stream will be rotated 180 degrees. For more information, see the xAdmin
User Guide.
PostScript
PostScript was developed by Adobe Systems. It is a PDL optimized for printing images and text
documents. For PostScript output you can resample images to the output resolution, use fonts
stored in your printer memory, and define the following properties for your output: Title, Author,
Subject, Keywords, and Creator.
84
Page Description Languages
For more information, see the xAdmin User Guide.
PostScript PPD Files
Printer definitions enable you to configure your output devices by specifying settings for your printer
and identifying printer resident images. Printer definitions use your print device PostScript Printer
Description (PPD) file to identify all of the features and settings supported by the device.
PPD files are created by vendors to describe the entire set of features and capabilities available for
their PostScript printers. A PPD also contains the PostScript code (commands) used to invoke features
for the print job. As such, PPDs function as drivers for all PostScript printers, by providing a unified
interface for the printer’s capabilities and features.
You can import PPD files through a Printer definition in xAdmin. Once the PPD is imported, all the
printer functions described in the PPD file are available to be mapped to Markers. Markers are placed
at locations in your document or in your document stream to initiate the mapped printer function.
For more information, see the xAdmin User Guide.
Reverse Printing
When creating PostScript output on the xPression Server, you can use the Reverse Printing feature.
When this feature is enabled, the order of the printed documents in the output stream will be
reversed. For example, instead of printing pages 1, 2, and 3, it will print in reverse order 3, 2, and 1.
For more information, see the xAdmin User Guide.
Rotating Pages 180 Degrees
When creating PostScript output on the xPression Server, you can use the Rotate Pages 180 feature.
When this feature is enabled, the pages in the output stream will be rotated 180 degrees. For more
information, see the xAdmin User Guide.
Images in PostScript
To see a table describing what image format is used for PostScript output, see How xPression Decides
Which Format to Use, page 36. For image type recommendations for PostScript, see General Image
Type Recommendations for Your PDL, page 40. For a list of natively supported image types for
PostScript, see PDL Native Support, page 28. To customize the image format selection for this PDL,
see How to Customize the Image Format Selection, page 37.
85
Page Description Languages
PPML
PPML (Personalized Print Markup Language) is a device-independent standard that enables the
widespread use of personalized print applications in high volume. The XML-based printer language
enables printers to manage variable data by sending all the data to the printer at once, making for
much faster printing. PPML makes the reuse of resources (reusable content) explicit, and enables the
printer to know which resources are required at particular points in the job.
Text
xPression can produce output for text-only devices such as text files, plain text emails, Short
Message Service (SMS) devices, and reports. When output is sent through a Text output definition,
it is assumed that the text will not be printed directly. Text output will be formatted for use as
input to a computerized system such as email, notepad, or free text in a database. No pagination
related functions are applied to the output, and all page-level formatting is removed. For example,
xPression will ignore all headers and footers, hyphenation, tables of contents, leader characters,
and page numbering.
The following list identifies the formatting options that are supported through Text output definitions.
Formatting
Definition
Line Wrapping
Line breaks and carriage return characters (lf/cr) are supported for the purpose
of breaking long lines.
Character Sets
Supports ASCII, EBCDIC, Unicode, and any other character sets supported by
xPublish.
Tables
Table cells are delimited by either tabs or paragraphs. This option is configurable.
Bullets
All bullets are converted to asterisks (*). Indented bulleted lists will receive tab
characters to duplicate the indentation.
Numbered Lists
Numbered lists are supported. Indented numbered lists will receive tab characters
to duplicate the indentation.
TIFF
TIFF output definitions enable you to send your output to archive systems, fax servers, and other
electronic systems as an image file. xPression uses the TIFF format for the output image because TIFF
provides the highest quality image and also supports compression. xPression can produce these
images at various bit depths and with various compression methods.
You can choose from three different bit depths: 1 (binary), 8 (grayscale), and 24 (RGB). You can also
choose from four different compression methods: CCITT T.6, Uncompressed, LZW, and Pack Bits.
86
Page Description Languages
Note: The OpenType font ZapfDingbatsStd.otf is not supported for TIFF output because it is
not supported by Multivalent, an open source tool used by xPression. EMC Document Sciences
recommends replacing it with the Wingdings font.
87
Page Description Languages
88
Chapter 5
Glossary
Adobe Type 1 Fonts
Type 1 fonts were developed by Adobe as the initial native font format for PostScript and the
Apple LaserWriter in 1985. Type 1 fonts are composed of two files. One contains the glyphs, and
the other the font metrics. PFB, PFM and AFM files are used to store Type 1 fonts on all platforms
except Macintosh. The Type 1 format supports 256 characters, and is not capable of describing
large character set fonts.
Bit Depth
Bit depth is the number of colors you can use in a digital image. With a binary image (1 bit per pixel),
you have only one color - black (the paper is white). With a CMYK image (32 bit per pixel) can use
up to 4,294,967,296 different colors.
Embedding
The strategy of embedding fonts directly within a document. Documents that contain embedded
fonts can be reproduced faithfully by using the embedded fonts. When rendering the document,
the font is extracted and fed to the font machinery of the rendering mechanism (PDF, PostScript,
AFP, etc.). When embedding fonts, the output files must contain fonts that can range from 20k to
20MB depending on the number of characters.
Encoding
Encoding is the association of a number with a glyph in a font. Characters in text are represented
by numeric values. When you press a key on a keyboard, you are really entering a number into the
computer. The computer takes that number and using the encoding of the font, matches it up to a
little drawing of a character for you. This is encoding.
89
Glossary
Font Metrics
Font metrics define information such as character width and height. Applications that use fonts
generally stack characters up against each other. Typically the space defined by the font metric is
wider than the actual glyph, otherwise characters would touch or overlap.
Glyphs
A glyph is the shape given in a particular typeface to a specific symbol. It is a particular graphical
representation of a character. Think of a font as a lot of very carefully drawn little drawings. The
glyph is this little drawing. Different fonts have a different number of glyphs. For example, a font can
contain a full western character set as well as a full Chinese character set.
ICC Color Profiles
Color management is the controlled conversion between the color representations of various devices
(such as digital cameras, monitors, TV screens, film printers, computer printers, and offset presses)
and corresponding media.
The primary goal of color management is to obtain a good color match across devices such as printers
and monitors. This goal is accomplished by measuring the response of each color managed device
and compensating for its inaccuracies when displaying colors. Each managed device has an ICC
(International Color Consortium) profile that describes its response. ICC color profiles embedded in
images are supported in PDF but not in other streams.
Note: ICC color profiles are not honored when images are resampled. For this reason, do not use
Resampling with color managed images.
Kerning
Kerning is the adjustment of the spacing between two specific characters when they appear together.
Lossless Compression
Lossless compression refers to compression techniques in which no data is lost. The PKZIP, ZIP, and
TAR compression technologies are example of lossless compression. For most types of data, lossless
compression techniques can reduce the space needed by only about 50%. These compression schemes
encode redundant data with a description of that data.
90
Glossary
Lossy Compression
Refers to data compression techniques in which some amount of data is lost. Lossy compression
technologies attempt to eliminate redundant or unnecessary information. When you compress and
decompress data with lossy compression, you may retrieve data that is different from the original, but
close enough to be useful in some way. Lossy compression is most commonly used to for to compress
multimedia data (MP3, video, JPEG). While you lose data, the benefits to file size are substantial.
Page Description Language (PDL)
Page Description Languages (PDLs) are languages for describing the layout and contents of a printed
page.
Pixels
Picture Element (Pixel) is the most basic part of any imaging device. Pixels exist on Television,
computer monitors, digital cameras and printers. All of these devices display digital images.
Resolution
Resolution is the number of pixels per unit measure of an image when displayed on a particular
imaging device.
Spot Color
Spot or highlight color models do not attempt to recreate all colors, instead each color is printed with
its own ink. pot color is used when a process color (CMYK equivalent) is not sufficient. For example,
if you are Coke, there is a specific "Coke Red" color that is required. If you are printing a color
brochure, you will use CMYK plus a spot color in "Coke Red." The spot color will only be used when
printing the logo or other things that you specifically want in that color.
Even though 5 colors are being used, the 5th color is NOT used in combination with CMYK, is used in
specific spots to provide an exact color match. It is not uncommon in high-end print applications to
use many spot colors in addition to CMYK. When generating output, each highlight or spot color is
given its own 8-bit image (256 shades).
In offset printing there are a number of ink vendors who sell specific colors of ink (For example,
Pantone and Focoltone). PMS (Pantone Matching System) colors are very commonly used as spot
color. When offset printing, you can use black plus one spot to be equivalent to digital highlight color,
also at a much lower production cost.
91
Glossary
Subsetting
Subsetting embeds only the glyphs used instead of embedding the entire font. For example, many
Unicode fonts contain Arabic and Chinese characters. If you are producing a document in German,
you do not need to include these characters.
Unicode
For large character sets xPression uses Unicode encoding. Unicode is an industry standard allowing
computers to consistently represent and manipulate text expressed in any of the world’s writing
systems. The standard itself describes quite a few concepts, the most important for the purposes of
this document is the ability to address and manipulate about 100,000 characters in any of the world’s
writing systems in a standard way.
WINANSI
For single byte fonts xPression uses WinANSI code page 1252 encoding. Windows-1252 is a character
encoding of the Latin alphabet used by default in the legacy components of Microsoft Windows
in English and some other Western languages.
92