Unplanned
Last Updated: 05 Oct 2017 10:15 by ADMIN
ADMIN
Created by: Deyan
Comments: 2
Category: WordsProcessing
Type: Feature Request
4
This field allows performing a mail merge operations with labels representing different source items on the same page.
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.
Unplanned
Last Updated: 04 Dec 2018 15:49 by ADMIN
Created by: Liu
Comments: 0
Category: WordsProcessing
Type: Feature Request
4

This element specifies the settings for the document grid, which enables precise layout of full-width East Asian language characters within a document by specifying the desired number of characters per line and lines per page for all East Asian text content in this section.

If Latin text is interspersed on this line, then it is placed across the number of grid units needed to fit the
content, but all other grid positions are unaffected.

Unplanned
Last Updated: 23 Sep 2024 08:49 by ADMIN
Created by: Hannah
Comments: 2
Category: WordsProcessing
Type: Feature Request
4

The mail merge should support conditional fields. Here is an example:

{ IF [Condition] [Display Result 1] [Display Result 2] }

Completed
Last Updated: 29 Jul 2020 07:04 by ADMIN
Release R3 2020
ArgumentException is thrown when importing an RTF document which has a font size is set to zero (\fs0).
Completed
Last Updated: 04 Jun 2020 09:42 by ADMIN
Release R2 2020 SP1
KeyNotFoundException is thrown when importing RTF document which has an invalid Font Family name.
Unplanned
Last Updated: 15 Apr 2020 09:52 by ADMIN
Currently, the Multilevel Numbering list is supported but when nesting one-level Numberings this results in wrongly exported to HTML multilevel list. 
Unplanned
Last Updated: 15 Oct 2020 05:34 by ADMIN
Created by: Dimitar
Comments: 0
Category: WordsProcessing
Type: Feature Request
4
The Open Document Format for Office Applications (ODF), also known as OpenDocument, is an open standard file format for spreadsheets, charts, presentations, and word processing documents using ZIP-compressed[6] XML files.

The most common filename extension for word processing (text) is .odt.
Unplanned
Last Updated: 01 Apr 2021 14:31 by ADMIN
Created by: Antonio
Comments: 0
Category: WordsProcessing
Type: Feature Request
4
This will allow users to use the same list and styling for paragraphs but separate the lists by restarting them.
Completed
Last Updated: 02 Aug 2024 11:09 by ADMIN
Release 2024.3.802 (2024 Q3)
ADMIN
Created by: Peshito
Comments: 5
Category: WordsProcessing
Type: Bug Report
4

List indent is not correct when exported to PDF. All indents start from the same position.

Unplanned
Last Updated: 15 Aug 2022 07:16 by Scott

Exception when there are merge fields in the header/footer and one performs mail merge: 

Unable to cast object of type 'Telerik.Windows.Documents.Flow.Model.Header' to type 'Telerik.Windows.Documents.Flow.Model.BlockBase

Unplanned
Last Updated: 08 Sep 2017 06:14 by ADMIN
Created by: Florian
Comments: 1
Category: WordsProcessing
Type: Feature Request
3
Make it possible to link files (read: excel table) into word documents, so the editing experience in e.g. word allows to navigate to the linked file.

Ms Word and OOXML allow insertion of files in a docx document. This results in OLEOobject referring to the embedded file.
Unplanned
Last Updated: 18 Aug 2017 09:58 by ADMIN
Now headings are imported with default heading styles.

Introduce an option for Heading styles to be exported as <h1> - <h6> tags. Consider whether this should be the default behavior, because MS Word exports Headings with H tag and additionally adds styling so the resulting HTML will visually look the way it does in MS Word.
Unplanned
Last Updated: 15 Feb 2022 16:56 by Joshua
ADMIN
Created by: Deyan
Comments: 1
Category: WordsProcessing
Type: Feature Request
3
Add support for smart tags (described in the OOXML using the smartTag element). As currently smart tags are not supported, the content inside them is not imported from docx.
Unplanned
Last Updated: 07 Jun 2022 11:25 by ADMIN
This is only reproducible when the Run contains an empty string. If the paragraph is empty or the Run contains a space, everything is working correctly.

Workaround: Remove all empty runs from the document.
Unplanned
Last Updated: 18 Aug 2017 10:16 by ADMIN
At this point only styling through CSS is supported. The below code does not align the paragraph to the center

            string import = "<html><body><p align=\"center\">centered??</p></body></html>";
            RadFlowDocument document = provider.Import(import);
Completed
Last Updated: 31 May 2016 13:40 by ADMIN
Workaround:

private static void WorkaroundFieldsIssue(RadFlowDocument flowdocument)
{
    foreach (FieldCharacter fieldCharacter in flowdocument.EnumerateChildrenOfType<FieldCharacter>().ToList())
    {
        // only for start
        if (fieldCharacter.FieldCharacterType == FieldCharacterType.Start)
        {
            if (fieldCharacter.FieldInfo.Separator != null && fieldCharacter.FieldInfo.Separator.Parent == null)
            {
                Paragraph parent = fieldCharacter.FieldInfo.End.Paragraph;
                int index = parent.Inlines.IndexOf(fieldCharacter.FieldInfo.End);

                fieldCharacter.FieldInfo.End.Paragraph.Inlines.Insert(index, fieldCharacter.FieldInfo.Separator);
            }
        }
    }
}
Unplanned
Last Updated: 16 Aug 2017 13:59 by ADMIN
ADMIN
Created by: Deyan
Comments: 0
Category: WordsProcessing
Type: Feature Request
3
Implement evaluation of = (Formula) fields (https://support.office.com/en-us/article/Field-codes-Formula-field-32d5c9de-3516-4ec3-80ed-d1fc2b5bc21d?ui=en-US&rs=en-US&ad=US ). This will allow export to PDF and HTML.
Unplanned
Last Updated: 27 Jan 2017 07:25 by ADMIN
Style properties defined in an element style selector are evaluated with higher priority over properties in a CSS class when importing from HTML.

For example if we have the following CSS style:

.sectionheading {
border: 10px solid red;
        }
td {
border: 10px solid black;
        }
and the class (.sectionheading) is applied on a table cell:

<td class="sectionheading">...</td>

The result in WordsProcessing after import of such HTML will be that the table cell has 10px black border. In MS Word and in the browsers (Chrome, Firefox...) the result will be that the cell has 10px red border.
Unplanned
Last Updated: 22 Dec 2016 13:03 by ADMIN
If the Table's TableCellSpacing property is not divided by 2 when the document is exported to Docx or Rtf, this leads to incorrect rendering after the exported document is opened with another editor (RadRichTextBox, MS Word).

Workaround: Divide by two the Table's table cell spacing property value before export to Docx, RTF formats:
foreach (Table table in document.EnumerateChildrenOfType<Table>())
{
    table.TableCellSpacing /= 2;   
}