PDF文档标准ISO 32000-1：2008版规范详解

5星 · 超过95%的资源需积分: 50 74 浏览量更新于2024-07-24 3 收藏 8.48MB PDF 举报

ISO PDF 32000-1：2008 ISO PDF 32000-1：2008是PDF标准书，介绍了PDF文档的各项标准和要求。该标准由国际标准化组织（ISO）发布，Adobe Systems Incorporated参与制定。下面是对该标准的详细解释和相关知识点：一、 PDF标准书概述 PDF标准书是ISO 32000-1：2008的官方名称，该标准规定了PDF文档的格式、结构和内容。该标准的目的是确保PDF文档的可移植性、可读性和可靠性。二、 PDF文档的组成部分 PDF文档由多个组成部分组成，包括： 1. 文档目录（Document Catalog）：文档目录是PDF文档的入口点，提供了文档的基本信息和结构信息。 2. 页面树（Page Tree）：页面树是PDF文档的逻辑结构，描述了文档的页面组织方式和页面之间的关系。 3. 对象（Object）：对象是PDF文档的基本组成单元，包括文本、图形、图像等各种对象。 4. 字体（Font）：字体是PDF文档中用于呈现文本的字体信息，包括字体名称、字体样式和字体大小等信息。 5. 图形（Graphics）：图形是PDF文档中用于呈现图形和图像的信息，包括矢量图形和位图图像。三、 PDF文档的格式和结构 PDF文档的格式和结构是由ISO 32000-1：2008标准规定的，该标准定义了PDF文档的文件结构、对象结构和数据类型等信息。PDF文档的文件结构包括： 1. 文件头（Header）：文件头是PDF文档的开头部分，包含了文档的基本信息和文件结构信息。 2. 文件体（Body）：文件体是PDF文档的主体部分，包含了文档的内容信息和对象信息。 3. 文件尾（Trailer）：文件尾是PDF文档的结尾部分，包含了文档的结束信息和文件结构信息。四、 PDF标准的应用场景 PDF标准的应用场景非常广泛，包括： 1. 文档共享：PDF文档可以跨平台、跨应用程序共享，确保了文档的可移植性和可读性。 2. 打印输出：PDF文档可以直接输出到打印机，确保了文档的打印质量和可靠性。 3. 数字签名：PDF文档支持数字签名，确保了文档的安全性和不可篡改性。 4. 电子表单：PDF文档可以用于电子表单的创建和处理，确保了表单数据的安全性和可靠性。五、结论 ISO PDF 32000-1：2008是PDF标准书，规定了PDF文档的格式、结构和内容。该标准的应用场景非常广泛，包括文档共享、打印输出、数字签名和电子表单等。理解和掌握该标准对PDF文档的创建、处理和应用具有重要意义。

PDF 32000-1:2008

4.23

font

identified collection of graphics that may be

glyphs or other graphic elements [ISO 15930-4]

4.24

function

a special type of object that represents parameterized classes, including

mathematical formulas and sampled

representations with arbitrary resolution

4.25

glyph

recognizable abstract graphic symbol that is indepe

ent of any specific design [ISO/IEC 9541-1]

4.26

graphic state

the top of a push down stack of the graphics control parameters that define the current global framework within

which

the graphics operators execute

4.27

ICC profile

colour profile conforming to the ICC spe

ification [ISO 15076-1:2005]

4.28

indirect object

an object that is labeled with a positive integer objec

t number followed by a non-negative integer generation

number followed by obj and having endobj after it

4.29

integer object

mathematical integers with an implementation specified i

terval centered at 0 and written as one or more

decimal digits optionally preceded by a sign

4.30

name object

an atomic symbol uniquely defined by a sequence of character

introduced by a SOLIDUS (/), (2Fh) but the

SOLIDUS is not considered to be part of the name

4.31

name tree

similar to a dictionary that associates

ys and values but the keys in a name tree are strings and are ordered

