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);
    }
}

Run's default constructor creates it with Text = null. When document with such run is exported to PDF, NullReferenceException is thrown.

Workaround: Create the Run and immediately set its Text property to string.Emtpy.

Available in LIB Version 2018.1.423.

Currently there is no easy way to modify the properties of bookmarks and fields in the document. Think of providing API for easier manipulation.

For example, following is one of the easiest approached to change the target of hyperlinks:

                    var hyperlinkStarts = document
                        .EnumerateChildrenOfType<FieldCharacter>()
                        .Where(fc => fc.FieldCharacterType == FieldCharacterType.Start && fc.FieldInfo.Field is Hyperlink);

                    foreach (var fieldCharacter in hyperlinkStarts)
                    {
                        int indexOfCodeRun = fieldCharacter.Paragraph.Inlines.IndexOf(fieldCharacter) + 1;
                        Run hyperlinkCode = (Run)fieldCharacter.Paragraph.Inlines[indexOfCodeRun];

                        string oldUri = ((Hyperlink)fieldCharacter.FieldInfo.Field).Uri;
                        string newUri = "mailto:mail@mail.com";

                        hyperlinkCode.Text = hyperlinkCode.Text.Replace($"\"{oldUri}\"", $"\"{newUri}\"");
                        fieldCharacter.FieldInfo.UpdateField();
                    }

If the background color is applied to <tr> element then it is not imported.

Workaround: The background color may be applied to the cells (<td> elements) in the desired row and this should have the same effect.

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

Add support for exporting hyperlinks which are not valid URIs to PDF. Currently such hyperlink URIs are not exported to the PDF document.

Example of such hyperlink is "mailto:abc%20abc-abc-abc%20%3cabc@abc.com%3e" (mailto:abc abc-abc-abc <abc@abc.com>), but there could be more types. Currently the internal API relies on creating instance of the system Uri class, which is not possible in this case.

When a break element is defined in the middle of a Run, DocxFormatProvider imports it at the end of the same run. For example, the following content: 

<w:r>
  <w:t>This is</w:t>
  <w:br/>
  <w:t xml:space="preserve"> a simple sentence.</w:t>
</w:r>

Results in "This is a simple sentence " + break element after it.

Add support for setting and exporting document metadata, like Title, Author and similar.

The measurements of the table cell are incorrect and an ArgumentException is thrown in TableCell.Draw when trying to create a rectangle with negative height: "Width and Height must be non-negative." 

The issue is reproducible only in a specific setup with a specific document. It is related to the calculations of the line spacing when the table row should be split between two pages.

Workaround: Change the line spacing:
foreach (var paragraph in this.document.EnumerateChildrenOfType<Paragraph>())
{
    paragraph.Properties.LineSpacingType.LocalValue = HeightType.Auto;
    paragraph.Properties.LineSpacing.LocalValue = 1;
}

The exception is thrown because we try to export a tblGrid element, but currently we do not support this: https://feedback.telerik.com/Project/184/Feedback/Details/190082-wordsprocessing-export-tblgrid-table-grid-property-for-table-elements

Add support for importing the text values of the input element. They could be imported as a simple text to preserve the content.

The exception is thrown because the AltChunk element is added for import, but we currently do not have implementation for importing of AltChunk elements: https://feedback.telerik.com/Project/184/Feedback/Details/190095-wordsprocessing-add-support-for-altchunk-element

The theme xml element (root of the theme.xml part) has a name property which is optional. However, WordsProcessing throws an exception when it doesn't find a name.

When a document has a deleted text as part of track changes and there is a comment on the deletion, the document throws InvalidOperationException upon import.

In addition to the values containing numbers, the font-size property can have one of the following values as well: medium|xx-small|x-small|small|large|x-large|xx-large|smaller|larger|initial|inherit;
At this point, HtmlFormatProvider skips these values and applies default font-size to the content.


To import similar content with the proper styling, the customer can replace the CSS keywords with their equivalents in px.

When the current position is in the middle of a paragraph and the InsertSection() method is invoked, it should automatically split the content at the current position and transfer the content that is on the right side of the position to the new section along with all the following blocks. 

At this point, the method transfers only the content of the current paragraph and, if the section has following paragraphs, they are left in the "old" one.

At the moment when a Floating Image is exported to HTML, it is exported as inline and its position is lost.

When a document with ordered list is exported to RTF and opened with WordPad or WinForms' system RichTextBox the numbers of the list are replaced by "{0}".

Implement import of bullets and numbering which use the old Word 6.0/Word 95 format from RTF. This includes, but is not limited to, the following RTF tags: \pnlvlN, \pnlvlblt, \pnlvlbody, \pnlvlcont. See RTF specification, "Word 6.0 and Word 95 RTF" heading for full description.
WordPad and some legacy systems export lists with this formatting, so the construction is relatively widespread.
According to the specification, if RTF reader doesn't support specific bullets/numbering tags, it can use the \pntext tag to read the bullets/numbering as plain text; but currently WordsProcessing always ignores the \pntext tag. Because of this, the bullets or numbers of lists in the old format are missing after import.