Adobe Acrobat SDK
Implementation Notes
Adobe® Supplement to the ISO 32000
Implementation Notes to the PDF Reference, sixth edition 111
37. In a document containing articles, if the first page that has an article bead does not have a
B
entry,
Acrobat viewers rebuild the
B
array for all pages of the document.
38. In PDF 1.2, additional-actions dictionaries were inheritable; beginning with PDF 1.3, they are not
inheritable.
3.7.1 Content Streams
39. Acrobat viewers report an error the first time they find an unknown operator or an operator with too
few operands, but continue processing the content stream. No further errors are reported.
3.9.1 Type 0 (Sampled) Functions
40. When printing, Acrobat performs only linear interpolation, regardless of the value of the
Order
entry.
3.9.2 Type 2 (Exponential Interpolation) Functions
41. Since Type 2 functions are not defined in PDF 1.2 or earlier versions, Acrobat 3.0 (whose native file
format is PDF 1.2) reports an Invalid Function Resource error if it encounters a function of this type.
3.9.3 Type 3 (Stitching) Functions
42. Since Type 3 functions are not defined in PDF 1.2 or earlier versions, Acrobat 3.0 (whose native file
format is PDF 1.2) reports an error, “Invalid Function Resource,” if it encounters a function of this type.
3.9.4 Type 4 (PostScript Calculator) Functions
43. Since Type 4 functions are not defined in PDF 1.2 or earlier versions, Acrobat 3.0 (whose native file
format is PDF 1.2) reports an error, “Invalid Function Resource,” if it encounters a function of this type.
44. Acrobat uses single-precision floating-point numbers for all real-number operations in a type 4
function.
3.10.2 File Specification Dictionaries
45.
.
In Acrobat 5.0, file specifications accessed through
EmbeddedFiles
have a
Type
entry whose value is
F
instead of the correct
Filespec
. Acrobat 6.0 and later accept a file specification
whose
Type
entry
is either
Filespec
or
F
.
46. In certain situations, Acrobat 3.0 and greater do not correctly interpret file specifications referenced by
the
F
entry in Form or Image XObjects. Specifically, Acrobat ignores the file specification
EF
entry when
that file specification is referenced from the XObject
F
entry.
The code that follows shows an example of an Image XObject
F
entry referencing a file specification
that in turn references an embedded file. Acrobat does not correctly interpret such file specifications.
Example:
Acrobat does not correctly interpret a file specification.
13 0 obj <<
/Type /XObject
/Subtype /Image
/F 12 0 R
