55
©
Adobe Systems Incorporated 2008 – All rights reserved
487
PDF 32000-1:2008
•
Renditions are of two varieties: media renditions (see 13.2.3.2, “Media Renditions”) that define the
characteristics of the media to be played, and selector renditions (see 13.2.3.3, “Selector Renditions”) that
enables choosing which of a set of media renditions should be played.
•
Media renditions contain entries that specify what should be played (see 13.2.4, “Media Clip Objects”),
how it should be played (see 13.2.5, “Media Play Parameters”), and where it should be played (see 13.2.6,
“Media Screen Parameters”).
•
13.2.7, “Other Multimedia Objects,” describes several PDF objects that are referenced by the preceding
major objects.
NOTE 2
Some of the features described in the following sub-clauses have references to corresponding elements in the
Synchronized Multimedia Integration Language (SMIL 2.0) standard (see the Bibliography).
13.2.2
Viability
When playing multimedia content, the conforming reader shall often make decisions such as which player
software and which options, such as volume and duration, to use.
In making these decisions, the viewer shall determine the viability of the objects used. If an object is considered
non-viable, the media should not be played. If the object is viable, the media should be played, though possibly
under less than optimum conditions.
There are several entries in the multimedia object dictionaries whose values shall have an effect on viability. In
particular, some of the object dictionaries define two entries that divide options into one of two categories:
•
MH (“must honour”): The options specified by this entry shall be honoured; otherwise, the containing object
shall be considered non-viable.
•
BE (“best effort”): An attempt should be made to honour the options; however, if they cannot be honoured,
the containing object is still considered viable.
MH and BE are both dictionaries, and the same entries shall be defined for both of them. In any dictionary
where these entries are allowed, both entries may be present, or only one, or neither.
EXAMPLE
The media play parameters dictionary (see Table 279) allows the playback volume to be set by means of
the V entry in its MH and BE dictionaries (see Table 280).
If the specified volume cannot be honoured, the object shall be considered non-viable if V is in the MH
dictionary, and playback shall not occur. If V is in the BE dictionary (and not also in the MH dictionary), playback
should still occur: the playing software attempts to honour the specified option as best it can.
Using this mechanism, authors may specify minimum requirements (MH) and preferred options (BE). They
may also specify how entries that are added in the future to the multimedia dictionaries shall be interpreted by
old conforming readers. If an entry that is unrecognized by the viewer is in the MH dictionary, the object shall be
considered non-viable. If an unrecognized entry is in a BE dictionary, the entry shall be ignored and viability
shall be unaffected. Unless otherwise stated, an object shall be considered non-viable if its MH dictionary
contains an unrecognized key or an unrecognized value for a recognized key.
The following rules apply to the entries in MH and BE dictionaries, which behave somewhat differently from
other PDF dictionaries:
•
If an entry is required, the requirement is met if the entry is present in either the MH dictionary or the BE
dictionary.
•
If an optional entry is not present in either dictionary, it shall be considered to be present with its default
value (if one is defined) in the BE dictionary.
DICOM Image Viewer| What is DICOM RasterEdge .NET Imaging SDK, you may add it on formats, including Bitmap, Png, Gif, Tiff, PDF, MS-Word NET sample codings are provided for image conversion if
add picture to pdf online; how to add image to pdf acrobat
58
PDF 32000-1:2008
488
©
Adobe Systems Incorporated 2008 – All rights reserved
•
If an instance of the same entry is present in both MH and BE, the instance in the BE dictionary shall be
ignored unless otherwise specified.
•
If the value of an entry in an MH or a BE dictionary is a dictionary or array, it shall be treated as an atomic
unit when determining viability. That is, all entries within the dictionary or array shall be honoured for the
containing object to be viable.
NOTE
When determining whether entries can be honoured, it is not required that each one be evaluated
independently, since they may be dependent on one another. That is, a conforming reader or player may
examine multiple entries at once (even within different dictionaries) to determine whether their values can be
honoured.
The following media objects may have MH and BE dictionaries. They function as described previously, except
where noted in the individual sub-clauses:
•
Rendition (Table 267)
•
Media clip data (Table 276)
•
Media clip section (Table 278)
•
Media play parameters (Table 280)
•
Media screen parameters (Table 283)
13.2.3
Renditions
13.2.3.1 General
There are two types of rendition objects:
•
A media rendition (see 13.2.3.2, “Media Renditions”) is a basic media object that specifies what to play,
how to play it, and where to play it.
•
A selector rendition (see 13.2.3.3, “Selector Renditions”) contains an ordered list of renditions. This list
may include other selector renditions, resulting in a tree whose leaves are media renditions. The
conforming reader should play the first viable media rendition it encounters in the tree (see 13.2.2,
“Viability”).
NOTE 1
Table 266 shows the entries common to all rendition dictionaries. The N entry in a rendition dictionary specifies
a name that can be used to access the rendition object by means of name tree lookup (see Table 31).
JavaScript actions (see 12.6.4.16, “JavaScript Actions”), for example, use this mechanism.
Since the values referenced by name trees shall be indirect objects, all rendition objects should be indirect
objects.
NOTE 2
A rendition dictionary is not required to have a name tree entry. When it does, the conforming reader should
ensure that the name specified in the tree is kept the same as the value of the N entry (for example, if the user
interface allows the name to be changed). A document should not contain multiple renditions with the same
name.
The MH and BE entries are dictionaries whose entries may be present in one or the other of them, as
described in 13.2.2, “Viability.” For renditions, these dictionaries shall have a single entry C (see Table 267),
whose value shall have a media criteria dictionary specifying a set of criteria that shall be met for the rendition
to be considered viable (see Table 268).
The media criteria dictionary behaves somewhat differently than other MH/BE entries, as they are described in
13.2.2, “Viability.” The criteria specified by all of its entries shall be met regardless of whether they are in an MH
or a BE dictionary. The only exception is that if an entry in a BE dictionary is unrecognized by the conforming
Guide for ASP.NET Barcode Web Server Control Open your project using Visual Studio, and add DLL to the You can also Add VB.NET to the Web Forms: Dim pages; Confirm the barcode and insert a image tag (img
pdf insert image; how to add an image to a pdf file
77
©
Adobe Systems Incorporated 2008 – All rights reserved
489
PDF 32000-1:2008
reader, it shall not affect the viability of the object. If a media criteria dictionary is present in both MH and BE,
the entries in both dictionaries shall be individually evaluated, with MH taking precedence (corresponding BE
entries shall be ignored).
Table 266 – Entries common to all rendition dictionaries
Key
Type
Value
Type
name
(Optional) The type of PDF object that dictionary describes; if present, shall
be Rendition for a rendition object.
S
name
(Required) The type of rendition that this dictionary describes. May be MR
for media rendition or SR for selector rendition. The rendition shall be
considered non-viable if the conforming reader does not recognize the value
of this entry.
N
text string
(Optional) A Unicode-encoded text string specifying the name of the
rendition for use in a user interface and for name tree lookup by JavaScript
actions.
MH
dictionary
(Optional) A dictionary whose entries (see Table 267) shall be honoured for
the rendition to be considered viable.
BE
dictionary
(Optional) A dictionary whose entries (see Table 267) shall only be honoured
in a “best effort” sense.
Table 267 – Entries in a rendition MH/BE dictionary
Key
Type
Value
C
dictionary
(Optional) A media criteria dictionary (see Table 268).
The media criteria dictionary behaves somewhat differently than other MH/
BE entries described in 13.2.2, “Viability.” The criteria specified by all of its
entries shall be met regardless of whether it is in an MH or a BE dictionary.
The only exception is that if an entry in a BE dictionary is unrecognized by
the conforming reader, it shall not affect the viability of the object.
Table 268 – Entries in a media criteria dictionary
Key
Type
Value
Type
name
(Optional) The type of PDF object that this dictionary describes; if present,
shall be MediaCriteria for a media criteria dictionary.
A
boolean
(Optional) If specified, the value of this entry shall match the user’s
preference for whether to hear audio descriptions in order for this object to
be viable.
NOTE 1
Equivalent to SMIL’s systemAudioDesc attribute.
C
boolean
(Optional) If specified, the value of this entry shall match the user’s
preference for whether to see text captions in order for this object to be
viable.
NOTE 2
Equivalent to SMIL’s systemCaptions attribute.
O
boolean
(Optional) If specified, the value of this entry shall match the user’s
preference for whether to hear audio overdubs in order for this object to be
viable.
S
boolean
(Optional) If specified, the value of this entry shall match the user’s
preference for whether to see subtitles in order for this object to be viable.
68
PDF 32000-1:2008
490
©
Adobe Systems Incorporated 2008 – All rights reserved
R
integer
(Optional) If specified, the system’s bandwidth (in bits per second) shall be
greater than or equal to the value of this entry in order for this object to be
viable.
NOTE 3
Equivalent to SMIL’s systemBitrate attribute.
D
dictionary
(Optional) A dictionary (see Table 269) specifying the minimum bit depth
required in order for this object to be viable.
NOTE 4
Equivalent to SMIL’s systemScreenDepth attribute.
Z
dictionary (Optional) A dictionary (see Table 270) specifying the minimum screen size
required in order for this object to be viable.
NOTE 5
Equivalent to SMIL’s systemScreenSize attribute.
V
array
(Optional) An array of software identifier objects (see 13.2.7.4, “Software
Identifier Dictionary”). If this entry is present and non-empty, the conforming
reader shall be identified by one or more of the objects in the array in order
for this object to be viable.
P
array
(Optional) An array containing one or two name objects specifying a
minimum and optionally a maximum PDF language version, in the same
format as the Version entry in the document catalog (see Table 28). If this
entry is present and non-empty, the version of multimedia constructs fully
supported by the conforming reader shall be within the specified range in
order for this object to be viable.
L
array
(Optional) An array of language identifiers (see 14.9.2.2, “Language
Identifiers”). If this entry is present and non-empty, the language in which the
conforming reader is running shall exactly match a language identifier, or
consist only of a primary code that matches the primary code of an identifier,
in order for this object to be viable.
NOTE 6
Equivalent to SMIL’s systemLanguage attribute.
Table 269 – Entries in a minimum bit depth dictionary
Key
Type
Value
Type
name
(Optional) The type of PDF object that this dictionary describes; if present,
shall be MinBitDepth for a minimum bit depth dictionary.
V
integer
(Required) A positive integer (0 or greater) specifying the minimum screen
depth (in bits) of the monitor for the rendition to be viable. A negative value
shall not be allowed.
M
integer
(Optional) A monitor specifier (see Table 270) that specifies which monitor
the value of V should be tested against. If the value is unrecognized, the
object shall not be viable.
Default value: 0.
Table 268 – Entries in a media criteria dictionary (continued)
Key
Type
Value
64
©
Adobe Systems Incorporated 2008 – All rights reserved
491
PDF 32000-1:2008
13.2.3.2 Media Renditions
Table 271 lists the entries in a media rendition dictionary. Its entries specify what media should be played (C),
how (P), and where (SP) it should be played. A media rendition object shall be viable if and only if the objects
referenced by its C, P, and SP entries are viable.
C may be omitted only in cases where a referenced player takes no meaningful input. This requires that P shall
be present and that its referenced media play parameters dictionary (see Table 279) shall contain a PL entry,
whose referenced media players dictionary (see 13.2.7.2, “Media Players Dictionary”) has a non-empty MU
array or a non-empty A array.
13.2.3.3 Selector Renditions
A selector rendition dictionary shall specify an array of rendition objects in its R entry (see Table 272). The
renditions in this array should be ordered by preference, with the most preferred rendition first. At play-time, the
renditions in the array shall be evaluated and the first viable media rendition, if any, shall be played. If one of
the renditions is itself a selector, that selector shall be evaluated in turn, yielding the equivalent of a depth-first
tree search. A selector rendition itself may be non-viable; in this case, none of its associated media renditions
shall be evaluated (in effect, this branch of the tree is skipped).
NOTE
This mechanism may be used, for example, to specify that a large video clip should be used on high-
bandwidth machines and a smaller clip should be used on low-bandwidth machines.
Table 270 – Entries in a minimum screen size dictionary
Key
Type
Value
Type
name
(Optional) The type of PDF object that this dictionary describes; if present,
shall be MinScreenSize for a rendition object.
V
array
(Required) An array containing two non-negative integers. The width and
height (in pixels) of the monitor specified by M shall be greater than or equal
to the values of the first and second integers in the array, respectively, in
order for this object to be viable.
M
integer
(Optional) A monitor specifier (see Table 293) that specifies which monitor
the value of V should be tested against. If the value is unrecognized, the
object shall be not viable.
Default value: 0.
Table 271 – Additional entries in a media rendition dictionary
Key
Type
Value
C
dictionary
(Optional) A media clip dictionary (see 13.2.4, “Media Clip Objects”) that
specifies what should be played when the media rendition object is played.
P
dictionary
(Required if C is not present, otherwise optional) A media play parameters
dictionary (see 13.2.5, “Media Play Parameters””) that specifies how the
media rendition object should be played.
Default value: a media play parameters dictionary whose entries (see
Table 279) all contain their default values.
SP
dictionary
(Optional) A media screen parameters dictionary (see 13.2.6, “Media Screen
Parameters”) that specifies where the media rendition object should be
played.
Default value: a media screen parameters dictionary whose entries (see
Table 282) all contain their default values.
69
PDF 32000-1:2008
492
©
Adobe Systems Incorporated 2008 – All rights reserved
13.2.4
Media Clip Objects
13.2.4.1 General
There are two types of media clip objects, determined by the subtype S, which can be either MCD for media
clip data (see 13.2.4.2, “Media Clip Data”) or MCS for media clip section (see 13.2.4.3, “Media Clip Section”).
The entries common to all media clip dictionaries are listed in Table 273.
13.2.4.2 Media Clip Data
A media clip data dictionary defines the data for a media object that can be played. Its entries are listed in
Table 274
NOTE 1
It may reference a URL to a streaming video presentation or a movie embedded in the PDF file.
Table 272 – Additional entries specific to a selector rendition dictionary
Key
Type
Value
R
array
(Required) An array of rendition objects. The first viable media rendition
object found in the array, or nested within a selector rendition in the array,
should be used. An empty array is legal.
Table 273 – Entries common to all media clip dictionaries
Key
Type
Value
Type
name
(Optional) The type of PDF object that this dictionary describes; if present,
shall be MediaClip for a media clip dictionary.
S
name
(Required) The subtype of media clip that this dictionary describes. May be
MCD for media clip data (see 13.2.4.2, “Media Clip Data”) or MCS for a
media clip section (see 13.2.4.3, “Media Clip Section”). The media clip shall
be considered non-viable if the conforming reader does not recognize the
value of this entry.
N
text string
(Optional) The name of the media clip, for use in the user interface.
Table 274 – Additional entries in a media clip data dictionary
Key
Type
Value
D
file
specification or
stream
(Required) A full file specification or form XObject that specifies the actual
media data.
CT
ASCII string
(Optional; not allowed for form XObjects) An ASCII string identifying the type
of data in D. The string should conform to the content type specification
described in Internet RFC 2045, Multipurpose Internet Mail Extensions
(MIME) Part One: Format of Internet Message Bodies (see the
Bibliography).
P
dictionary
(Optional) A me
dia permissions dictionary (see Table 275) containing
permissions that control the use of the media data. Default value: a media
permissions dictionary containing default values.
Alt
array
(Optional) An array that provides alternate text descriptions for the media clip
data in case it cannot be played; see 14.9.2.4, “Multi-language Text Arrays.”
Documents you may be interested
Documents you may be interested
