Currently, the text is exported but the strikethrough line is not drawn in the exported PDF.

When exporting hyperlink pointing to a bookmark, the resultant PDF document should contain Link annotation with destination pointing the bookmark's destination.

One important scenario to cover is the ability to import HTML with hyperlinks to anchors in the documents, and export them as working hyperlinks in the PDF document.

There are 27 types of border styles in the Open XML specification and they are implemented in RadFlowDocument. Only borders None and Single are supported when exporting to PDF, all others are treated as None and stripped.

Updates:

• The following feature request is created to handle the support of Thick, Dotted, Dashed, and DashSmallGap BorderStyles: Add support for Dotted, Dashed, and DashSmallGap borders.

Please subscribe to the tasks, so we can notify you when their status changes.

Provide support for Track Changes.

When exporting, an option of how to create the PDF bookmarks should be provided:
- Using the RadFlowDocument bookmarks
- Using document Headings

Enable customers to create and modify chart objects. The shapes featurе must be implemented before implementing this functionality.

Enable the customers to import SVG images and use them in their documents.

Add support for exporting shapes to PDF.

Currently the PageOrientation property is used to determine the actual size of the paper to use on the printer and does not reflect document's visualization. In order to affect Section's appearance the user should change the PageSize and PageMargin properties. For convenience the Rotate method is introduced in order to update the properties simultaneously. However the usage of the Section.Rotate(PageOrientation) method is confusing since the properties are not updated when Section.PageOrientation is already set to the same value as the parameter. Also, Rotate method is useful only for rotating already created sections, and to create section with specified pages size and margins the user should set all Section's PageSize, PageMargin, PageOrientation properties anyway.

More convenient API must be provided to create Section instances with correctly set properties for the desired page orientation.

Currently, this property is implemented only in DOCX and RTF exports.

The non-breaking hyphen element is currently not supported in the model and is stripped when importing the document.

Allow to password-protect a document, so that it cannot be shown (read) without the password. Also, enable opening encrypted documents.

Workaround for encrypting: PdfProcessing can be used to encrypt the document:

using (MemoryStream ms = new MemoryStream())
{
    PdfFormatProvider pdfProcessingFormatProvider = new PdfFormatProvider();
    Telerik.Windows.Documents.Flow.FormatProviders.Pdf.PdfFormatProvider pdfFormatProvider = new Telerik.Windows.Documents.Flow.FormatProviders.Pdf.PdfFormatProvider();
    pdfFormatProvider.Export(flowDocument, ms);
    RadFixedDocument fixedDocument = pdfProcessingFormatProvider.Import(ms);

    using (Stream output = new FileStream(outputPath, FileMode.OpenOrCreate))
    {
        pdfProcessingFormatProvider.ExportSettings.IsEncrypted = true;
        pdfProcessingFormatProvider.ExportSettings.UserPassword = "pass";
        pdfProcessingFormatProvider.ExportSettings.ImageQuality = ImageQuality.Medium;
        pdfProcessingFormatProvider.Export(fixedDocument, output);
    }
}

Add support for character spacing. Currently, such spacing cannot be set and are not imported.

The AltChunk element is responsible for embedding external content into documents.

The paragraphs in RadFlowDocument can have paragraph borders. These borders are not exported when exporting the document to PDF. 

Introduce Run.IsHidden property or similar, which hides the text in the document.

In MS Word, text is hidden using the Home -> Font -> Font -> Effects -> Hidden. In the Rtf format, such text is preceded (marked) with a '\v' tag. In OOXML, the tag is <vanish/>. The display: none; style from HTML is mapped to hidden text when document is converted to DOCX.

Hidden text is visualized with dotted underline when formatting symbols are shown. Hidden text is not exported to PDF.

Implement page border property which could be applied over the whole document or over a specific page.

The API should allow the client to navigate to an empty block container and manipulate it.

The block containers are Section, TableCell, Header, Footer, Comment.

The API should also include manipulation methods for a table like:

Add a row to a table.
Add a cell to a row.
Add a table to an empty cell.
Add a paragraph to an empty cell.
Add a run to an empty cell.
add a text to an empty cell.
Move to a next/previous cell.
Move to a next/previous row.

The API should use the currently applied editor formatting when creating the specified document elements.

Page breaks can be exported and subsequently imported using the "page-break-before: always; " property set of some elements.
Introduce support for break-[before/after] and page-break-[before/after].

This can eventually be extended to support "page-break-before: avoid" to preserve the value of the Paragraph.KeepWithNextParagraph property.
Attached to this item is a sample project demonstrating how an HTML file is imported into a RadFlowDocument, the custom page break string are replaced with Break elements of type PageBreak and then the RadFlowDocument is exported to PDF and DOCX files.

Implement support for pictures with references represented with the r:link attribute in the schema.