I’m using Aspose.Words 6.6.0.0. I have an Input.docx file containing a table with a header row and three data rows. When I save the document as a Pdf, each data row is missing the blank/spacing line I have at the end of each row.
I’ve attached a zip file of a C# project that demonstrates this issue. The zip file’s Bin\Debug folder contains the Input.docx file and the generated Output.pdf file. Open them both side by side and visually compare them to see what I mean. The table in the PDF has rows that aren’t the correct height because there is no blank line between the text in each row.
Hi
Thanks for your inquiry. I managed to reproduce the problem on my side. You will be notified as soon as it is resolved.
It seems the problem occurs because there are Content Controls in this table. Currently, Aspose.Words does not fully support Content Controls.
Best regards.
Thanks. This is a relatively minor rendering issue, and I can work around it by putting a single space character on the “blank” line. Then it renders the same in Word and in the Aspose-generated PDF.
My overall solution is very dependent on content controls though. I’m doing a one-way push of data into Word content controls using Microsoft’s Open XML Format SDK. Then I use Aspose.Words to convert the output document into a PDF. So far Aspose.Words has handled all the content controls fine. I’m using text, date, and image content controls for simple values, and I’m only using rich text controls to hold embedded tables. I’m pushing values directly into the content sections of the controls. I’m not using custom XML properties and/or XPath queries with the controls.
Is there any documentation on exactly what features of content controls that Aspose.Words does and does not support?
Hi
Thanks for your inquiry. Currently, only content of Structured Document Tags (Content Controls) is preserved. Unfortunately, there is no way to work with SDT controls using Aspose.Words. I will notify you as soon as this feature is fully supported. But I cannot give you any reliable estimate at the moment. Hopefully, this feature will be supported before end of this year or at the beginning of the next year.
Best regards.
The issues you have found earlier (filed as 4295) have been fixed in this update.
This message was posted using Notification2Forum from Downloads module by aspose.notifier.
(81)
The issues you have found earlier (filed as WORDSNET-2696) have been fixed in this .NET update and this Java update.
This message was posted using Notification2Forum from Downloads module by aspose.notifier.