4.32

null object

a single object of type null, d

enoted by the keyword null, and having a type and value that are unequal to those

of any other object

4.33

number tree

similar to a dictionary that associates keys an

values but the keys in a number tree are integers and are

ordered

4.34

numeric object

either an integer object or a real object

4.35

object

a basic data structure from which PDF files are constructed

d includes these types: array, Boolean,

dictionary, integer, name, null, real, stream and string

PDF 32000-1:2008

4.36

object reference

an object value used to allow one object to refer to another

; th

at has the form “<n> <m> R” where <n> is an

indirect object number, <m> is its version number and R is the uppercase letter R

4.37

object stream

a stream that contains a sequence of PDF objects

4.38

PDF

Portable Document Format file fo

at defined by this specification [ISO 32000-1]

4.39

real object

approximate mathematical real numbers, but with limited r

ange and precision and written as one or more

decimal digits with an optional sign and a leading, trailing, or embedded PERIOD (2Eh) (decimal point)

4.40

rectangle

a specific array object used to describe locations on a p

ge and bounding boxes for a variety of objects and

written as an array of four numbers giving the coordinates of a pair of diagonally opposite corners, typically in

the form [ ll

] specifying the lower-left x, lower-left y, upper-right x, and upper-right y coordinates of

the rectangle, in that order

4.41

resource dictionary

associates resource names, used in content str

eams, with the resource objects themselves and organized into

various categories (e.g., Font, ColorSpace, Pattern)

4.42

space character

text string character used to represent orthog

phic white space in text strings

NOTE 2 space characters include HORIZONTAL TAB (U+0009), LINE FEED (U+000A), VERTICAL TAB (U+000B),

FORM FEED (U+000C), CARRIAGE RETURN (U+000D), SPACE (U+0020), NOBREAK SPACE (U+00A0),

EN SPACE (U+2002), EM SPACE (U+2003), FIGURE SPACE (U+2007), PUNCTUATION SPACE (U+2008),

THIN SPACE (U+2009), HAIR SPACE (U+200A), ZERO WIDTH SPACE (U+200B), and IDEOGRAPHIC

SPACE (U+3000)

4.43

stream object

consists of a dictionary followed by zero or more byte

s b

racketed between the keywords stream and endstream

4.44

string object

consists of a series of bytes (unsigned integer values in th

e range 0 to 255) and the bytes are not integer

objects, but are stored in a more compact form

4.45

web capture

refers to the process of creating PDF content by importin

g a

nd possibly converting internet-based or locally-

resident files. The files being imported may be any arbitrary format, such as HTML, GIF, JPEG, text, and PDF

4.46

white-space character

characters that separate PDF syntactic constructs such as nam

es and

numbers from each other; white space

characters are HORIZONTAL TAB (09h), LINE FEED (0Ah), FORM FEED (0Ch), CARRIAGE RETURN (0Dh),

SPACE (20h); (see Table 1 in 7.2.2, “Character Set”)

PDF 32000-1:2008

4.47

XFDF file

file conforming to the XML Forms Data Format 2.0 specificatio

n, wh

ich is an XML transliteration of Forms Data

Format (FDF)

4.48

XMP packet

structured wrapper for serialized XML metadata that can be embedded in a wide variety of file formats

5Notation

PDF operators, PDF keywords, the names of keys in PDF dictionaries, and other predefined names are written

in bold sans serif font; words that denote operands of PDF operators or values of dictionary keys are written in

italic sans serif font.

Token characters used to delimit objects and descri

be the structure of PDF files, as defined in 7.2, "Lexical

Conventions", may be identified by their ANSI X3.4-1986 (ASCII 7-bit USA codes) character name written in

upper case in bold sans serif font followed by a parenthetic two

dig

it hexadecimal character value with the suffix

“h”.

Characters in text streams, as define

d by 7.9.2, "String Object Types", may be identified by their ANSI X3.4-

