Approved
Last Updated: 17 Jul 2018 15:41 by ADMIN
The property controls whether a paragraph should be rendered at least partially on the same page with the following paragraph when the document is shown in page view mode.
Approved
Last Updated: 17 Jul 2018 13:57 by ADMIN
Currently, the align attribute is supported only for a table and when applied to a cell or row is omitted on import.
Approved
Last Updated: 22 Jun 2018 12:28 by ADMIN
The Indent property of Table is not respected by PdfFormatProvider.
Approved
Last Updated: 05 Jun 2018 08:42 by ADMIN
Add support for importing HTML with syntax <img style="width: 300px; height: 300px;" /> At the moment only HTML attributes are supported.
Approved
Last Updated: 05 Jun 2018 08:27 by ADMIN
ADMIN
Created by: Anna
Comments: 2
Category: WordsProcessing
Type: Feature Request
3
There are multiple tags and attributes in the Open XML model which define the formatting of the complex script characters and are not implemented in the WordsProcessing model. 

Such tags are:
szCs: Complex script font size;
bCs: Complex script bold;
iCs: Complex script italic;

Attributes:
cstheme: Complex Script Theme Font;

The cs (Complex Script Font) attribute is implemented in the export, but it is not preserved in the model on import.
Approved
Last Updated: 04 Jun 2018 10:31 by ADMIN
ADMIN
Created by: Deyan
Comments: 2
Category: WordsProcessing
Type: Feature Request
7
Add support for import and export of floating tables.
Approved
Last Updated: 10 May 2018 10:28 by ADMIN
Add support for the <w:sym /> element, e.g.:

<w:r>
   <w:sym w:font="Wingdings" w:char="F0FC"/>
</w:r> 


From the specification:
"This element specifies the presence of a symbol character at the current location in the runs content. A symbol character is a special character within a runs content which does not use any of the run fonts specified in the rFonts element (17.3.2.26) (or by the style hierarchy).

Instead, this character shall be determined by pulling the character with the hexadecimal value specified in the char attribute from the font specified in the font attribute."

Currently such symbols are skipped during DOCX import.

Possible workaround: These tags are inserted from MS Word when the Symbol dialog in used. If the document is created with MS Word, the user could insert the symbol using the keyboard, in this case the character is inserted as a normal run.
Approved
Last Updated: 05 Apr 2018 14:22 by ADMIN
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.
Approved
Last Updated: 03 Apr 2018 10:19 by ADMIN
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();
                    }
Approved
Last Updated: 02 Apr 2018 13:40 by ADMIN
Currently, the text is exported but the strikethrough line is not drawn in the exported PDF.
Approved
Last Updated: 19 Mar 2018 14:08 by ADMIN
The vertical alignment of the table cells is not exported to PDF. The values are always exported with top alignment.
Approved
Last Updated: 09 Mar 2018 08:36 by ADMIN
ADMIN
Created by: Tanya
Comments: 2
Category: WordsProcessing
Type: Feature Request
1
This element specifies that the nearest ancestor structured document tag shall be of a document part type.

<w:sdt>
<w:sdtPr>
…
<w:docPartObj>
…
</w:docPartObj>
</w:sdtPr>
…
</w:sdt>
The docPartObj element in this structured document tag's properties specify that the type of structured document tag is a document part. The child elements must specify the gallery and category semantics for this part, if any.
Currently, such elements are skipped on import.
Approved
Last Updated: 06 Mar 2018 13:12 by ADMIN
When paragraph contains only merge fields (and eventually whitespaces), and all of these fields are evaluated to empty string for particular data record, the paragraph could be removed from the merged document.

Example: The document contains two paragraphs:
<<FirstName>>
<<LastName>> <<Address>>

For particular data record, LastName and Address are empty, so the merged document for this data record will contain only one paragraph (the first one). This behavior is expected from customers, as it's implemented by MS Word.
Approved
Last Updated: 20 Feb 2018 09:24 by ADMIN
ADMIN
Created by: Anna
Comments: 0
Category: WordsProcessing
Type: Feature Request
0
At the moment when a Floating Image is exported to HTML, it is exported as inline and its position is lost.
Approved
Last Updated: 13 Feb 2018 13:47 by ADMIN
ADMIN
Created by: Tanya
Comments: 0
Category: WordsProcessing
Type: Feature Request
0
The table height is currently not respected when applied to a table element through an attribute or through a CSS style. This setting is not respected in the flow document model, but we could import it and calculate the value to distribute it to the rows.
Approved
Last Updated: 31 Jan 2018 09:20 by ADMIN
ADMIN
Created by: Tanya
Comments: 0
Category: WordsProcessing
Type: Feature Request
0
Add support for importing the text values of the input element. They could be imported as a simple text to preserve the content.
Approved
Last Updated: 09 Jan 2018 13:25 by ADMIN
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.
Approved
Last Updated: 18 Dec 2017 16:41 by ADMIN
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.
Declined
Last Updated: 08 Nov 2017 12:40 by ADMIN
ADMIN
Created by: Peshito
Comments: 0
Category: WordsProcessing
Type: Feature Request
4
This property will control whether a table row may start on one page and end on the next page.

Declined: Duplicate with https://feedback.telerik.com/Project/184/Feedback/Details/190081-wordsprocessing-respect-tablerow-cansplit-property-when-exporting-to-pdf.
Approved
Last Updated: 08 Nov 2017 12:37 by ADMIN
Take into account the table row's CanSplit property when exporting to PDF from RadFlowDocument model. Is set to false, the table row should not be split between two pages, if possible.

This property could be set to false, for example, when importing MS Word documents with "Allow row to break across pages" unchecked for some table rows.