This feature is currently supported only for .NET Framework and WPF .NET Core for Windows assemblies.

If ImageInline's size is set through its Size property and not through Height or Width, the given size is not respected on export.

When there is a destination object in a RadFixedDocument and it doesn't have page set (it is null), an exception is thrown. However, this is supported by Adobe and it is not forbidden in the Pdf specification.

According to the specification, the startfref keyword must be followed by the offset the xref table start on, defined on a new line. Some documents, however, have both entries defined on the same line, which leads to InvalidOperationException with message "Stack empty" while importing. Make sure this case is handled in PdfProcessing as well.

When a TrueType font is defined, the mapping of character codes to glyph indices depends on the built-in cmap table mappings defined in the font and the Encoding property defined in the PDF dictionary.

However, the current implementation maps all characters with cmap tables for Microsoft Symbolic and Macintosh Roman, which causes incorrect mapping results, e.g. space characters are mapped to an Ê glyph.

The issue is also described in the following public item: TryGetCharCode for OpenTypeFont uses wrong cmap and returns wrong charcode.

Workaround: Change the font  of the TextBoxField's widget appearance:
foreach (var widget in field.Widgets)
{
    widget.TextProperties.Font = FontsRepository.Helvetica;
}

By specification when a form field is merged with the dictionary of the widget annotation, a Kids parameter can be existent if there are more than one widget annotations for that field. Support for importing such a fields should be added. 

I would like to request an example of the RadPdfProcessing library utilizing a Line Chart similar to how the Bar Chart is drawn in this example. 

Additionally, it would be great if there was an example with multiple charts on one page.

Thank you!

Add support for Lab color space to allow clients to import and export documents with Lab color space.

In principle, the blend function B (Cb , Cs ) is used in the compositing formula to customize the blending operation in Adobe transparency imaging model. The blending mode may define any function which yields another result color from the backdrop and source colors. This will allow overlaying objects on each other forming a transparency stack.

Support for the Blend Mode parameter of the external graphic state should be implemented.

When the content of a page is rotated, each glyph is exported on a new line.

Sometimes customers need to create documents using the CMYK colors to meet specific requirements for printing. Expose such functionality in PdfProcessing.

Importing document containing TextBox widgets with NormalContentSource defining text properties, such as FontSize and Position, are exported with incorrect appearance when the value of the field is modified.

Currently adding an Image content element with ImageSource instantiated with a PNG file format leads to NotSupportedException: 'Can not export other than Jpeg and Jpeg2000 and ImageQuality different than High', when exporting the document.

Support for adding PNG images and exporting to PDF should be implemented for PdfProcessing for .NET Standard scenario.

Support for exporting WMF (Windows Metafile) and EMF (Enhanced Metafile) images should be implemented.

Workaround: Convert the WMF images to PNG before exporting:

By the PDF format specification, CIDToGIDMap is optional. The default value is Identity. However when exporting CID Font with missing CIDToGIDMap property the analyzing tool causes the following warning message:

"PDF/A requires that a Type 2 CIDFont has a stream mapping from CIDs to glyph indices or the name Identity as its value."

When merging files the documents might have the same fonts embedded. Then the PdfProcessing should use only one of the fonts and skip embedding the second font in the resulting document.

Documents can be signed using the end certificate of a certificate chain, instead of the whole chain. This improves the performance of the signing.

When there is long text that is out of the used cell range area, this text should be included in page splitting calculations.

Also, when a cell has text that overflows its width, the text is again clipped by the cell boundaries and is not visible in the exported PDF. In a similar case Excel exports the surrounding cells to ensure that the content is visible.

Workaround: Extend the used cell range to include all the cells which the text content spans.

Some documents result in glyphs with wrong widths after import-export. Widths are mixed making some of them to overlap and others to have bigger distance.