Previous Next
1118
APPENDIX H Compatibility and Implementation Notes
8.6.2, “Field Dictionaries” (Variable Text)
118. In PDF 1.2, an additional entry in the field dictionary, DR, was defined but
was never implemented. Beginning with PDF 1.5, this entry is obsolete
and should be ignored.
119. If the MK entry is present in the field’s widget annotation dictionary (see
Table 8.39), Acrobat viewers regenerate the entire XObject appearance
stream. If MK is not present, the contents of the stream outside /Tx BMC ...
EMC are preserved.
8.6.2, “Field Dictionaries” (Rich Text Strings)
120. To select a font specified by attributes in a rich text string, Acrobat 6.0 fol-
lows this sequence, choosing the first appropriate font it finds:
a. A font in the default resource dictionary (specified by the document’s DR
entry; see Table 8.67) whose font descriptor information matches the font
specification in the rich text string. “Font Characteristics” on page 892 de-
scribes how this matching is done.
b. A matching font installed on the user’s system, ignoring generic font fami-
lies.
c. A font on the user’s system that matches the generic font family, if speci-
fied.
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.2, “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 val-
ue. 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 docu-
ment author to choose between these behaviors.
Previous Next