CHAPTER 3
180
Syntax
location/login, fragment identifier, query information, and parameter sections
are not allowed.
In the case of other file systems, a relative file specification is converted to an
absolute file specification by removing the file name component from the
specification of the containing PDF file and appending the relative file
specification in its place. For example, the relative file specification
ArtFiles / Figure1 . pdf
appearing in a PDF file whose specification is
/ HardDisk / PDFDocuments / AnnualReport / Summary . pdf
yields the absolute specification
/ HardDisk / PDFDocuments / AnnualReport / ArtFiles / Figure1 . pdf
The special component
. .
(two periods) can be used in a relative file specification
to move up a level in the file system hierarchy. When the component immediately
preceding
. .
is not another
. .
, the two cancel each other; both are eliminated from
the file specification and the process is repeated. Thus, in the example above, the
relative file specification
. . /. . / ArtFiles / Figure1 . pdf
would yield the absolute specification
/ HardDisk / ArtFiles / Figure1 . pdf
Conversion to Platform-Dependent File Names
The conversion of a file specification to a platform-dependent file name depends
on the specific file naming conventions of each platform:
•
For DOS, the initial component is either a physical or logical drive identifier or
a network resource name as returned by the Microsoft Windows function
WNetGetConnection
, and is followed by a colon (
:
). A network resource name is
constructed from the first two components; the first component is the server
name and the second is the share name (volume name). All components are
then separated by backslashes. It is possible to specify an absolute DOS path