1986 (ASCII 7-bit USA codes) character name written in uppercase in

sans serif font followed by a parenthetic

four digit hexadecimal character code value with the prefix “U+” as shown in EXAMPLE 1 in this clause.

EXAMPLE 1 EN SPACE (U+2002).

6 Version Designations

For the convenience of the reader, the PDF versions in which various features were introduced are provided

informatively within this document. The first version of PDF was designated PDF 1.0 and was specified by

Adobe Systems Incorporated in the PDF Reference 1.0 document published by Adobe and Addison Wesley.

Since then, PDF has gone through seven revisions designated as: PDF 1.1, PDF 1.2, PDF 1.3, PDF 1.4, PDF

1.5, PDF 1.6 and PDF 1.7. All non-deprecated features defined in a previous PDF version were also included in

the subsequent PDF version. Since ISO 32000-1 is a PDF version matching PDF 1.7, it is also suitable for

interpretation of files made to conform with any of the PDF specifications 1.0 through 1.7. Throughout this

specification in order to indicate at which point in the sequence of versions a feature was introduced, a notation

with a PDF version number in parenthesis (e.g., (PDF 1.3)) is used. Thus if a feature is labelled with (PDF 1.3)

it means that PDF 1.0, PDF 1.1 and PDF 1.2 were not specified to support this feature whereas all versions of

PDF 1.3 and greater were defined to support it.

PDF 32000-1:2008

7Syntax

7.1 General

This clause covers everything about the syntax of PDF at the object, file, and document level. It sets the stage

for subsequent clauses, which describe how the contents of a PDF file are interpreted as page descriptions,

interactive navigational aids, and application-level logical structure.

PDF syntax is best understood by considering it as four parts, as shown in Figure 1:

• Objects. A PDF document is a data structure composed from a small set of basic types of data objects.

Sub-

clause 7.2, "Lexical Conventions," describes the character set used to write objects and other

syntactic elements. Sub-clause 7.3, "Objects," describes the syntax and essential properties of the objects.

Sub-clause 7.3.8, "Stream Objects," provides complete details of the most complex data type, the stream

object.

• File struc

ure. The PDF file structure determines how objects are stored in a PDF file, how they are

accessed, and how they are updated. This structure is independent of the semantics of the objects. Sub-

clause 7.5, "File Structure," describes the file structur

e. Sub-

clause 7.6, "Encryption," describes a file-level

mechanism for protecting a document’s contents from unauthorized access.

• Document structure. Th

e PDF document structure specifies how the basic object types are used to

represent components of a PDF document: pages, fonts, annotations, and so forth. Sub-clause 7.7,

"Document Structure," describes the overall document structure; later clauses address the detailed

semantics of the components.

• Co

ntent streams. A PDF co

ntent stream contains a sequence of instructions describing the appearance of

a page or other graphical entity. These instructions, while also represented as objects, are conceptually

distinct from the objects that represent the document structure and are described separately. Sub-clause

7.8, "Content Streams and Resources," discusses PDF content streams and

eir associated resources.

Figure 1 – PDF Components

In addition, this clause describes some dat

a structures, built from basic objects, that are so widely used that

they can almost be considered basic object types in their own right. These objects are covered in: 7.9,

"Common Data Structures"; 7.10, "Functions"; and 7.11, "File Specifications."

NOTE Variants of PDF’s object and file syntax are also used as the basis for other file formats. These include the

Forms Data Format (FDF), described in 12.7.7, "Forms Data Format", and the Portable Job Ticket Format

(PJTF), described in Adobe Technical Note #5620, Po

able Job Ticket Format.

7.2 Lexical Conventions

7.2.1 General

At the most fundamental level, a PDF file is a sequence o

f bytes. These bytes can be grouped into tokens

according to the syntax rules described in this sub-clause. One or more tokens are assembled to form higher-

Objects

File

structure

Document

structure

Content

stream

PDF 32000-1:2008

