Current implementation relies on valid cross-reference offsets in the PDF documents so that PDF objects are easily found and parsed. However, we can implement a mechanism for repairing documents with invalid cross-reference tables.

The attached project shows how to repair the simplest case of cross-reference table by using RepairDocumentWithSimpleCrossReferenceTable method.

Importing HTML list containing div element in the list item is leading to additional empty paragraph before the content:


Workaround: Using other Html elements (e.g. <p> or <span>) instead of <div>

Wrong measured column width when exporting to PDF after binaries version 2019.2.624.

The empty lines are not converted properly from RTF to HTML

Workaround: 

private static void FixEmptyParagraphs(RadFlowDocument document)
{
    var paragraphs = document.EnumerateChildrenOfType<Paragraph>();



    foreach (var paragraph in paragraphs)
    {
        if (paragraph.Inlines.Count < 1)
        {
            char nbsp = (char)160;
            paragraph.Inlines.AddRun(nbsp.ToString());
        }
    }
}

Add support for documents with an invalid stream cross-reference table

PDF/UA (PDF/Universal Accessibility) is the informal name for ISO 14289, the International Standard for accessible PDF technology.

'Value cannot be null. Parameter name: relationshipId' exception is thrown when an image does not have a relationship id specified. MS Word is showing the image as invalid but renders the document.

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.

Currently, ImportSettings allows importing a single stylesheet only. Users should be able to specify and load several external stylesheets.

One should be able to set the axis titles in the code. The attached images show an example of the exported document opened in Excel. 

 When exporting to HTML file, the table width is wrongly evaluated when the table width (in the original document) is set to fixed width.

Workaround: 
IEnumerable<Table> tables = this.document.EnumerateChildrenOfType<Table>();
foreach (Table table in tables)
{
table.PreferredWidth = new TableWidthUnit(TableWidthUnitType.Auto);
}

IEnumerable<Paragraph> paragraphs = this.document.EnumerateChildrenOfType<Paragraph>();
foreach (Paragraph paragraph in paragraphs)
{
paragraph.Spacing.SpacingAfter = 0;
}

One should be able to add hyperlinks.

 The table styles are not imported correctly form HTML.

Exception when the endstream is no on a new row 

When merging files that contain the "159 '\u009f'" char, ArgumentException("The encoding is not supported.") is thrown.

Workaround:

Use PdfFormatProvider.

Implement GetColor method for Indexed color space

Implement support for cell references to columns and rows, e.g. $1:$2, A:D, etc.

Currently, CellSelection.SetValue throws ParseException, and CellSelection.SetValueAsFormula throws InvalidOperationException. 

RadPDfProcessing: Exception when parsing a Tiling pattern with non-rgb color.

Currently, PdfStreamWriter writes only PDF pages.

If we implement API for merging multiple pages or whole documents we would be able to preserve links between pages (which are currently being corrupted).

Merging whole documents would also allow preserving document properties (bookmarks, interactive forms, ...). For a more detailed list of the unsupported document properties you can refer to our documentation: https://docs.telerik.com/devtools/document-processing/libraries/radpdfprocessing/formats-and-conversion/pdf/pdfstreamwriter/features.

We may also implement API for adding initial document properties from some existing PDF file.

When the bookmarks are declared as objects instead of a string they are not visible.