CMYK color may be set using SCN, scn, K and k operators.

Available support for import of CMYK colors in R3 2018 Official Release.

In this case, we should use a default alpha source value which is the opacity source.

The signature field preserves information about the time of signing through the TimeOfSigning property of Signature.Properties. However, the DateTime object doesn't keep info about the time zone the document has been signed in. Some customers need to obtain this information.

While signing a document in Adobe Reader, the users can lock the document fields from editing. Expose a similar functionality.

The feature is described by the FieldMDP transform method, described on page 736 from the Pdf Reference 1.7

This happens only in cases when the Radio flag is not set and there are multiple widgets with different "ON" state names.

The issue may be reproduced by opening the attached PDF in Adobe Reader. Although the viewer initially shows the characters correctly, when you start typing in the TextBox, the umlaut/diacritics characters get corrupted. In other PDF viewers, the umlaut characters are handled correctly, so the issue seems to related to concrete Adobe Reader encoding handling implementation. The diacritic characters are handled incorrectly in other viewers as well (e.g. Chrome).

For details: https://www.adobe.com/devnet-docs/acrobatetk/tools/DigSig/Acrobat_DigitalSignatures_in_PDF.pdf

This feature is a must have for every business or enterprise!



Available in R2 2017 Release

For instance, we may implement WritePageAsync method in addition to the existing WritePage method. This is a similar scenario as in System.IO.StreamWriter class which has WriteLine and WriteLineAsync methods.

Add ability to create, import and modify layers (optional content) in a PDF document.

The exception is reproduced only with specific custom fonts and is thrown by the ComputeSubset() method of the GlyphTypeface class with the following message: "file does not conform to the expected file format specification". However, we can handle the exception and export the font data using the base class.

Fix available in LIB Version 2018.2.828.

The exception is thrown by System.Linq.Enumerable.Max method during the CidSet calculations.

Fix available in LIB Version 2018.2.730.

Usually, the entries are on neighboring rows. However, some producers introduce some extra blank rows between entries and this causes exception in RadPdfProcessing implementation.

Fix available in LIB Version 2018.2.625.

Importing document containing content with DeviceN color space causes System.InvalidCastException when the color components contain integer values

Fix available in R2 2018 SP1 release version.

The  FunctionType property is required according to PDF specification and we should always export it.

Fix available in R2 2018 SP1 release version.

Currently, a default constant value is used for the font size in this scenario.

Currently, there is internal API which is used by RadWordsProcessing PDF export functionality. We should consider making appropriate public API which would expose tab stops editing functionality.

Implemented import and export of IccBased, Indexed, Cmyk color spaces. Available in Q3 2015.

Available in R2 2018 Official Release version.

 This is content stream operator used for setting color in Device, CIE-based or Indexed color space.

Available in R2 2018 Official Release version.

Currently, when writing RadFixedPage the page instance reference is cached, as well as its content resources (images and fonts). This cache is important as it allows to reuse pages, images and fonts without writing them multiple times in the result PDF document. However, it needs to be optimized in order to consume less memory. 

The attached demo shows how to create 2500 pages with big images (different image on each page). With the current version, this demo consumes about 3 GB memory which may lead to OutOfMemoryException. With the optimization that will be introduced in LIB version, the same demo will consume about 20 MB memory for writing this big PDF document.

Available in LIB version: 2017.1.320

Some field values are initially not visible when opening file exported with RadPdfProcessing in Adobe Reader. The field value becomes visible once you click (focus) the field in Adobe Reader. The setting which causes this UI rendering issue may be found in "Edit" -> "Preferences" -> "Forms" -> "Highlight Color" -> "Show border hover color for fields". On the attached screenshots you may compare the rendering result when this setting is On and when it is Off.

Fix available in LIB Version 2017.2.710.