Table of Contents
  • Getting Started
  • EO.Pdf
    • Overview
    • Installation and Deployment
    • Using HTML to PDF
    • Using PDF Creator
      • Using PDF Creator
      • Getting Started
      • Advanced Formatting Techniques
      • Interactive Features
      • Low Level Content Objects
    • Working with Existing PDF Files
    • Using in Web Application
    • Advanced Topics
  • EO.Web
  • EO.WebBrowser
  • EO.Wpf
  • Common Topics
  • Reference
Overview

Overview

PDF Creator (ACM - Abstract Content Model) is a layout engine with a model very similar to that of HTML but is much simpler. It is very powerful and efficient, but generally requires more code than HTML to PDF. ACM is the main layout engine used before HTML to PDF was implemented.

When to use ACM instead of HTML to PDF?

HTML to PDF is much more powerful and easier to use, so usually you should start with HTML to PDF. However ACM is particular useful for the following scenarios:

  • You are not familiar with HTML. One of the main advantage of HTML to PDF is HTML is ubiquitous. However if it is still not in your world yet, then ACM might be an easier option;
  • Performance is extremely important. HTML to PDF is much more complex than ACM because the level of complexity involved for parsing HTML, CSS and scripts. For this reason ACM is usually faster;
  • Need access to low level interface such as working with transformation directly or output special curves or shapes. Such interface are available through ACM but do not exist through HTML to PDF;

Because both HTML to PDF and ACM renders to PdfPage and PdfDcoument, you can use them together on the same PDF file. A typical scenario is to use HTML to PDF to render the main contents but use ACM to render small "add-ons" such as rubberstamp, header and footer, etc. However you can also use it completely the other way around -- using ACM to render main content and use HTML to PDF to render a portion of the page.