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

Workaround: 

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:

after import/export results in

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.

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

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

Workaround: Manually set the ID

The floating image is not exported when it is at the end of the document and does not fit an the same page.

The tab stop line wrongly inherits its thickness from the previous table cell`s border.

There is border over the whole table when exporting to HTML.

Table cell width are not correctly resolved on export.

Table cell width are not correctly resolved on export.

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.

That behavior makes the document invalid and it cannot be later merged successfully as it remains with an empty section.

Currently, when exporting documents containing RTL (right-to-left) text, the flow direction is not respected and it is set to LTR.

When the col HTML elements don't have width attribute set, an ArgumentNullException is thrown during parsing the document.

Implement options for setting hyperlink on an image and preserving it in import/export.

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.

Text is not replaced when the document contains empty fields

The 'border' attribute of Html <table /> is imported wrong. When set to 0, a 1px border is rendered. 

The exception is thrown during the exporting of the document with the following stack trace:

  Telerik.Windows.Documents.Flow.FormatProviders.Docx.Model.Elements.Styles.ShadingElement.FillAttributes(IPropertiesWithShading properties)
   at Telerik.Windows.Documents.Flow.FormatProviders.Docx.Model.Elements.Document.RunPropertiesElement.OnBeforeWrite(IDocxExportContext context)
   at Telerik.Windows.Documents.FormatProviders.OpenXml.Model.Elements.OpenXmlElementBase`3.OnBeforeWrite(IOpenXmlExportContext context)
   at Telerik.Windows.Documents.FormatProviders.OpenXml.Model.Elements.OpenXmlElementBase.Write(IOpenXmlWriter writer, IOpenXmlExportContext context)
   at Telerik.Windows.Documents.FormatProviders.OpenXml.Model.Elements.OpenXmlElementBase.Write(IOpenXmlWriter writer, IOpenXmlExportContext context)
   at Telerik.Windows.Documents.FormatProviders.OpenXml.Model.Elements.OpenXmlElementBase.Write(IOpenXmlWriter writer, IOpenXmlExportContext context)
   at Telerik.Windows.Documents.FormatProviders.OpenXml.Model.Elements.OpenXmlElementBase.Write(IOpenXmlWriter writer, IOpenXmlExportContext context)
   at Telerik.Windows.Documents.FormatProviders.OpenXml.Model.Parts.OpenXmlPartBase.Export(IOpenXmlWriter writer, IOpenXmlExportContext context)
   at Telerik.Windows.Documents.FormatProviders.OpenXml.Model.Parts.OpenXmlPartBase.Export(Stream stream, IOpenXmlExportContext context)
   at Telerik.Windows.Documents.FormatProviders.OpenXml.Export.OpenXmlExporter`2.ExportPart(PartBase part, TContext context)
   at Telerik.Windows.Documents.FormatProviders.OpenXml.Export.OpenXmlExporter`2.Export(Stream output, TContext context, OpenXmlExportSettings settings)
   at Telerik.Windows.Documents.Flow.FormatProviders.Docx.DocxFormatProvider.ExportOverride(RadFlowDocument document, Stream output)
   at Telerik.Windows.Documents.Common.FormatProviders.FormatProviderBase`1.Export(T document, Stream output)

Currently, WordsProcessing evaluates the result of any field to a string. However, there are cases when other document elements need to be added as a result of the field's evaluation. For example, IF fields can be evaluated in a table.