DLI Implementation and Reference Guide - Datalogics

2.6 DLI Implementation and Reference Guide
Adobe PDF Library Version Control
Concepts and Facilities: Guide to the DL Pager Composition System
There are two version issues that you may need to consider when building and
running your application: the version of Adobe PDF Library and DLI in use, and the
declared PDF version (or Compliance Level) being declared within the PDF output
being generated.
Obtaining Adobe PDF Library Version Number
The version number of the Adobe PDF Library which was initialized may be obtained
at any time after initialization as the return value of the method PDFLGetVersion:
• The high-order 16 bits of the value are the Major Version Number
• bits 8 through 15 are the Minor Version Number
• bits 0 through 7 are the Sub-minor Version Number
You may wish to have your application obtain and compare the returned Version
Number to the constant kPDFLVersion to see if the version of the Adobe PDF
Library being used at runtime is the same, greater, or less than the Version Number of
with which it was compiled.
PDF Level Declarations in Output
PDF output files declare their compliance level with a particular version of the PDF
Standard; e.g. documents created with Adobe PDF Library v6.x can declare PDF
v1.5. Applications reading, processing or displaying PDF output may inspect the
declaration within the file to determine how to process it. In particular, Adobe
Acrobat and Reader v5.x applications may produce a popup warning of possible
unsupported PDF features if they detect that the declared PDF level of the document is
higher than v1.4, even if the document does not in fact contain any functionality
unique to v1.5 or above.
The Adobe PDF Library is a set of routines associated with other Adobe products
such as Adobe Acrobat, Adobe Acrobat Distiller and Adobe Reader. The original
Adobe PDF Library was labeled as version 1.2 in order to maintain consistency with