PDF Reference sixth edition, Adobe Portable Document Format Version 1.7 (book 2) — page 14
1123
SECTION H.3
Implementation Notes
9.1, “Multimedia”
148. The following media formats are recommended for use in authoring
cross-platform PDF files intended for consumption by Acrobat 6.0.
TABLE H.4 Recommended media types
COMMON EXTENSION COMMON MIME TYPE
DESCRIPTION
.aiff
audio/aiff
Audio Interchange File Format
.au
audio/basic
NeXT/Sun™ Audio Format
.avi
video/avi
AVI (Audio/Video Interleaved)
.mid
audio/midi
MIDI (Musical Instrument Digital Interface)
.mov
video/quicktime
QuickTime
.mp3
audio/x-mp3
MPEG Audio Layer-3
.mp4
audio/mp4
MPEG-4 Audio
.mp4
video/mp4
MPEG-4 Video
.mpeg
video/mpeg
MPEG-2 Video
.smil
application/smil
Synchronized Multimedia Integration Language
.swf
application/x-shockwave-flash Macromedia Flash
149. If the CT entry is not present, Acrobat requires a PL entry to be present
that specifies at least one player that can be used.
9.2, “Sounds”
150. Acrobat supports a maximum of two sound channels.
9.3, “Movies”
151. Acrobat viewers do not support the value of Aspect.
152. Acrobat viewers support only the DeviceRGB and DeviceGray color spaces
for poster image XObjects. For indexed color spaces with a base color
space of DeviceRGB (see “Indexed Color Spaces” on page 262”), Acrobat
5.0 viewers incorrectly treat hival as the number of colors rather than the
1124
APPENDIX H
Compatibility and Implementation Notes
number of colors - 1. Acrobat 6.0 can handle this case properly, as well as
the correct value of hival; for compatibility with 5.0 viewers, it is necessary
to specify hival as the number of colors.
Also, Acrobat viewers do not support authoring or rendering posters
when the value of Poster is true.
153. Acrobat viewers treat a FWScale value of [999 1] as full screen.
154. Acrobat viewers never allow any portion of a floating window to be off-
screen.
9.4, “Alternate Presentations”
155.
The PDF language contains no direct method of initiating an alternate
presentation-defined slideshow. Instead, a slideshow is invoked by a
JavaScript call that is typically triggered by an interactive form element
(see Section 8.6, “Interactive Forms”). Refer to the JavaScript for Acrobat
API Reference (see the Bibliography) for information on starting and stop-
ping a slideshow using JavaScript.
156.
The only type of slideshow supported in Acrobat 5.1 and later is an SVG
slideshow (MIME content type image/svg+xml). Acrobat supports the
Scalable Vector Graphics (SVG) 1.0 Specification defined by the W3C (see
the Bibliography). Implementation notes on support of SVG by Adobe
products are available at <http://www.adobe.com/svg/>.
All resources must be either image XObjects (see Section 4.8.4, “Image
Dictionaries”) or embedded file streams (see Section 3.10.3, “Embedded
File Streams”).
• Image XObjects used for slideshows must use the DCTDecode filter and
an RGB color space. Color profile information must be specified in the
image XObject dictionary as well as embedded within the JPEG stream.
• Embedded audio files must be of type .wav (supported on Windows
only, MIME type audio/x-wav) or .mp3 (MIME type audio/mpeg, docu-
mented at <http://www.chiariglione.org/mpeg/index.htm>).
• Embedded video must be QuickTime-compatible files of type .avi
(MIME type video/ms-video) or .mov (MIME type video/quicktime,
documented on Apple’s Developer Connection site at <http://develop-
er.apple.com>. To play video, a QuickTime player (version 3 or later)
must be installed.
1125
SECTION H.3
Implementation Notes
9.5, “3D Artwork”
157. Acrobat viewers earlier than version 7.0.7 did not honor the U3DPath en-
try of a 3D view dictionary. Acrobat 7.0.7 supports text string values for
this entry and deprecates the use of an array for its value.
158. PDF 1.7 introduced several new dictionaries for controlling the appear-
ance and behavior of 3D artwork and for enabling markup annotations on
3D views. Although Acrobat 7.0 officially supports PDF 1.6, Acrobat 7.0.7
also supports these new dictionaries.
10.1, “Procedure Sets”
159. Acrobat viewers earlier than version 5.0 respond to requests for unknown
procedure sets by warning the user that a required procedure set is un-
available and canceling the printing operation. Acrobat 5.0 ignores proce-
dure sets.
10.2, “Metadata”
160. Acrobat viewers display the document’s metadata in the Document Prop-
erties dialog box and impose a limit of 255 bytes on any string represent-
ing one of those values.
10.2.2, “Metadata Streams”
161. For backward compatibility, applications that create PDF 1.4 documents
should include the metadata for a document in the document information
dictionary as well as in the document’s metadata stream. Applications that
support PDF 1.4 should check for the existence of a metadata stream and
synchronize the information in it with that in the document information
dictionary. The Adobe metadata framework provides a date stamp for
metadata expressed in the framework. If this date stamp is equal to or later
than the document modification date recorded in the document informa-
tion dictionary, the metadata stream can be taken as authoritative. If, how-
ever, the document modification date recorded in the document
information dictionary is later than the metadata stream’s date stamp, the
document has likely been saved by an application that is not aware of PDF
1.4 metadata streams. In this case, information stored in the document in-
formation dictionary should be taken to override any semantically equiva-
lent items in the metadata stream.
1126
APPENDIX H
Compatibility and Implementation Notes
10.3, “File Identifiers”
162. Although the ID entry is not required, all Adobe applications that produce
PDF files include this entry. Acrobat adds this entry when saving a file if it
is not already present.
163. Adobe applications pass the suggested information to the MD5 message
digest algorithm to calculate file identifiers. Note that the calculation of
the file identifier need not be reproducible; all that matters is that the
identifier is likely to be unique. For example, two implementations of this
algorithm might use different formats for the current time, causing them
to produce different file identifiers for the same file created at the same
time, but the uniqueness of the identifier is not affected.
10.9.2, “Content Database” (Digital Identifiers)
164. The Acrobat Web Capture plug-in treats external streams referenced with-
in a PDF file as auxiliary data. Such streams are not used in generating the
digital identifier.
10.9.3, “Content Sets” (Image Sets)
165. In Acrobat 4.0 and later versions, if the indirect reference to an image
XObject is not removed from the O array when its reference count reaches
0, the XObject is never garbage-collected during a save operation. The im-
age set’s reference to the XObject may thus be considered a weak one that
is relevant only for caching purposes; when the last strong reference goes
away, so does the weak one.
10.9.4, “Source Information” (URL Alias Dictionaries)
166. Acrobat viewers use an indirect object reference to a shared string for each
URL in a URL alias dictionary. These strings can be shared among the
chains and with other data structures. It is recommended that other PDF
viewer applications adopt this same implementation.
10.10.1, “Page Boundaries”
167. Acrobat provides various user-specified options for determining how the
region specified by the crop box is to be imposed on the output medium
1127
SECTION H.3
Implementation Notes
during printing. Although these options have varied from one Acrobat
version to another, the default behavior is as follows:
1. Select the media size and orientation according to the operating sys-
tem’s Print Setup dialog. (Acrobat has no direct control over this pro-
cess.)
2. Compute an effective crop box by clipping it with the media box and
rotating the page according to the page object’s Rotate entry, if speci-
fied.
3. Center the crop box on the medium, rotating it if necessary to enable
it to fit in both dimensions.
4. Optionally, scale the page up or down so that the crop box coincides
with the edges of the medium in the more restrictive dimension.
The description above applies only in simple printing workflows that lack
any other information about how PDF pages are to be imposed on the
output medium. In some workflows, there is additional information, ei-
ther in the PDF file (BleedBox, TrimBox, or ArtBox) or in a separate job
ticket (such as JDF or PJTF). In these circumstances, other rules apply,
which depend on the details of the workflow.
Consequently, it is recommended that PDF files initially be created with
the crop box the same as the media box (or equivalently, with the crop box
omitted). This ensures that if the page is printed on that size medium, the
crop box coincides with the edges of the medium, producing predictable
and dependable positioning of the page contents. On the other hand, if the
page is printed on a different size medium, the page may be repositioned
or scaled in implementation-defined or user-specified ways.
10.10.4, “Output Intents”
168. Acrobat viewers do not make use of the “to CIE” (AToB) information in an
output intent’s ICC profile.
169. Acrobat 5.0 does not make direct use of the destination profile in the out-
put intent dictionary, but third-party plug-in extensions might do so. Ac-
robat 6.0 does make use of this profile.
1128
APPENDIX H
Compatibility and Implementation Notes
10.10.5, “Trapping Support” (Trap Network Annotations)
170. Older viewers may fail to maintain the trap network annotation’s required
position at the end of the Annots array.
171. Older viewers may fail to validate trap networks before printing.
172. In Acrobat 4.0, saving a PDF file with the Optimize option selected causes
a page’s trap networks to be incorrectly invalidated even if the contents of
the page has not been changed. This occurs because the new, optimized
content stream generated for the page differs from the original content
stream still referenced by the trap network annotation’s Version array. This
problem has been corrected in later versions of Acrobat.
10.10.6, “Open Prepress Interface (OPI)”
173. The Acrobat 3.0 Distiller application converts OPI comments into OPI
dictionaries. When the Acrobat 3.0 viewer prints a PDF file to a PostScript
file or printer, it converts the OPI dictionary back to OPI comments.
However, the OPI information has no effect on the displayed image or
form XObject.
174. Acrobat viewer and Distiller applications earlier than version 4.0 do not
support OPI 2.0.
175. In Acrobat 3.0, the value of the F entry in an OPI dictionary must be a
string.
Appendix C, “Implementation Limits”
176. Acrobat viewers earlier than 5.0 use the PostScript save and restore opera-
tors rather than gsave and grestore to implement q and Q, and are subject
to a nesting limit of 12 levels.
177. In PDF versions earlier than PDF 1.6, the size of the default user space
unit is fixed at 1 ⁄ 72 inch. In Acrobat viewers earlier than version 4.0, the
minimum allowed page size is 72 by 72 units in default user space (1 by 1
inch); the maximum is 3240 by 3240 units (45 by 45 inches). In Acrobat
versions 5.0 and later, the minimum allowed page size is 3 by 3 units (ap-
proximately 0.04 by 0.04 inch); the maximum is 14,400 by 14,400 units
(200 by 200 inches).
Beginning with PDF 1.6, the size of the default user space unit may be set
with the UserUnit entry of the page dictionary. Acrobat 7.0 supports a
1129
SECTION H.3
Implementation Notes
maximum UserUnit value of 75,000, which gives a maximum page dimen-
sion of
15,000,000 inches
(14,400
75,000
1 ⁄ 72). The minimum
UserUnit value is 1.0 (the default).
F.2.2, “Linearization Parameter Dictionary (Part 2)“
178. Acrobat requires a white-space character to follow the left bracket ( [ )
character that begins the H array.
179. Acrobat does not currently support reading or writing files that have an
overflow hint stream.
Note: This implementation note is also referred to in Section F.2.5, “Hint Streams
(Parts 5 and 10).”
180. Acrobat generates a value for the E parameter that incorrectly includes an
object beyond the end of the first page as if it were part of the first page.
F.2.6, “First-Page Section (Part 6)”
181. Acrobat always treats page 0 as the first page for linearization, regardless
of the value of OpenAction.
F.2.8, “Shared Objects (Part 8)”
182. Acrobat does not generate shared object groups containing more than one
object.
F.3.1, “Page Offset Hint Table”
183. In Acrobat, items 6 and 7 in the header section of the page offset hint table
are set to 0. As a result, item 6 of the per-page entry effectively does not
exist; its value is taken to be 0. That is, the sequence of bytes constituting
the content stream for a page is described as if the content stream were the
first object in the page, even though it is not.
184. Acrobat 4.0 and later versions always set item 8 equal to 0. They also set
item 9 equal to the value of item 5, and set item 7 of each per-page hint ta-
ble entry (Table F.4) to be the same as item 2 of the per-page entry. Acro-
bat ignores all of these entries when reading the file.
1130
APPENDIX H
Compatibility and Implementation Notes
F.3.2, “Shared Object Hint Table”
185. In Acrobat, item 5 in the header section of the shared objects hint table is
unused and is always set to 0.
186. MD5 signatures are not implemented in Acrobat; item 2 in a shared object
group entry must be 0.
187. Acrobat does not support more than one shared object in a group; item 4
in a shared object group entry should always be 0.
188. In a document consisting of only one page, items 1 and 2 in the shared ob-
ject hint table are not meaningful; Acrobat writes unpredictable values for
these items.
APPENDIX I
I
Computation of Object
Digests
This appendix describes the algorithm for computing object digests (discussed in
Section 8.7, “Digital Signatures”). The computation uses a hashing method, spec-
ified by the DigestMethod entry of the signature reference dictionary (see Table
8.103). Its value can be SHA1 for the Secure Hash Algorithm 1 (SHA-1) or MD5
for the MD5 message-digest algorithm; see the Bibliography. Both algorithms op-
erate on an arbitrary-length stream of bytes to produce a digest of fixed length (16
bytes for MD5, 20 bytes for SHA-1).
The following sections describe how the stream of bytes to be digested is generat-
ed, starting with a specific object within a PDF file. A PDF object is digested by re-
cursively traversing the object hierarchy beginning with the given object. Objects
encountered during the traversal are categorized as basic PDF types, described in
Section I.1, “Basic Object Types,” or more complex types, described in Section I.2,
“Selective Computation.” Each object is digested as it is processed. Not all objects
may be included, depending on the transform method and parameters (see Sec-
tion 8.7.1, “Transform Methods”) that are being used.
I.1
Basic Object Types
The basic PDF object types are listed in Table I.1. For each type, the following
data is digested:
• a single-byte type identifier
• other bytes representing the value of the data, as described in Table I.1
Dictionaries and arrays can contain indirect references to other objects; therefore,
the data can be recursive. To prevent infinite recursions, the algorithm keeps
track of all indirect objects visited during a recursive descent into a given object.
1131
1132
APPENDIX I
Computation of Object Digests
When it encounters an object that has already been visited, it adds the type iden-
tifier followed by a 4-byte value for the number -1 (0xFFFFFFFF).
TABLE I.1 Data added to object digest for basic object types
OBJECT TYPE
TYPE IDENTIFIER
REMAINING VALUES ADDED TO DIGEST
Null
0
Nothing.
Integer
1
The unsigned 4-byte value of this integer (most significant byte first).
Real
2
The 4-byte integer corresponding to the integral part of the rounded value of the
object.
Boolean
3
0x01 for true; 0x00 for false.
Name
4
An unsigned 4-byte integer (most significant byte first) representing the length of
the name, followed by byte array containing the string representing the name
(following expansion of any escape characters, and excluding the leading “/”
character).
String
5
An unsigned 4-byte integer (most significant byte first) representing the length of
the string, followed by the sequence of bytes corresponding to the string.
Dictionary
6
An unsigned 4-byte value (most significant byte first) specifying the number of
entries in the dictionary, followed by the key-value pairs of the dictionary, sorted
by lexicographic order of the keys (for comparison purposes, the key names are
treated as binary byte sequences). The values may involve recursion; see above.
Special treatment is given to certain dictionaries when the transform method is
anything but Identity (see Section 8.7.1, “Transform Methods”). For these dictio-
naries (which include catalog, page, named page, form field, annotation, action
and additional-actions dictionaries), all key-value pairs are not digested. Instead,
only the values of specified entries are digested; see Section I.2, “Selective Com-
putation,” for details.
Array
7
An unsigned 4-byte value (most significant byte first) specifying the number of
entries in the array, followed by the individual entries, in order. Individual entries
may involve recursion. Specific entries may be excluded when dictated by the
transform method and parameters (for example, annotation dictionaries in a
page’s Annots array).
1133
SECTION I.2
Selective Computation
OBJECT TYPE TYPE IDENTIFIER REMAINING VALUES ADDED TO DIGEST
Stream
8
The following values, in order:
• An unsigned 4-byte value (most significant byte first) specifying the number of
entries in the stream dictionary
• The following key-value pairs in the stream dictionary, if present, sorted as fol-
lows: DecodeParms, F, FDecodeParms, FFilter, Filter and Length
• An unsigned 4-byte value (most significant byte first) specifying the length of
the stream
• The stream data
I.2
Selective Computation
There is a set of special objects that, when encountered in an object calculation,
are not treated as described in the previous section. These objects are described
in the following sections. For each of them, a selective list of entries is chosen,
and only the value of the entry is digested; the key is not included.
When the transform method is DocMDP (see “DocMDP” on page 731)or UR (see
“UR” on page 733), the object digest is computed over the entire document (see
Section I.2.1, “Document”). The calculation varies depending on the transform
parameters, which may specify, for example, whether form fields or annotations
are included.
When the transform method is FieldMDP (see “FieldMDP” on page 736), the
transform parameters indicate specific form fields over which the object digest
should be computed. For each form field, the digest calculation is performed as
specified in Section I.2.6, “Form Fields.”
When the transform method is Identity, selective computation is not used. All
objects are processed as basic object types as described in Section I.1, “Basic Ob-
ject Types.”
1134
APPENDIX I
Computation of Object Digests
I.2.1
Document
When calculating a digest for the document, the following items are included, in
order:
• The values of the following entries in the document catalog (see Table 3.25), if
present: AA, Legal; and Perms
• The values of the following entries in the document information dictionary
(see Table 10.2), if present: Title, Author, Keywords, and Subject
• All page objects in the document, in page order, as described in Section I.2.2,
“Page Objects”
• All named pages specified in the Pages name tree, sorted by name, as described
in Section I.2.3, “Named Pages”
• All embedded files specified in the EmbeddedFiles name tree, sorted by name,
as described in Section I.2.4, “Embedded Files”
I.2.2
Page Objects
For page objects (see Table 3.27), the digest includes the values of the following
entries, in order, if present. For entries listed as inheritable, their values may be
inherited from ancestor nodes in the page tree if not specified explicitly.
• MediaBox (inheritable)
• CropBox (inheritable)
• Resources (inheritable)
• Contents
• Rotate (inheritable)
• AA
• Annots. This entry consists of an array of dictionaries for annotations on the
page. They are sorted by the value of the NM entry; if NM is not present, a glo-
bally unique ID (GUID) is supplied as NM.
For each annotation, if it is a widget, the values added to the digest are those
specified in Section I.2.6, “Form Fields.” If it is any other type of annotation, the
values added to the digest are those specified in Section I.2.5, “Annotation Dic-
tionaries.” However, when the transform parameters specify that annotations
1135
SECTION I.2
Selective Computation
may be modified (for example, when the value of P is 3 for the DocMDP trans-
form method), annotation dictionaries other than widgets are not included.
Note: Pages that have a TemplateInstantiated entry are not included in the digest
when the transform method indicates that page template instantiation is permitted.
Instead, a separate calculation is performed to compare instantiated pages with
their associated named pages; see Section I.2.9, “Page Template Verification.”
I.2.3
Named Pages
For named pages (see Section 8.6.5, “Named Pages”), only the Contents and
Annots entries are digested, as shown in Section I.2.2, “Page Objects,” above.
I.2.4
Embedded Files
The document’s embedded files (as specified in the EmbeddedFiles name tree)
are sorted by name. For each embedded file, the following values are digested, in
order:
• The name of the embedded file
• The stream corresponding to the file
I.2.5
Annotation Dictionaries
For annotation dictionaries (see Table 8.44), the values of the following entries
are digested, in order, if present:
• Contents
Note: A string of the form “()” (empty parentheses) is considered nonexistent con-
tent and is not included.
•T
• F
•A
• AA
• Dest
• QuadPoints
1136
APPENDIX I
Computation of Object Digests
• Inklist
• Name
• FS (If FS refers to the contents of a remote file, the contents of that file are not
digested)
• Sound
• If Movie is present, the value of its F and Poster entries
• For stamp annotations only, the value of the AP entry
I.2.6
Form Fields
For form fields (see Table 8.69), the values of the following entries are digested, in
order, if present:
Note: The A, AA, and F entries are from the annotation dictionary (see Table 8.15);
all others are from the form field dictionary (see Tables 8.69 and 8.81).
• T (the unqualified name)
• FT (inheritable)
• DV (inheritable)
• V (included only in the cases where the transform method and parameters
specify that form field fill-in is not allowed or that this particular field is
locked)
• A (inheritable)
• AA (inheritable)
• F (annotation flags, whose values, if necessary, are obtained by traveling the in-
heritance hierarchy)
• Lock (signature fields only)
• SV (signature fields only)
1137
SECTION I.2
Selective Computation
I.2.7
Actions
For most actions (see Section 8.5, “Actions”), the values of the following entries in
the action dictionary are digested, in order, if present: S
(required), D, F,
NewWindow, O, P, B, Base, Sound, Vol, Annot, T, H, N, JS and URI.
Rendition actions (see “Rendition Actions” on page 668) are treated differently
than the other types. The data that is digested is media data that is nested in sev-
eral levels of objects, as follows:
• The rendition action’s R entry, if present, specifies a rendition object (see Sec-
tion 9.1.2, “Renditions”) whose S entry determines whether it is a media rendi-
tion or a selector rendition.
• Selector renditions have an R entry specifying an array of renditions, which
may themselves be selector renditions. This array is searched recursively for all
media renditions, which are then processed as specified below.
• Media renditions have a C entry that refers to a media clip dictionary. If the S
entry of the media clip is MCD (media clip data), the D entry specifies the data
that is digested (see Table 9.9).
I.2.8
Additional-Actions
Additional-actions dictionaries (see Section 8.5.2, “Trigger Events”) can be the
value of the AA entry of a catalog, page, annotation or field dictionary. If the addi-
tional action is valid, the values of the following entries in the additional-actions
dictionary are digested, in order, if present: E, X, D, U, Fo, Bl, O, C, K, F, V, C, WC,
WS, DS, WP, and DP.
I.2.9
Page Template Verification
In some cases, the permissions granted allow page template instantiation; this oc-
curs when the value of P in the DocMDP transform parameters dictionary is 2 or 3
(see Table 8.104) or the value of Form in the UR transform parameters is
SpawnTemplate (see Table 8.105). In such cases, object digest must be computed
in such a way that its value changes when new pages have been added to the doc-
ument but not when pages have been instantiated from named pages (templates).
1138
APPENDIX I
Computation of Object Digests
To accomplish this, the document object digest does not include pages that have a
value for the TemplateInstantiated entry (see Table 3.27), indicating that they are
instantiated from a named page. At the time the signature is verified, the follow-
ing occurs:
• An object digest is computed for every named page in the document.
• Using the same method, an object digest is computed for every page in the doc-
ument that has a TemplateInstantiated entry and matched against the digest for
the corresponding named page.
• Verification succeeds only if the digests match for all instantiated pages in the
document.
Color Plates
Additive
Subtractive
PLATE 1 Additive and subtractive color (Section 4.5.3, “Device Color Spaces,” page 241)
PLATE 2 Uncalibrated color (Section 4.5.4, “CIE-Based Color Spaces,” page 244)
L* = 100
white
a* = -100
b* = 100
green
yellow
b* = -100
a* = 100
blue
red
L* = 0
black
PLATE 3 Lab color space (“Lab Color Spaces,” page 250)
L*a*b *
RGB
CMYK
PLATE 4 Color gamuts (“Lab Color Spaces,” page 250)
AbsoluteColorimetric
RelativeColorimetric
Saturation
Perceptual
PLATE 5 Rendering intents (“Rendering Intents,” page 260)
Grayscale
Black
Magenta
Result
PLATE 6 Duotone image (“DeviceN Color Spaces,” page 269)
Single-component (grayscale) image
Quadtone image
PLATE 7 Quadtone image (“DeviceN Color Spaces,” page 269)
♦♣
♠♥
PLATE 8 Colored tiling pattern (“Colored Tiling Patterns,” page 295)
♦♣
♠♥
PLATE 9 Uncolored tiling pattern (“Uncolored Tiling Patterns,” page 299)
ABCDE FGHIJ M
Extend = [ false false ], Background not specified
ABCDE FGHIJKLM
Extend = [ true true ], Background not specified
ABCD E FGHIJKLM
Extend = [ true true ], Background not specified
PLATE 10 Axial shading (“Type 2 (Axial) Shadings,” page 310)
Starting from
smaller circle
Starting from
larger circle
Neither circle extended
Starting circle extended
PLATE 11 Radial shadings depicting a cone (“Type 3 (Radial) Shadings,” page 312)
Starting from inner circle;
Starting from outer circle;
no background color specified
background color specified
PLATE 12 Radial shadings depicting a sphere (“Type 3 (Radial) Shadings,” page 313)
No background color specified
Background color specified
PLATE 13 Radial shadings with extension (“Type 3 (Radial) Shadings,” page 313)
PLATE 14 Radial shading effect (“Type 3 (Radial) Shadings,” page 313)
Unit square
Nonlinear (control points altered)
PLATE 15 Coons patch mesh (“Type 6 Shadings (Coons Patch Meshes),” page 321)
Ungrouped objects
Ungrouped objects
Object opacity = 1.0
Object opacity = 0.5
Transparency group
Transparency group
Object opacity = 1.0
Object opacity = 0.5
Group opacity = 0.5
Group opacity = 1.0
Blend mode = Normal
Blend mode = HardLight
PLATE 16 Transparency groups (Section 7.1, “Overview of Transparency,” page 515)
Isolated
Non-isolated
Knockout
Non-knockout
PLATE 17 Isolated and knockout groups (Sections 7.3.4, “Isolated Groups,” page 539
and 7.3.5, “Knockout Groups,” page 540)
PLATE 20 Blending and overprinting (“Compatibility with Opaque Overprinting,” page 569)
Bibliography
This Bibliography provides details on books and documents, from both Adobe
Systems and other sources, that are referred to in this book.
Resources from Adobe Systems Incorporated
All of these resources from Adobe are available on the Adobe Solutions Network
(ASN) Web site. They can be accessed from this location:
The ASN can also be contacted as follows:
Adobe Solutions Network
Adobe Systems Incorporated
345 Park Avenue
San Jose, CA 95110-2704
(800) 685-3510 (from North America)
(206) 675-6145 (from other areas)
Note: Document version numbers and dates given in this Bibliography are the latest
at the time of publication; more recent versions may be found on the Web site.
JavaScript for Acrobat API Reference, Version 8.0
Adobe Glyph List, Version 2.0
Adobe Type 1 Font Format. Explains the internal organization of a PostScript Type
1 font program. Also see Adobe Technical Note #5015, Type 1 Font Format
Supplement.
Digital Signature Appearances
1151
1152
Bibliography
OPI: Open Prepress Interface Specification 1.3. Also see Adobe Technical Note
#5660, Open Prepress Interface (OPI) Specification, Version 2.0.
OpenType Font Specification
PDF Signature Build Dictionary Specification
PostScript Language Reference, Third Edition, Addison-Wesley, Reading, MA,
1999
XML Architecture, XML Forms Architecture (XFA) Specification, version 2.4
Adobe XML Architecture, Forms Architecture (XFA) Specification, version 2.2
Note: Beginning with XFA 2.2, the XFA specification includes the Template Specifi-
cation, the Config Specification, the XDP Specification, and all other XML specifica-
tions unique to the XML Forms Architecture (XFA).
Adobe XML Architecture, XML Data Package (XDP) Specification, version 2.0
Adobe XML Architecture, Template Specification, version 2.0
Adobe XML Architecture, XML Forms Data Format Specification, version 2.0
(Draft)
XMP: Extensible Metadata Platform
Numbered Technical Notes:
• Technical Note #5001, PostScript Language Document Structuring Conventions
Specification, Version 3.0
• Technical Note #5004, Adobe Font Metrics File Format Specification, Version 4.1
Adobe font metrics (AFM) files are available through the Type section of the
ASN Web site.
• Technical Note #5014, Adobe CMap and CID Font Files Specification, Version
1.0
• Technical Note #5015, Type 1 Font Format Supplement
1153
Bibliography
• Technical Note #5044, Color Separation Conventions for PostScript Language
Programs
• Technical Note #5078, Adobe-Japan1-4 Character Collection for CID-Keyed
Fonts
• Technical Note #5079, Adobe-GB1-4 Character Collection for CID-Keyed Fonts
• Technical Note #5080, Adobe-CNS1-4 Character Collection for CID-Keyed Fonts
• Technical Note #5088, Font Naming Issues
• Technical Note #5092, CID-Keyed Font Technology Overview
• Technical Note #5093, Adobe-Korea1-2 Character Collection for CID-Keyed
Fonts
• Technical Note #5094, Adobe CJKV Character Collections and CMaps for CID-
Keyed Fonts
• Technical Note #5097, Adobe-Japan2-0 Character Collection for CID-Keyed
Fonts
• Technical Note #5116, Supporting the DCT Filters in PostScript Level 2
• Technical Note #5146, Adobe-Japan1-5 Character Collection for CID-Keyed
Fonts (Addendum)
• Technical Note #5176, The Compact Font Format Specification
• Technical Note #5177, The Type 2 Charstring Format
• Technical Note #5411, ToUnicode Mapping File Tutorial
• Technical Note #5620, Portable Job Ticket Format, Version 1.1
• Technical Note #5660, Open Prepress Interface (OPI) Specification, Version 2.0
Other Resources
Aho, A. V., Hopcroft, J. E., and Ullman, J. D., Data Structures and Algorithms,
Addison-Wesley, Reading, MA, 1983. Includes a discussion of balanced trees.
Apple Computer, Inc., TrueType Reference Manual. Available on Apple’s Web site
1154
Bibliography
Arvo, J. (ed.), Graphics Gems II, Academic Press, 1994. The section “Geometric-
ally Continuous Cubic Bézier Curves” by Hans-Peter Seidel describes the mathe-
matics used to smoothly join two cubic Bézier curves.
CIP4. See International Cooperation for the Integration of Processes in Prepress,
Press and Postpress.
Ecma International, Standard ECMA-363, Universal 3D File Format. This docu-
ment is available at <http://www.ecma-international.org/>
Fairchild, M. D., Color Appearance Models, Addison-Wesley, Reading, MA, 1997.
Covers color vision, basic colorimetry, color appearance models, cross-media
color reproduction, and the current CIE standards activities. Updates, software,
and color appearance data are available at < http://www.cis.rit.edu/people/faculty/
fairchild/CAM.html >.
Federal Information Processing Standards Publications:
• FIPS PUB 186-2, Digital Signature Standard, describes DSA signatures. It is
available at
• FIPS PUB 197, Advanced Encryption Standard (AES)
Foley, J. D. et al., Computer Graphics: Principles and Practice, Addison-Wesley,
Reading, MA, 1996. (First edition was Foley, J. D. and van Dam, A., Fundamentals
of Interactive Computer Graphics, Addison-Wesley, Reading, MA, 1982.) Covers
many graphics-related topics, including a thorough treatment of the mathematics
of Bézier cubics and Gouraud shadings.
Glassner, A. S. (ed.), Graphics Gems, Academic Press, 1993. The section “An Al-
gorithm for Automatically Fitting Digitized Curves” by Philip J. Schneider de-
scribes an algorithm for determining the set of Bézier curves approximating an
arbitrary set of user-provided points. Appendix 2 contains an implementation of
the algorithm, written in the C programming language. Other sections relevant to
the mathematics of Bézier curves include “Solving the Nearest-Point-On-Curve
Problem” and “A Bézier Curve-Based Root-Finder,” both by Philip J. Schneider,
and “Some Properties of Bézier Curves” by Ronald Goldman. The source code
appearing in the appendix is available via anonymous FTP, as described in the
preface to Graphics Gems III (edited by D. Kirk; see its entry below).
1155
Bibliography
Hewlett-Packard Corporation, PANOSE Classification Metrics Guide. Available
on the Agfa Monotype Web site at < http://www.agfamonotype.com/printer/
pan1.asp >.
Hunt, R. W. G., The Reproduction of Colour, 5th ed., Fisher Books, England, 1996.
A comprehensive general reference on color reproduction; includes an introduc-
tion to the CIE system.
Institute of Electrical and Electronics Engineers, IEEE Standard for Binary Float-
ing-Point Arithmetic (IEEE 754-1985).
International Color Consortium (ICC). The following are available with related
documents at < http://www.color.org >:
• Specification ICC.1:2004-10, File Format for Color Profiles
• ICC Characterization Data Registry
International Cooperation for the Integration of Processes in Prepress, Press and
Postpress (CIP4), JDF Specification, Version 1.2. Available through the CIP4 Web
site at < http://www.cip4.org >.
International Electrotechnical Commission (IEC), IEC/3WD 61966-2.1, Colour
Measurement and Management in Multimedia Systems and Equipment, Part 2.1:
Default RGB Colour Space—sRGB. Available through the International Electro-
technical Commission (IEC) at <http://www.iec.ch>.
International Organization for Standardization (ISO). The following standards
are available through < http://www.iso.org />:
• ISO 639-1:2002 Codes for the representation of names of languages -- Part 1: Al-
pha-2 code
• ISO 639-2:1998 Codes for the representation of names of languages -- Part 2: Al-
pha-3 code
• ISO 3166-1:1997 , Codes for the representation of names of countries and their
subdivisions -- Part 1: Country codes
• ISO 3166-2:1998 , Codes for the representation of names of countries and their
subdivisions -- Part 2: Country subdivision code
• ISO/IEC 8824-1:2002, Abstract Syntax Notation One (ASN.1): Specification of
basic notation
1156
Bibliography
• ISO/IEC 10918-1:1994, Digital Compression and Coding of Continuous-Tone
Still Images (informally known as the JPEG standard, for the Joint Photograph-
ic Experts Group, the ISO group that developed the standard)
• ISO/IEC 15444-2:2004, Information Technology—JPEG 2000 Image Coding Sys-
tem: Extensions
• ISO 15930-1:2001, Graphic technology -- Prepress digital data exchange -- Use of
PDF -- Part 1: Complete exchange using CMYK data (PDF/X-1 and PDF/X-1a)
International Telecommunication Union (ITU). The following can be ordered
from ITU at < http://www.itu.int />
• Recommendations T.4 and T.6. These standards for Group 3 and Group 4 fac-
simile encoding replace those formerly provided in the CCITT Blue Book, Vol.
VII.3.
• Recommendation X.509 (1997): Information Technology—Open Systems Inter-
connection—The Directory: Authentication Framework.
Internet Engineering Task Force (IETF) Requests for Comments (RFCs). The
following RFCs are available through < http://www.rfc-editor.org >:
• RFC 1321, The MD5 Message-Digest Algorithm
• RFC 1738, Uniform Resource Locators
• RFC 1808, Relative Uniform Resource Locators
• RFC 1950, ZLIB Compressed Data Format Specification, Version 3.3
• RFC 1951, DEFLATE Compressed Data Format Specification, Version 1.3
• RFC 2045, Multipurpose Internet Mail Extensions (MIME) Part One: Format of
Internet Message Bodies
• RFC 2046, Multipurpose Internet Mail Extensions (MIME) Part Two: Media
Types
• RFC 2083, PNG (Portable Network Graphics) Specification, Version 1.0
• RFC 2315, PKCS #7: Cryptographic Message Syntax, Version 1.5
• RFC 2396, Uniform Resource Identifiers (URI): Generic Syntax
• RFC 2560, X.509 Internet Public Key Infrastructure Online Certificate Status
Protocol—OCSP
1157
Bibliography
• RFC 2616, Hypertext Transfer Protocol—HTTP/1.1
• RFC 2898, PKCS #5: Password-Based Cryptography Specification Version 2.0
• RFC 3066, Tags for the Identification of Languages
• RFC 3161, Internet X.509 Public Key Infrastructure Time-Stamp Protocol (TSP)
• RFC 3174, US Secure Hash Algorithm 1 (SHA1)
• RFC 3280, Internet X.509 Public Key Infrastructure, Certificate and Certificate
Revocation List (CRL) Profile
Internet Engineering Task Force (IETF) Public Key Infrastructure (PKIX) work-
ing group: <http://www.ietf.org/html.charters/pkix-charter.html>
Kirk, D. (ed.), Graphics Gems III, Academic Press, 1994. The section “Interpola-
tion Using Bézier Curves” by Gershon Elber contains an algorithm for calculating
a Bézier curve that passes through a user-specified set of points. The algorithm
uses not only cubic Bézier curves, which are supported in PDF, but also higher-
order Bézier curves. The appendix contains an implementation of the algorithm,
written in the C programming language. The source code appearing in the
appendix is available via anonymous FTP, as described in the book’s preface.
Lunde, K., CJKV Information Processing, O’Reilly & Associates, Sebastopol, CA,
1999. Excellent background material on CMaps, character sets, encodings, and
the like.
Microsoft Corporation, TrueType 1.0 Font Files Technical Specification. Available
Netscape Communications Corporation, Client-Side JavaScript Reference and
other JavaScript documents are available through the Adobe Web page
Pennebaker, W. B. and Mitchell, J. L., JPEG: Still Image Data Compression Stan-
dard, Van Nostrand Reinhold, New York, 1992.
Porter, T. and Duff, T., “Compositing Digital Images,” Computer Graphics, Vol. 18
No. 3, July 1984. Computer Graphics is the newsletter of the ACM’s special interest
group SIGGRAPH; for more information, see < http://www.acm.org >.
1158
Bibliography
RSA Security, Inc. The following document, among others related to encryption
and digital signatures, is available at < http://www.rsasecurity.com >:
PKCS #1 - RSA Cryptography Standard
Unicode Consortium publications:
• The Unicode Standard, Version 4.0, Addison-Wesley, Boston, MA, 2003. The
latest information is available at < http://www.unicode.org >.
• Unicode Standard Annex #9, The Bidirectional Algorithm, Version 4.0.0, Uni-
code Standard Annex #14, Line Breaking Properties, Version 4.0.0, and Unicode
Standard Annex #29, Text Boundaries, Version 4.0.0. These technical reports
are available at < http://www.unicode.org >.
World Wide Web Consortium (W3C). The following publications are available
through the W3C Web site at < http://www.w3.org/ >:
• Cascading Style Sheets, level 2 (CSS2) Specification
• Extensible Markup Language (XML) 1.1
• Extensible Stylesheet Language (XSL) 1.0
• HTML 4.01 Specification
• Scalable Vector Graphics (SVG) 1.0 Specification
• Synchronized Multimedia Integration Language (SMIL 2.0)
<http//:www.w3.org/TR/smil20/>
• Web Content Accessibility Guidelines 1.0
• XHTML 1.0: The Extensible HyperText Markup Language
Большое спасибо!
Ваше мнение очень важно для нас.
Нет комментариевНе стесняйтесь поделиться с нами вашим ценным мнением.
Текст