This API should provide a method for removing all fields and widgets in the document and draw the default widget appearance in place of the removed widgets.

WORKAROUND: Sample implementation for flattening form fields may be seen in the FlattenFormFields method from the attached demo project.

Hello Telerik,

Last time we attempted this the <Viewbox> contents would not render and were empty upon xaml to pdf output. It would be great if you had this feature and we could move completely away from raster output to PDF for controls that contain Viewboxes. Otherwise we have really liked the PDF's created by the tool, the vector output is sharp as expected.

Thank you,

Patrick

Add support for shapes, and especially for shapes with textual content. 
In OOXML, shapes are represented by the wps:wsp element, and shapes with textual content by <wps:txbx>, <w:txbxContent>.
Such shape can be added to a Word document using the Insert -> Text -> Text Box -> Draw Text Box, or through a shape's context menu -> Add Text.

Do not confuse these shapes with Text/Rich Text content controls (see https://feedback.telerik.com/Project/184/Feedback/Details/190057 )

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. 

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.

We would like to have image formats like JPG, PNG and TIFF supported in addition to the PDF and Office document support in DPL.

Introduce new section properties which are responsible for defining columns in the section.

Currently Run.Shading is not exported to PDF.

Note: This scenario is common when converting HTML to PDF, as Run.Shading is set when construct like <span style="background-color:#ffcc00;"> is used.

Workaround: Iterate all the Runs in the already imported HTML document and set their HighlightColor to Shading.BackgroundColor.LocalValue. Check this code snippet:

foreach (Run run in document.EnumerateChildrenOfType<Run>())
{
	if (!run.Properties.HighlightColor.HasLocalValue)
	{
		run.HighlightColor = run.Shading.BackgroundColor.LocalValue;
	}
}

This operator is used for drawing shading patterns.