Adobe 12020596 Supplement Manual page 122

Adobe Acrobat SDK
Adobe® Supplement to the ISO 32000
b. A matching font installed on the user's system, ignoring generic font families.
c. A font on the user's system that matches the generic font family, if specified.
d. A standard font (see implementation note 62) that most closely matches the other font
specification properties and is appropriate for the current input locale.
8.6.3 Field Dictionaries (Button Fields)
121. The behavior of Acrobat has changed in the situation where a check box or radio button field have
multiple children that have the same export value. In Acrobat 4.0, such buttons always turned off and
on in unison. In Acrobat 5.0, the behavior of radio buttons was changed to mimic HTML so that turning
on a radio button always turned off its siblings regardless of export value. In Acrobat 6.0, the
RadiosInUnison flag allows the document author to choose between these behaviors.
8.6.3 Field Types (Choice Fields)
122. In Acrobat 3.0, the
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 recognized 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
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 Preferences 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
8.6.4 Form Actions (JavaScript Actions)
126. Because JavaScript 1.2 is not Unicode-compatible,
translated to a platform-specific encoding before 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
array must be homogenous: its elements must be either all text strings or all
Opt
entry to a relative file specification locating the FDF file with respect to the
F
entry in the FDF catalog dictionary instead.
Version
Implementation Notes to the PDF Reference, sixth edition
and entries in the FDF dictionary of the FDF file.
F ID
and the Unicode encoding are
PDFDocEncoding
Implementation Notes
122