Apitron PDF Kit

From
Jump to: navigation, search

Overview

Apitron PDF Kit is a .NET component that provides API for creating, editing, digitally signing and manipulating the content of PDF documents. It supports adding text, images, drawings, annotations and basically all available content types defined by the PDF specification. The library contains 100% managed code and is available for any .NET framework version starting from 2.0. Xamarin/MONO, Silverlight and Windows Phone versions are provided in addition to the main builds.

For version history, purchasing or downloading visit the Apitron PDF Kit product page.

Supported PDF versions and subtypes

Documents saved using PDF versions starting from 1.4 until 2.0 can be opened, edited and saved, with PDF 2.0 being the latest version of the specification . Files can be normal, tagged, password-protected, signed, incrementally updated. PDF/A is supported as well, namely PDF/A-1A, PDF/A-1B, PDF/A-2A, PDF/A-2B, PDF/A-2U (unicode).

Support for digital signatures

The digital signing of PDF documents is implemented with extensibility in mind. So in addition to providing the own implementation for the common standards, the product supports third party signing implementations that makes it suitable for using hardware certificate storages like Suisse ID, Bank ID and others issued by governments, affiliated parties or large corporations which integrate with target OS using custom Crypto API drivers or tokend implementations. OCSP responses and CRLs combined with timestamps from third party servers can be embedded as well.

Platforms

The Apitron PDF Kit library can be used to create cross-platform desktop, mobile, web and cloud solutions. Using this component you'll be able to create or build applications and services for:

  • Windows desktop systems (Windows Forms, WPF, Silverlight, console apps, windows services)
  • Windows Phone 8.1\10, Windows Store and Windows Runtime, Windows 10 UWP
  • Xamarin.Android, Xamarin.iOS, OS X (using MONO or Xamarin)
  • Azure Web or Worker Roles, Azure Web Jobs
  • Any system where .NET, .NET Core or MONO implementation exists

using command line utilities or any suitable IDE e.g. Visual Studio, Visual Studio for Mac, Visual Studio Code, MonoDevelop etc.

See cross-platform development using Apitron PDF Kit article for more information.

Features from functional perspective

Features mapped to specification structure

  1. Graphics
    1. Extract, modify and add graphic objects (Paths, Text, XObjects, Inline images, Shading objects)
    2. Overview
      1. Native PDF Coordinate systems
      2. Device and User coordinate spaces
    3. Graphics State
      1. Graphics State Stack
      2. Graphics State operators and parameters
    4. Support for path construction, path-painting and clipping operators
    5. Colorspaces
      1. Device (RGB, CMYK, GRAY)
      2. CIE-based (CalRGB, CalGRAY, Lab, ICCBased - via ICC color profile)
      3. Special (Pattern, DeviceN, Indexed, Separation)
    6. Patterns
      1. Tiling patterns (colored, uncolored)
      2. Shading patterns (type1, type2, type3)
    7. Images
      1. Standard images in common formats
      2. Masked images
        1. Stencil masked
        2. Explicitly masked
        3. Color key masked
      3. Inline
    8. Form XObjects
    9. Optional content (layers)
  2. Text
    1. Text state parameters and operators
      1. General (text font and size)
      2. Character spacing
      3. Word spacing
      4. Horizontal scaling
      5. Leading
      6. Text rendering mode
      7. Text rise
    2. Text Objects
      1. Text positioning operators
      2. Text showing operators
    3. Simple fonts
      1. Standard fonts
      2. Type 1 fonts
      3. TrueType fonts
      4. Type 3 fonts
    4. Composite fonts
      1. Type 0 fonts
    5. Embedded font programs (fonts)
    6. Extraction of Text Content
  3. Transparency
    1. Blend modes
    2. Alpha
    3. Transparency groups
    4. Soft masks
  4. Interactive Features
    1. Viewer preferences
    2. Document-level navigation
      1. Destinations
        1. Explicit destinations
        2. Named destinations
      2. Document outline
      3. Collections(attachments management)
    3. Page-Level navigation
      1. Page labels
      2. Articles
    4. Annotations
      1. Appearance streams
      2. Annotation types (FreeText, Markup, RubberStamp etc.)
    5. Actions
      1. Trigger events
      2. Action types (GoTo, JavaScript, URI etc..)
    6. Interactive forms
      1. Fields
      2. Form actions
      3. Named pages
      4. Non interactive forms
      5. Code samples
    7. Digital signatures
      1. Long term validation of signatures
      2. CAdES signatures as used in PDF
      3. Code samples
  5. Encryption
    1. Standard encryption
    2. Certificate encryption
    3. Custom Encryption
    4. Unecrypted Wrapper
  6. Document Interchange
    1. Metadata
    2. Marked content
    3. Logical structure
    4. Tagged PDF

API highlights

The library can be divided into two large parts, demonstrating different approaches to PDF creation and manipulation. Being independent from each other they share several common objects and can be used together to achieve a complex result.

FixedLayout API

This part is built around the FixedDocument class and provides “classic” approach for PDF manipulation. It has 100% mapping to spec-defined entities and can be used for every task where the developer needs precise control over the things which are to be put on PDF page and the way it should be done. The developer can get access to all drawing commands and content of the page; everything in PDF document can be manipulated using this API. See the article Fixed layout API for the details.

FlowLayout API

This part is built around the FlowDocument class and provides innovative and flexible approach for generating PDF documents using styles-based, html- and css- like document model. Developers can use it when they need automatic layout rules applied to the content blocks. The developer doesn't set the explicit position of content elements on page, but rather control the layout behavior using built-in styling mechanism similar to how the CSS is used with HTML. Content for the document has to be built using predefined content elements, e.g. TextBlock, Image, Grid etc. while the flow layout engine performs automatic pagination or splitting if necessary. See the article Flow layout API for the details.

Scalability and development process

File processing and parsing is being done using all available processor cores, so applications are scaling well when you increase the processing power. It's especially important for server-side/cloud solutions. The build system use continuous integration including automated testing environment running thousands of test every day, and ensuring the component’s solidness and reliability. It helps the dev team to quickly track and fix possible problems before the new version is released. Customers' contribution is always welcome, so if you find any problems don't hesitate to contact us with your suggestions.

Licensing

All Apitron's software components employ the same licensing scheme described in details in a separate article.