DLL files

All core DLL files located in \Binaries, for C++, and the ICU DLL files, are required.

In the icu files above, “cnv” refers to conversions, and “dt” to data. The cnv DLL file has the logic to convert between encodings, while the dt DLL file is data only, containing the tables that describe each code point attribute.

Plug-ins

There are three optional plug-ins with supporting DLL files:

The XPS to PDF conversion plug-in is not supported on IBM AIX or MacOS for the C Language interface.

These two DLL files are needed if you want to use the plug-ins:

The plugin PPI files must be stored in the folder specified by the pluginDirList entry of the PDFLDataRec.

For Linux or macOS the DLL and plug-in files will have similar names, but may begin with lib and end with .so, .framework, or .dylib.

Max Speed Libraries (Windows only)

Recent versions Adobe PDF Library include an alternate set of DLLs built with more aggressive compiler options from the standard DLL files. These Maximum Speed Library files may improve system performance. They are found in the \MaxSpeedLibs folder and may be used in place of the core DLLs found in the libs folder. Note that these DLL files require SSE2 processor instruction support. They are available only on Windows platforms.

Note that the MaxSpeedLibs directory is only provided with Adobe PDF Library 15. The directory is no longer needed with APDFL 18.

Resources

The files found in the folders under Resources are used for a variety of operations, including creating/setting text and extracting or parsing content. Most of these are font files. Datalogics recommends that you include all of the resources in the Resources tree with your distribution. If, however, you need to limit the total size of the files included in your application, some of the components in the Resource folder can be removed.

When deploying, it is important to consider where the resources will be located on the target machine, as opposed to the development machines. For the sample programs included with the release, APDFL initialization is handled by the MyPDFLibUtils.cpp utility code. MyPDFLibUtils.cpp uses relative paths in the PDFLData object to locate the resources. Your application must change these as required for your deployment.

• Font. This folder includes CJKV fonts. These are Multi-byte (16 bit) character fields mostly used by Chinese, Japanese, Korean, and Vietnamese characters (CJKV). Thus a CJKV character is twice as wide as a normal single-byte character space. The double byte character field is needed because these languages have so many characters that a single 8 bit character field is not enough to represent all of them, but the font files that result tend to be larger than typical fonts. You can leave these files out of your distribution package if you will not be processing documents with CJKV content.
• CMap . Some fonts in PDF files use predefined mappings between character encodings and specific, predefined character identifier sets. These mappings are called Character Maps (CMaps), and we recommend that they all be included with your distribution, even though they can be quite large.
• Joboptions. Joboption files are used only by the standard plug-ins provided with the Library. You can leave them out of your distribution if your applications will not be using the plug-ins.
• Color. This is used for rendering, printing, and conversion operations, as well as the XPS2PDF plugin.
• Unicode. Used for text extraction and for text conversion during printing, rendering, and conversion operations. We recommend that all Unicode font files be included. Unicode is an international font standard.

The Resource files must be stored in the folders specified by the dirList, cMapDirectory, colorProfileDirList, and the unicodeDirectory of the PDFLDataRec.