Previous Next
1119
S E C T I O N H .3 Implementation Notes
8.6.3, “Field Types” (Choice Fields)
122. In Acrobat 3.0, the Opt array must be homogenous: its elements must be
either all text strings or all arrays.
8.6.4, “Form Actions” (Submit-Form Actions)
123. In Acrobat viewers, if the response to a submit-form action uses Forms
Data Format (FDF), the URL must end in #FDF so that it can be recog-
nized as such by the Acrobat software and handled properly. Conversely, if
the response is in any other format, the URL should not end in #FDF.
8.6.4, “Form Actions” (Import-Data Actions)
124. Acrobat viewers set the F entry to a relative file specification locating the
FDF file with respect to the current PDF document file. If the designated
FDF file is not found when the import-data action is performed, Acrobat
tries to locate the file in a few well-known locations, depending on the
host platform. On the Windows platform, for example, Acrobat searches
in the directory from which Acrobat was loaded, the current directory, the
System directory, the Windows directory, and any directories listed in the
PATH environment variable. On Mac OS, Acrobat searches in the Prefer-
ences folder and the Acrobat folder.
125. When performing an import-data action, Acrobat viewers import the
contents of the FDF file into the current document’s interactive form,
ignoring the F and ID entries in the FDF dictionary of the FDF file.
8.6.4, “Form Actions” (JavaScript Actions)
126. Because JavaScript 1.2 is not Unicode-compatible, PDFDocEncoding and
the Unicode encoding are translated to a platform-specific encoding be-
fore interpretation by the JavaScript engine.
8.6.6, “Forms Data Format” (FDF Header)
127. Because Acrobat viewers earlier than 5.0 cannot accept any other version
number because of a bug, the FDF file header is permanently frozen at
version 1.2. All further updates to the version number will be made via the
Version entry in the FDF catalog dictionary instead.
Previous Next