Completed
Last Updated: 02 Aug 2021 14:24 by Marc
Release R3 2021
The <col> tag specifies column properties for each column within a <colgroup> element. It is useful for applying styles to entire columns, instead of repeating the styles for each cell, for each row. This functionality is currently not respected while importing with HtmlFormatProvider.
Completed
Last Updated: 02 Aug 2021 08:21 by ADMIN
Release R3 2021
The exception is thrown at Telerik.Windows.Documents.Core.Data.ValueMapper`2.GetToValue(TFrom value) with message 'System.InvalidOperationException: 'Not supported from value: 16''
Completed
Last Updated: 02 Aug 2021 07:09 by ADMIN
Release R3 2021
The exception is thrown at Telerik.Windows.Documents.Core.Data.ValueMapper`2.GetToValue(TFrom value) with message 'Not supported from value: numTab'
Unplanned
Last Updated: 29 Jul 2021 14:24 by ADMIN
Num definition that follows another num definition and both share the same abstractNumId should continue the numbering. In the current version, the numbering is restarted. 
Unplanned
Last Updated: 29 Jul 2021 09:49 by ADMIN
ADMIN
Created by: Deyan
Comments: 12
Category: WordsProcessing
Type: Feature Request
47
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 )
Unplanned
Last Updated: 28 Jul 2021 13:42 by ADMIN
In the current implementation, when the table and its cells don't define specific widths, they are automatically calculated according to the available space. This, however, might sometimes result in breaking whole words. The entirety of words should be preserved if that is possible in the concrete case.
Completed
Last Updated: 13 Jul 2021 14:50 by ADMIN
Release R3 2021

When exporting a document containing a Field that has no Separator set the content after this field is omitted.

According to the OOXML Specification, the fldCharType value separate is optional. 

Unplanned
Last Updated: 02 Jul 2021 06:18 by ADMIN
The line-height of the paragraph should be applied to the spacing before and after as well.
Completed
Last Updated: 01 Jul 2021 14:16 by ADMIN
Release LIB 2021.2.705 (05 Jul 2021)

When the data is set as double or float the Numeric formatting of the MergeField is not respected.

When the following merge field:

MERGEFIELD BAL  \# ###,0.00

is populated with 5.70F or 5.70D the result is 5.7 instead of 5.70.

 

Unplanned
Last Updated: 01 Jul 2021 13:03 by ADMIN
The styles that are declared inside the body selector should be applied to the whole document content if another styling is not specified. However, during the import, HtmlFormatProvider doesn't respect these definitions.
Unplanned
Last Updated: 01 Jul 2021 08:12 by ADMIN
Line-height of the spans is not imported when converting Html to Docx
Unplanned
Last Updated: 28 Jun 2021 05:11 by ADMIN
Converting table with custom borders to PDF does not work
Completed
Last Updated: 24 Jun 2021 10:24 by ADMIN
In the document produced by the mail merge, the date time and numeric formatting applied are not respected and the value is in its default format. 
Unplanned
Last Updated: 14 Jun 2021 11:30 by ADMIN

 Table with specified width in inches is not correctly exported when the size is set in inches (this is  done in the imported HTML) 

Workaround: set the table size in the code and remove the style.

foreach (Table table in document2.EnumerateChildrenOfType<Table>())
{
    table.LayoutType = TableLayoutType.FixedWidth;
    table.PreferredWidth = new TableWidthUnit(TableWidthUnitType.Fixed, 950);
}
Unplanned
Last Updated: 11 Jun 2021 09:29 by ADMIN
Created by: Al
Comments: 0
Category: WordsProcessing
Type: Feature Request
1

Add support for Upper and Lower field switches  More info is available here: Formatting fields with switches

Here are the switches that should be supported:

First Name Upper: {MERGEFIELD FirstName \* Upper}
First Name Lower: {MERGEFIELD FirstName \* Lower}
Unplanned
Last Updated: 11 Jun 2021 09:23 by ADMIN
Created by: Al
Comments: 0
Category: WordsProcessing
Type: Feature Request
1

Add support for all number switches.  More info is available here: Formatting fields with switches

Here are the switches that should be supported:

Amount \# $,0.00: {MERGEFIELD FirstAmount \# $,0.00}
Amount \# $#,###,###: {MERGEFIELD FirstAmount \# $#,###,###}
Amount \*CardText:  {MERGEFIELD \\*CardText}
Amount \*DollarText:  {MERGEFIELD \\*DollarText}
Integer \*alphabetic: {MERGEFIELD \\*alphabetic}
Integer \* ALPHABETIC: {MERGEFIELD FirstInteger \* ALPHABETIC}
Integer \* OrdText: {MERGEFIELD FirstInteger \* OrdText}
Integer \* Ordinal: {MERGEFIELD FirstInteger \* Ordinal}
Integer \* roman: {MERGEFIELD FirstInteger \* roman}
Unplanned
Last Updated: 02 Jun 2021 07:21 by ADMIN

When exporting to PDF a document containing Table merged into a TableCell an extra empty space below the inner table is added:

Unplanned
Last Updated: 01 Jun 2021 08:22 by ADMIN

When we have Document properties set (no Section properties set) and the \sectd control word is missing the Document properties are not respected.

From the RTF Specification: When we have Section properties set the \sectd resets the values to that specified by the Document properties. But when we don't have Section properties set and the \sectd is missing we should inherit the values specified by the Document properties

Unplanned
Last Updated: 28 May 2021 07:23 by ADMIN
Created by: Oksana
Comments: 0
Category: WordsProcessing
Type: Feature Request
2
Provide support for import and export of Fields to HTML format.
Unplanned
Last Updated: 20 May 2021 13:16 by ADMIN
ADMIN
Created by: Deyan
Comments: 17
Category: WordsProcessing
Type: Feature Request
40
Implement nested mail merge and master-detail scenario.
1 2 3 4 5 6