Adobe 12020596 User Guide - Page 37

Annotations

Get Adobe 12020596 PDF manuals and user guides View all Adobe 12020596 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 37 highlights

Adobe Acrobat SDK Adobe® Supplement to the ISO 32000 Interactive Features (Chapter 8 in PDF Reference) 8.4 Annotations 37 the navigator dictionary refers to MyIcon.png. The base IRI in this case is the root directory of the abstract container. The navigator's resources name tree should then include four resources: MyNavigator.swf, MyIcon.png, MyStyles.css, and images/MyImage.jpeg. The base IRI for PDF viewer components such as the welcome page and header is the root directory of the abstract container. A resources name tree differs from the EmbeddedFiles name tree (Section 3.10.3 in the PDF Reference) in two respects. The keys in the tree are always text strings that represent relative IRIs. The values in the tree are simple streams rather than file specifications. The only information associated with a resource is its name, which is defined by the key. Storing the navigator resources in a name tree separate from the collection resources allows a navigator to be self-contained. If a user replaces a navigator with another, the navigator resources are replaced as well. The SWF file components embedded in a PDF file use the collection resources. (See the Resources entry in Table 8.6. on page 29.) The resources in the collection resources name tree are organized by directory. All the resources needed by the welcome page are named beginning with welcome/, as if these resources were in a directory named welcome. Similarly, header resources begin with header/. String table Navigators include some text that is displayed to the user. While the content of PDF documents is generally not localized, navigators include both content and application (the navigator SWF file), and PDF provides a mechanism that enables navigators to specify localized text separate from the application. The String entry in the navigator dictionary (TABLE 8.6d Entries in a navigator dictionary) is an indirect reference to a string table. This string table is a name tree whose keys are string IDs and values are localized text strings. A string ID is itself a text string. Given a string ID and a locale (the Locale entry in a navigator dictionary), a localized text string can be found. The Acrobat ActionScript API provides access to the string table. (See the Acrobat ActionScript API Reference in the Bibliography.) The method INavigatorHost.getLocalizedString returns the value for a given ID or returns the provided default value (a parameter to getLocalizedString) if the ID is not in the string table. 8.4 Annotations Page 605 of the PDF Reference describes the effect of each supported Tabs value. After the description for the S (structure order) value, add these bulleted entries: ● A (annotation array order): All annotations are visited in the order in which they appear in the page Annots array. (See Table 3.27, "Entries in a page object," and implementation note E-17, page 132.) ● W (widgets order): Widget annotations are visited in the order in which they appear in the page Annots array, followed by other annotation types in row order. (See Table 3.27 "Entries in a page object.") For information about row order, see the R (row order) entry description on page 605. For information about the Acrobat implementation of this feature and the effect of the accessibility preference on annotations order, see "Interaction between accessibility preference and annotation tab order," part of implementation note 77, on page 116.

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
Adobe Acrobat SDK
Interactive Features (Chapter 8 in PDF Reference)
Adobe® Supplement to the ISO 32000
8.4 Annotations
37
the navigator dictionary refers to MyIcon.png. The base IRI in this case is the root directory of the abstract
container. The navigator’s resources name tree should then include four resources: MyNavigator.swf,
MyIcon.png, MyStyles.css, and images/MyImage.jpeg.
The base IRI for PDF viewer components such as the welcome page and header is the root directory of the
abstract container.
A resources name tree differs from the
EmbeddedFiles
name tree (Section 3.10.3 in the
PDF Reference
) in
two respects. The keys in the tree are always text strings that represent relative IRIs. The values in the tree
are simple streams rather than file specifications. The only information associated with a resource is its
name, which is defined by the key.
Storing the navigator resources in a name tree separate from the collection resources allows a navigator to
be self-contained. If a user replaces a navigator with another, the navigator resources are replaced as well.
The SWF file components embedded in a PDF file use the collection resources. (See the
Resources
entry
in Table 8.6. on
page 29
.) The resources in the collection resources name tree are organized by directory.
All the resources needed by the welcome page are named beginning with welcome/, as if these resources
were in a directory named welcome. Similarly, header resources begin with header/.
String table
Navigators include some text that is displayed to the user. While the content of PDF documents is
generally not localized, navigators include both content and application (the navigator SWF file), and PDF
provides a mechanism that enables navigators to specify localized text separate from the application.
The
String
entry in the navigator dictionary (
TABLE 8.6d Entries in a navigator dictionary
) is an indirect
reference to a string table. This string table is a name tree whose keys are string IDs and values are
localized text strings. A string ID is itself a text string. Given a string ID and a locale (the
Locale
entry in a
navigator dictionary), a localized text string can be found. The Acrobat ActionScript API provides access to
the string table. (See the
Acrobat ActionScript API Reference
in the
Bibliograph
y
.) The method
INavigatorHost.getLocalizedString
returns the value for a given ID or returns the provided
default value (a parameter to
getLocalizedString
) if the ID is not in the string table.
8.4 Annotations
Page 605 of the PDF Reference describes the effect of each supported
Tabs
value. After the description for the
S
(structure order) value, add these bulleted entries
:
●
A
(annotation array order): All annotations are visited in the order in which they appear in the page
Annots
array. (See
Table 3.27
, “
Entries in a page object
,” and implementation note E-17,
page 132
.)
●
W
(widgets order): Widget annotations are visited in the order in which they appear in the page
Annots
array, followed by other annotation types in row order. (See
Table 3.27
“
Entries in a page object.”
) For
information about row order, see the
R
(row order) entry description on page 605.
For information about the Acrobat implementation of this feature and the effect of the accessibility
preference on annotations order, see “
Interaction between accessibility preference and annotation tab
order
,” part of implementation note 77, on
page 116
.