Completed
Last Updated: 20 Jan 2022 08:20 by ADMIN
Release R1 2022
Expose a method that deletes the content between two inlines
Completed
Last Updated: 20 Jan 2022 08:19 by ADMIN
Release R1 2022
The vertical alignment of the table cells is not exported to PDF. The values are always exported with top alignment.
Completed
Last Updated: 20 Jan 2022 08:19 by ADMIN
Release R1 2022
Respect the Height property of TableRow when exporting with PdfFormatProvider.
Unplanned
Last Updated: 23 Dec 2021 12:46 by ADMIN

The table is cut off when its width is larger than the default page width.

Workaround: 

var htmlProvider = new HtmlFormatProvider();
var document = htmlProvider.Import(File.ReadAllText(@"..\..\HTMLPage1.html"));

var tables = document.EnumerateChildrenOfType<Table>();
double maxWidth = document.Sections.FirstOrDefault().PageSize.Width;

foreach (var item in tables)
{
    if (item.PreferredWidth.Type == Telerik.Windows.Documents.Flow.Model.Styles.TableWidthUnitType.Fixed)
    {
        maxWidth = Math.Max(maxWidth, (item.PreferredWidth.Value + 100));
    }
}

foreach (var item in document.Sections)
{
    item.PageSize = new System.Windows.Size(maxWidth, item.PageSize.Height);
}

var pdfProvider = new PdfFormatProvider();
File.WriteAllBytes(@"..\..\result.pdf", pdfProvider.Export(document));

Completed
Last Updated: 21 Dec 2021 10:32 by ADMIN
Release R1 2022
The default left and right margins for a table in MS Word are 0.08". However, the DocxFormatProvider uses 0 as a default value and overrides the padding when any of the top, bottom, right, or left is applied. For example:

<w:tblCellMar>
	<w:top w:w="2880" w:type="dxa"/>
	<w:bottom w:w="2880" w:type="dxa"/>
</w:tblCellMar>
after import/export results in
<w:tblCellMar>
	<w:top w:w="2880" w:type="dxa"/>
	<w:left w:w="0" w:type="dxa"/>
	<w:right w:w="0" w:type="dxa"/>
	<w:bottom w:w="2880" w:type="dxa"/>
</w:tblCellMar>

Unplanned
Last Updated: 16 Dec 2021 13:29 by ADMIN
Currently, invoking the InsertStructuredDocumentTag method inserts only the start and end elements for content control. That way, the content control remains empty and one should explicitly add its content so that the control can be seen when the document is visualized. Apply default values for the different types of content controls to make their creation easier.
Duplicated
Last Updated: 07 Dec 2021 11:23 by ADMIN
Created by: Dominik
Comments: 1
Category: WordsProcessing
Type: Bug Report
2

Hello,

 

we are describing a reproducable problem (WordProcessing demo page), where DOCX footnotes are not imported as expected.

 

Current behaviour:

Upon converting a custom DOCX (including footnotes) into a DOCX again, using the WordProcessing demo, the converted document does no longer contain any footnotes.

 

Expected behaviour:

The downloaded DOCX should still contain all footnotes from the uploaded DOCX after converting it.

 

How to reproduce:

  1. Download docx sample file (or create new Word 2016 document -> References -> Add footnote)
  2. Go to demo page https://demos.telerik.com/aspnet-mvc/wordsprocessing 
  3. Select "load custom document"
  4. Upload sample file
  5. Select "Convert and Download"
  6. Open the converted file - the footnotes in the document are gone

 

 

Is there anything that can be done as a workaround until this has been resolved?

 

Thank you in advance.

 

Kind Regards,

Dominik

Unplanned
Last Updated: 03 Dec 2021 06:40 by ADMIN

The content controls ID's must be set automatically when once clones or inserts an SDT.

Workaround: Manually set the ID

SdtRangeStart start = grpContentControls.Where(c => Convert.ToString(c.SdtProperties.Tag) ==  "purchlastname").First();

var properties = new SdtProperties(start.SdtProperties);
properties.ID = 123456;
var currentItem = editor.InsertStructuredDocumentTag(properties);

Completed
Last Updated: 22 Nov 2021 15:35 by ADMIN
Release R1 2022
The floating image is not exported when it is at the end of the document and does not fit an the same page.
Unplanned
Last Updated: 22 Nov 2021 11:33 by ADMIN
Unplanned
Last Updated: 16 Nov 2021 16:11 by ADMIN
There is border over the whole table when exporting to HTML.
Unplanned
Last Updated: 16 Nov 2021 16:10 by ADMIN
Table cell width are not correctly resolved on export.
Unplanned
Last Updated: 16 Nov 2021 16:09 by ADMIN
Table cell width are not correctly resolved on export.
Unplanned
Last Updated: 11 Nov 2021 10:48 by ADMIN
The value of a content control can be resolved from an XML element stored within a Custom XML Data part in the document. Currently, WordsProcessing is unable to import all the data related to the data binding, thus cannot resolve the value of the content control.
Unplanned
Last Updated: 05 Nov 2021 09:18 by ADMIN
That behavior makes the document invalid and it cannot be later merged successfully as it remains with an empty section.
Unplanned
Last Updated: 01 Nov 2021 08:11 by ADMIN
Currently, when exporting documents containing RTL (right-to-left) text, the flow direction is not respected and it is set to LTR.
Completed
Last Updated: 25 Oct 2021 08:27 by ADMIN
Release R3 2021 SP1
When the col HTML elements don't have width attribute set, an ArgumentNullException is thrown during parsing the document.
Completed
Last Updated: 23 Oct 2021 17:16 by Tom
Release R3 2021 SP1
Implement options for setting hyperlink on an image and preserving it in import/export.
Unplanned
Last Updated: 21 Oct 2021 15:24 by ADMIN
ADMIN
Created by: Tanya
Comments: 0
Category: WordsProcessing
Type: Feature Request
1
Currently, text can be replaced with other text, inlines, or blocks. However, the API doesn't provide an option for constructing hyperlinks and getting their inlines. Users can only insert hyperlinks directly through the editor. Expose overload enabling users to replace text with a hyperlink.

Completed
Last Updated: 21 Oct 2021 14:00 by ADMIN
Release R3 2021 SP1
Text is not replaced when the document contains empty fields