Completed
Last Updated: 08 Feb 2022 15:16 by ADMIN
Release R1 2022 SP1

When a field is formatted using the numberInDash format through the section's PageNumberingSettings, the format is not parsed and the field result is not included in the PDF document.

Workaround: Remove the formatting from the section settings:

foreach (var section in this.document.Sections)
{
    section.PageNumberingSettings.PageNumberFormat = null;
}

Completed
Last Updated: 07 Feb 2022 14:41 by ADMIN
Release R1 2022 SP1
When the content control is the first element of a paragraph inside a table cell and doesn't have content, NullReferenceException is thrown while parsing the document.
Completed
Last Updated: 03 Feb 2022 07:45 by ADMIN
Release R1 2022 SP1
The exception is thrown for documents that contain a repeating section that spans over the whole content of a table cell. Also, the content should contain more than one paragraph.
Completed
Last Updated: 01 Feb 2022 15:05 by ADMIN
Release R1 2022 SP1
Importing docx file throws System.InvalidOperationException "Hierarchical Index is empty" when importing a specific file.
Completed
Last Updated: 01 Feb 2022 14:13 by ADMIN

Importing document with invalid bookmarks throws System.Collections.Generic.KeyNotFoundException. The issue is caused by an invalid bookmark having missing BookmarkRangeStart/bookmarkStart or BookmarkRangeEnd/bookmarkEnd elements.

Unplanned
Last Updated: 27 Jan 2022 15:56 by ADMIN
Internally, the WebClient class is used to load external resources. This class is not supported in Blazor and WordsProcessing should provide a mechanism for loading the resource.
Completed
Last Updated: 20 Jan 2022 08:21 by ADMIN
Release R1 2022
ADMIN
Created by: Deyan
Comments: 2
Category: WordsProcessing
Type: Feature Request
26
In WordsProcessing you could set 

table.Alignment = Telerik.Windows.Documents.Flow.Model.Styles.Alignment.Center;

But when the document is exported to PDF, this is not respected.
Completed
Last Updated: 20 Jan 2022 08:20 by ADMIN
Release R1 2022
ADMIN
Created by: Deyan
Comments: 17
Category: WordsProcessing
Type: Feature Request
44
Implement nested mail merge and master-detail scenario.
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.