Paint content stream operator ("Do" in PDF specification) currently draws only Image XObjects. We should implement support for Form XObjects. 


Available in R2 2017 Release

Currently, only images without transparency may be created with this class.

Available in LIB version 2017.1.410.

This leads to keeping a lot of memory when exporting pages from multiple PdfFileSource instances which are created from MemoryStream.

Available in LIB version: 2017.1.320

This new API will not read/delete the existing PDF pages content and this would allow performance and memory efficient realization of the following scenarios: 

 - Merge PDF document pages from different PDF files.

 - Split PDF document pages to separate PDF files.

 - Append/Prepend PDF content to existing PDF pages.

Moreover, as this approach will not require reading/deleting existing PDF page content, it will not depend on complex PDF features and will depend only on the PDF file structure. This will allow processing of PDF documents which use less common PDF features which are currently not supported by the existing PdfProcessing API.


Available in R1 2017 Release

The "g" and "G" operators are used for setting color with a single component.


Available in R1 2017 Release

Measuring big paragraphs is time consuming and may be optimized.

Currently every text fragment is exported by specifying all its properties. When there are many fragments one after another we may skip specifying the properties for every single fragment. This will improve both memory and time consumption performance.

From R1 2017 all annotations (including sound and video) are supported for import-export scenarios by using PdfStreamWriter class. 

These feedback item will be opened as we may add API for generating and inserting new sound annotations from scratch in the file.

As one can use annotations we should support attachments per page or per pdf-file.

This is happening when the pages in the document has content arrays similar to the following:

[34 0 R 243 0 R] [34 0 R 245 0 R] [34 0 R 247 0 R] ....

As you may notice the content stream 34 0 R is reused and the issue is caused by incorrect caching of content stream indirect objects by their reference.

The issue is reproducible only with nested tables - tables positioned inside some other table cell. When using simple tables the text is always wrapped and rendered correctly. This may be used as a workaround for scenarios which allow replacing nested tables with simple ones.

PDF Editor: the pdfiewer will now have a feature to perform the following:

Sort pages by dragging and dropping selected pages.
After adding stamps/annotations on the page, user will be able to move around those objects by dragging and dropping.

Possibility to convert a PDF file to EPS file.

As some other decoders, JBIG2 may also handle different parameters in order to correctly decode the stream. Currently, decode parameters are not supported for this decoder.

When a source RadFixedDocument is merged to a target RadFixedDocument, the content of the source document is cleared.

This may cause either big distance between some glyphs, or overlapping glyphs.