Adobe® PDF Library

Required components, Java and .NET applications

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

DLL files

All library files located in \Binaries including the ICU library files are required.

DL180PDFL.dll PDF Library primary DLL file
DL180ACE.dll Adobe Color Engine
DL180AdobeXMP.dll XMP metadata
DL180AGM.dll Adobe Graphics Manager printing engine
DL180ARE.dll Adobe Raster Express
DL180AXE8SharedExpat.dll XML processing
DL180BIB.dll Bravo interface binder
DL180BIBUtils.dll Bravo interface binder utilities
DL180CoolType.dll CoolType Typography Engine
DL180JP2K.dll JPEG2000 Library
icuuc68.dll (APDFL 18)
icucnv40.dll (APDFL 15)
International Components for Unicode
icudt68.dll (APDFL 18)
icudt40.dll (APDFL 15)
International Components for Unicode

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.

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-DL180PDFL.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.VC###.CRT and .MFC  subdirectories into the executable directory or install the libraries globally using vc_redist.x86.exe or vc_redist.x64.exe. It is important to use the runtime libraries supplied with the specific distribution to ensure the correct version will be found.

The Java and .NET interfaces depend on these Microsoft runtime libraries. When you build your own Windows application for the Adobe PDF Library, you need to copy these files to the same folder where you copy Datalogics.PDFL.dll.


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

DL180XPS2PDF.ppi XPS to PDF conversion
DL180PDFlattener.ppi transparency flattener
DL180PDFProcessor.ppi PDF/A and PDF/X conversions

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

DL180pdfport.dll Required by all of the plug-ins
DL180pdfsettings.dll Required by the XPS2PDF and PDFProcessor plug-ins

Optical Character Recognition (OCR) processing

The Java and .NET interfaces for the Adobe PDF Library provide an Optical Character Recognition (OCR) utility that can recognize images in a PDF document. The OCR utility recognizes text within each image, and then saves that text to a new PDF export file, with that text underlaying the image where it was found.

The Adobe PDF Library uses a software product called the Tesseract 3 OCR Engine. The tessdata directory holds the language files to support OCR processing to identify text in images in PDF documents. The default languages offered include English, Dutch, French, German, Italian, Spanish, and Portuguese, as well as Mandarin, Japanese, and Korean.

Note that the OCR engine in Adobe PDF Library is only compatible with the Windows 64 and Linux 64 platforms.

The OCR engine library is stored in the /Binaries directory, under Java and DOTNET:

dltesseract3.dll Windows Linux

Two sample programs show how to use OCR processing, AddTextToImage and AddTextToDocument. These samples are available for both Java and C# and are found in the /OpticalCharacterRecognition folder for Java and C#.


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 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.
  • tessdata. This folder is optional, except for applications that use the OCR engine.

The .NET and Java interfaces will look for the Resources folder under the primary deployment folder. The Font, CMap, Color, and Unicode path names can be specified during the Library initialization.