Adobe PDF Library

Required components, Java and .NET applications

An independent copy of the core PDF Library DLL files are included in the Binaries folder under both the Java and the DotNET folders.

DLL files

All core DLL files located in \Binaries and the ICU DLL files are required.

DL150PDFL.dll PDF Library primary DLL file
DL150ACE.dll Adobe Color Engine
DL150AdobeXMP.dll XMP metadata
DL150AGM.dll Adobe Graphics Manager printing engine
DL150ARE.dll Adobe Raster Express
DL150AXE8SharedExpat.dll XML processing
DL150BIB.dll Bravo interface binder
DL150BIBUtils.dll Bravo interface binder utilities
DL150CoolType.dll CoolType Typography Engine
DL150JP2KLib.dll JPEG2000 Library
icucnv40.dll International Components for Unicode
icudt40.dll International Components for Unicode

Max Speed Libraries

Recent versions Adobe PDF Library include an alternate set of the core DLLs built with different 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.

Other required files

For .NET, the application will also need:

  • Datalogics.PDFL.dll

For Java, the application will also need:

  • com-datalogics-DL150PDFL.dll
  • com.datalogics.PDFL.jar

The Microsoft runtime libraries are required for both Java and .NET:

  • Microsoft.VC120.CRT
  • Microsoft.VC120.MFC

On Windows systems, copy the .dll files and .manifest files from the Microsoft.VC120 subdirectories into the executable directory or install the libraries globally using vcredist_x86.exe or vcredist_x64.exe. It is important to use the runtime libraries supplied with the specific distribution to ensure the correct version will be found.


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

DL150XPS2PDF.ppi XPS to PDF conversion
DL150PDFlattener.ppi transparency flattener
DL150PDFProcessor.ppi PDF/A and PDF/X conversions

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

DL150pdfport.dll Required by all of the plug-ins
DL150pdfsettings.dll Required by the XPS2PDF and PDFProcessor plug-ins


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, and some of them are quite large. 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 \Resources folder can be removed.

  • \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 .NET and Java interfaces will look for the Resources folder under the primary deployment folder. The Font, CMap, and Unicode path names can be specified during the Library initialization.