level syntactic entities, principally objects, which are the basic data values from which a PDF document is

constructed.

A non-encrypted PDF can be entirely represented using by

te values corresponding to the visible printable

subset of the character set defined in ANSI X3.4-1986, plus white space characters. However, a PDF file is not

restricted to the ASCII character set; it may contain arbitrary bytes, subject to the following considerations:

• The tokens that delimit objects and that describe the stru

cture of a PDF file shall use the ASCII character

set. In addition all the reserved words and the names used as keys in PDF standard dictionaries and

certain types of arrays shall be defined using the ASCII character set.

• The data values of strings and streams objects may be wr

itten either entirely using the ASCII character set

or entirely in binary data. In actual practice, data that is naturally binary, such as sampled images, is

usually represented in binary for compactness and efficiency.

• A PDF file containing binary data shall be transported as a

binary file rather than as a text file to insure that

all bytes of the file are faithfully preserved.

NOTE 1 A binary file is not portable to environments that impose reserved character codes, maximum line lengths, end-

of-line conventions, or other restrictions

NOTE 2 In this clause, the usage of the term character is en

tirely independent of any logical meaning that the value

may have when it is treated as data in specific contexts, such as representing human-readable text or

selecting a glyph from a font.

7.2.2 Character Set

The PDF character set is divided into three classes, called regu

lar, delimiter, and white-space characters. This

classification determines the grouping of characters into tokens. The rules defined in this sub-clause apply to

all characters in the file except within strings, streams, and comments.

The White-space characters sh

own in Table 1 separate syntactic constructs such as names and numbers from

each other. All white-space characters are equivalent, except i

n comments, strings, and streams. In all other

contexts, PDF treats any sequence of consecutive white-space characters as one character.

The CARRIAGE RETURN (0Dh) and LINE FEED (0Ah) char

acters, also called newline characters, shall be

treated as end-of-line (EOL) markers. The combination of a CARRIAGE RETURN followed immediately by a

LINE FEED shall be treated as one EOL marker. EOL markers may be treated the same as any other white-

space characters. However, sometimes an EOL marker is required or recommended—that is, preceding a

token that must appear at the beginning of a line.

NOTE The examples in this standard use a convention that arranges tokens into lines. However, the examples’ use of

white space for indentation is purely for clarity of exposition and need not be included in practical use.

Table 1 – White-space characters

Decimal Hexadecimal Octal Name

0 00 000 Null (NUL)

9 09 011 HORIZONTAL TAB (HT)

10 0A 012 LINE FEED (LF)

12 0C 014 FORM FEED (FF)

13 0D 015 CARRIAGE RETURN (CR)

32 20 040 SPACE (SP)

剩余755页未读，继续阅读

GPU大哥

粉丝: 2
资源: 11

PDF文档标准ISO 32000-1：2008版规范详解

ISO 32000 手册

PDF格式规范文档ISO32000(2008)

PDF32000-2008.pdf

ISO 32000-1:2008 - PDF 1.7技术标准详解

ISO 32000-1:2008 - 国际化PDF文件标准与使用规定

PDF32000-1:2008标准详解：PDF解析与格式转换指南

PDF32000-1:2008 - Adobe Portable Document Format标准与版权声明

ISO IEC TR 20000-7：2019 Information technology — Service management — Part 7：Guidance on the integration and correlation of ISO IEC 20000-1：2018 to ISO 9001：2015 and ISO IEC 27001：2013 -完整英文版（62页）.pdf

ISO IEC TR 20000-11：2015 Information technology — Service management — Part 11：Guidance on the relationship between ISO IEC 20000-1：2011 and service management frameworks：ITIL - 完整英文电子版（53页）.pdf

ISO IEC TR 20000-12：2016 Information technology — Service management — Part 12：Guidance on the relationship between ISO IEC 20000-1：2011 and service management frameworks：CMMI-SVC- 完整英文电子版（38页）.pdf

最新资源