System.InvalidOperationException is thrown on the import of a document containing content control with no content when it is the first item in the current section. The message is: "Sequence contains no elements".

Bolding of some content on Import/Export. 

Exporting a document to PDF throws a System.ArgumentException: 'Width and Height must be non-negative.' The line height property is calculated to less than zero.

InvalidOperationException caused by some PageNumberType formats.

Incorrect measurement of spaces when they have a set size.

Exporting a document with a shape containing PictureFill fails with NullReferenceException.

Nested Mail Merge cannot handle empty lists.

Workaround: Replace the empty list with null.

A table cell with a dark background is always exported with a white foreground.

When border styles are both set inline and in CSS they are wrongly evaluated.

Arabic Letter Mark (ALM) is a non-printing character but is visible after PDF export.

Fonts that are not surrounded by curly braces cannot be imported in the RTF format

The paper source is lost when importing/exporting a docx file

Exception when converting table with empty runs in the cells.

 

 

List item (HTML) that contains paragraph is shown on the next line when exporting to PDF

When importing documents containing pictures with references represented with the r:link attribute, ArgumentNullException is thrown.

Empty lists with auto-close tags (i.e. <ol />) break the numbering of the lists declared after them.

Is there a way to prevent font embedding in the RadFlow methodology or is utilizing RadFixed the only way to have a reasonably sized PDF document?

Table columns are not the expected width after export while having large cropped images as content and all table content is resized. The input document's images are not resized and are too big to fit on the table and thus are cropped. 

PdfFormatProvider: NullReferenceException when exporting bookmarks spanning more than one paragraph.

When some character is not supported by the font, the fallback mechanism should try finding some other font that is capable of rendering the unsupported character. However, RadPdfProcessing fallback mechanism does not always find the correct font which sometimes result in wrong glyph visualization or in missing glyph.

Workaround: Font that supports these special characters may be used. This way the fallback mechanism will not be needed to export the PDF text.