Approved
Last Updated: 14 Oct 2019 12:35 by ADMIN

When applying a table or table cell border with no thickness specified, the border is exported with a default thickness value of zero. However, by specification, the default value should be 2.

Workaround: Create a border by specifying the thickness value. For example:

table.Borders = new TableBorders(new Border(thickness, BorderStyle.Single, new ThemableColor(Colors.Black)));

Approved
Last Updated: 10 Oct 2019 14:43 by ADMIN
When a heading element has a CSS class applied to it, the heading styling applied to it is lost and overridden by the CSS style.
Approved
Last Updated: 09 Oct 2019 10:29 by ADMIN
ADMIN
Created by: Tanya
Comments: 5
Category: WordsProcessing
Type: Feature Request
29
The API should allow you to perform a text-based search and return the parent element(s) of the result(s) or directly the found element(s).
Approved
Last Updated: 02 Oct 2019 15:44 by ADMIN
When merging two documents each of which has header/footer with InsertDocument, the headers/footers are misplaced in the result document.
Approved
Last Updated: 02 Oct 2019 13:25 by ADMIN

In WordsProcessing on import only the lower case CSS attributes are correctly imported. Upper case and mixed case are ignored and the default values are used.

Completed
Last Updated: 30 Sep 2019 10:31 by ADMIN
Release 2019.3.930 (09/30/2019)
The exception is caused by the charts import which is not implemented for WordsProcessing but the processing tries to import the charts part and process it.
Approved
Last Updated: 27 Sep 2019 19:11 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: 11 Sep 2019 09:02 by ADMIN
Created by: Susan
Comments: 0
Category: WordsProcessing
Type: Feature Request
1
An index lists the terms and topics that are discussed in a document, along with the pages that they appear on. 
Completed
Last Updated: 11 Sep 2019 06:17 by ADMIN
Release R3 2019

The construct <link rel="stylesheet" href="main.min.css" /> doesn't raise the HtmlImportSettings.LoadFromUri event on import, as we currently require type="text\css" to be specified explicitly.

According to mdn:
The common use of this attribute is to define the type of stylesheet being referenced (such as text/css), but given that CSS is the only stylesheet language used on the web, not only is it possible to omit the type attribute, but is actually now recommended practice. 


Think of improving the message of the exception we throw if no data is loaded.

Workaround: set type explicitly:
<link rel="stylesheet" type="text/csshref="main.min.css" />

Approved
Last Updated: 09 Sep 2019 14:28 by ADMIN

HtmlFormatProvider does not maintain all the whitespaces on import even though {style="white-space: pre;"} was set.

Approved
Last Updated: 06 Sep 2019 10:13 by ADMIN
ADMIN
Created by: Deyan
Comments: 7
Category: WordsProcessing
Type: Feature Request
23
This feature includes: table of figure, table of tables etc.

TOC field contains PageRef fields inside it. To update it, we will need pagination (layout) support and PageRef fields implementation. Also TOC update can be influenced by TC fields presence in the document.

Implement export to PDF.
Approved
Last Updated: 02 Sep 2019 08:44 by ADMIN
The HtmlFormatProvider currently doesn't support borders for p elements.
Approved
Last Updated: 28 Aug 2019 17:46 by ADMIN
A paragraph containing multiple Hyperlinks inside Fields with missing End FieldCharacter, leads to OutOfMemoryException: 'Exception of type 'System.OutOfMemoryException' when exporting to PDF.

Workaround: Iterate all FieldCharacter instances and move any End FieldCharacter instance to paragraphs with Start FieldCharacters. See the attached project.
 
Approved
Last Updated: 27 Aug 2019 07:55 by ADMIN
The attached sample project below demonstrates a possible workaround for PAGE and NUMPAGES fields when exporting to PDF. The demo shows how to generate document from scratch containing PAGE and NUMPAGES fields and export it to PDF.
Approved
Last Updated: 26 Aug 2019 10:08 by ADMIN
Created by: Nigel
Comments: 0
Category: WordsProcessing
Type: Feature Request
0

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

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

Approved
Last Updated: 16 Aug 2019 06:17 by ADMIN
ADMIN
Created by: Deyan
Comments: 6
Category: WordsProcessing
Type: Feature Request
22
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 )
Approved
Last Updated: 15 Aug 2019 08:27 by ADMIN
Currently some properties are supported only in their shorthand forms, and others - only in their longhand forms:
- 'background' shorthand is not supported.
- 'margin' shorthand is not supported.
- 'border' shorthand is supported, but 'border-bottom-color', 'border-bottom-style', 'border-bottom-width', 'border-left-color', 'border-left-style', 'border-left-width', 'border-right-color', 'border-right-style', 'border-right-width', 'border-style', 'border-top-color', 'border-top-style', 'border-top-width', 'border-width' are not supported.
Approved
Last Updated: 12 Aug 2019 12:09 by ADMIN
Created by: Naveen
Comments: 0
Category: WordsProcessing
Type: Feature Request
2
Provide support for Track Changes.
Approved
Last Updated: 09 Aug 2019 13:35 by ADMIN
Such tags are not supported in RtfFormatProvider and while skipping them, there might be fields that are not properly imported. This can lead to issues while exporting the document. If the document is re-saved using MS Word, the HTML-related tags are removed and the content can be properly imported with WordsProcessing.
Approved
Last Updated: 08 Aug 2019 10:21 by ADMIN
Created by: Naveen
Comments: 0
Category: WordsProcessing
Type: Feature Request
2
Create a feature that allows the RadWordsProcessing to split RadFlowDocument.

Workaround: DocumentElementImporter can be used to prepare a document element from the source document for import into the target document

private static void SplitDocument(RadFlowDocument sourceDocument, RadFlowDocument targetDocument)
{
    DocumentElementImporter importer = new DocumentElementImporter(targetDocument, sourceDocument, ConflictingStylesResolutionMode.UseTargetStyle);
    Section section = sourceDocument.EnumerateChildrenOfType<Section>().First();
    Section importedSection = importer.Import(section);
    targetDocument.Sections.Add(importedSection);
 
    sourceDocument.Sections.Remove(section);
}
1 2 3 4 5 6