Adobe 12020596 Supplement Manual page 131

Adobe Acrobat SDK
Adobe® Supplement to the ISO 32000
E-7. The Acrobat implementation of barcode form fields places several constraints on some of the entries in
the field dictionary:
Field Flags Entry: In the field dictionary of a barcode form field, bits 1, 3, 13, and 23 of the
(field flags) are set. These bit positions have the names ReadOnly, NoExport, Multiline, and
DoNotSpellCheck. (See Tables 8.70 and 8.77 of the PDF Reference, sixth edition, PDF 1.7.)
Kids Entry: In Acrobat 9, there is a limit of 255 on the array of indirect references to the barcode
widget annotations that render the barcode.
The Acrobat implementation of barcode widget annotations sets the
to
[1.0]
E-8. In Acrobat 9.0, the string length of
E-9. For EPSG codes that the Acrobat 9.0 implementation does not support, or for custom coordinate
systems not associated with EPSG codes, Well Known Text strings can be used to fully specify an object.
E-10. If the text box, as determined by
E-11. In the implementation for version 9.0 of the Adobe Reader software, both Flash and 3D content are
supported.
E-12. Rich Media annotations in version 9.0 of the Adobe Reader software support only a subset of the
Border Style dictionary (/BS), including the line width and color values. One behavior discrepancy is
that if the dictionary is not present, the line width value defaults to zero.
E-13. When the value for the key
RichMediaPresentation dictionary" on page
composited over already flattened page content using an alpha channel. Rich Media Annotation
artwork is always rendered above all page content and does not, therefore, interfere with the
transparency model of the page.
E-14. Older viewers—earlier than 9.0—ignore and do not process the additional approval signature
FieldMDP Lock state. To increase compatibility, Acrobat sets
document is locked. Consequently, older viewers consider all fields locked when the document lock is
applied using Acrobat 9.0. However, adding annotations is still possible.
Documents signed with Acrobat 9.0 with locking, and then opened and modified in an older viewer
(adding annotations), and then opened in Acrobat 9.0 show invalidated signatures.
E-15. How seed values are interpreted is both application-specific and specific to the signature handler
associated with the signature field. Each application and handler may choose how to honor the seed
values. The behavior of Acrobat and the PPKLite signature handler is documented below for the
LockDocument
A seed value of
auto
document. Otherwise, the signer can choose whether to lock at the time of signing, with the same
behavior as the value being set to
required flag when the
E-16. The
AppearanceFilter
automatically chooses a matching appearance from the user interface. If the
optional, and if a matching appearance is not available, it defaults to the normal behavior where any
appearance can be chosen. If the filter is required, the matching appearance is selected and the
selection box disabled.
to obtain a black background for the barcode widget annotation.
Transparent
seed value, and for
specifies that the implementation is application-specific. Acrobat processes the
auto
value as follows: If the document contains hidden fields, the signer is not allowed to lock the
LockDocument
is implemented as follows: If the
Implementation Notes to Adobe Extensions to ISO 32000
is limited to 1024 bytes.
WKT
, is not large enough, Acrobat 9.0 truncates the string (
TB
(as described in
82) is set to
true
AppearanceFilter
and the required flag not set. Acrobat does not honor the
false
value is .
auto
Implementation Notes
entry of the
BG
"TABLE 9.50d Entries in a
, the Rich Media Annotation artwork is
to lock all fields when the
FieldMDP
in implementation note E-15.
is present, it
AppearanceFilter
AppearanceFilter
131
entry
Ff
dictionary
MK
).
UT
is