Hi Team,
Found an issue with converting a DOCX with smart shapes and smart shapes with grouping, Causes separate one after another with smart shapes to have incorrect and overlapping rendering.
Ive attached the expected.png output with exporting/saving the document as PDF from word directly and the actual.png output using aspose to perform the conversion.
Code used:
var fileStream = File.OpenRead(path)
var document = new WordsDocument(fileStream, new LoadOptions {
LoadFormat = loadFormat
});
document.SavePdf();
public class WordsDocument : IAsposeEditableDocument {
// This must be wrapped in order to mock it
private readonly Document _document;
public WordsDocument() {
if (WordsLicense == null) {
WordsLicense = new License();
WordsLicense.SetLicense("Aspose.Total.lic");
}
}
public WordsDocument(Stream fileStream, LoadOptions options) : this() {
_document = new Document(fileStream, options);
}
private static License WordsLicense { get; set; }
public virtual Stream SavePdf() {
var outputStream = new MemoryStream();
_document.Save(outputStream, SaveFormat.Pdf);
return outputStream;
}
}
expected.png (158.3 KB)
actual.png (161.3 KB)
@lancomdevteam,
Have you tried the latest (20.9) version of Aspose.Words for .NET on your end? In case the problem still remains, please ZIP and upload your input DOCX Word document and Aspose.Words 20.9 generated output PDF file showing the undesired behavior here for testing. We will then investigate the issue on our end and provide you more information.
Hi Team,
I have gone head and tested current version were using and updated package 20.9 and still have same issue.
I have attached output of both versions with expected output, resulting output from aspose as well as the original source word document.
Zip files are suffixed with the version of aspose used.
aspose_words_20.9.zip (226.1 KB)
aspose_words_20.6.zip (520.4 KB)
@lancomdevteam,
We tested the scenario and have managed to reproduce the same problem on our end. The Group Shapes comprising of Text-boxes, Arrow Shapes etc on the last two pages of Word DOCX document are currently not rendering correctly in Aspose.Words’ generated PDF. For the sake of correction, we have logged this problem in our issue tracking system. The ID of this issue is WORDSNET-21106. We will further look into the details of this problem and will keep you updated on the status of correction. We apologize for your inconvenience.
Hi Team,
Can I get a status updated on progress for this issue.
Thanks.
Kind Regards,
lancomdevteam
@lancomdevteam,
We have completed the analysis of this issue; but I am afraid, the implementation of the fix of this issue has been postponed till a later date. There are no estimates available at the moment. We will inform you here as soon as this issue will get resolved in future. We apologize for your inconvenience.
Hi team,
What would be required for us to expedite this issue? This is urgent for us as a large subset of our processed documents contain Smart Shapes.
This has been raised multiple times by our end users since the case was raised, and we would like to set expectations for our customers by providing a resolution timeline.
Let me know if there’s any additional information I can supply in the mean time.
Kind regards,
Lancomdevteam
@lancomdevteam
I am afraid, WORDSNET-21106 is still postponed. If this issue is important to you, then please have a look at the paid support options - e.g. purchasing ‘Paid Support’ will allow you to post your issues in our Paid Support Helpdesk and raise the priority of this issue. Many ‘Paid Support’ customers find that this leads to their issues being fixed in the next release of the software.
If you would like to take advantage of the ‘Paid Support’, then please contact our sales team via purchase forum - Aspose.Purchase - Free Support Forum - aspose.com.
Hi Team,
Any status updates on this issue?
Kind Regards,
lancomdevteam
@lancomdevteam,
Unfortunately, WORDSNET-21106 is not resolved yet and there is no further news about it. We will inform you via this thread as soon as this issue will get resolved in future. We apologize for your inconvenience.
Hi Team,
Any updates on the status of this issue or a potential ETA?
Cheers,
lancomdevteam
@lancomdevteam,
Unfortunately, the issue WORDSNET-21106 is still postponed and there is no ETA available at the moment. We apologize for any inconvenience.
Hi team,
We raised this request in September 202, this request has been open for 400+ days. When can we expect a indicative timeline of when this can be resolved?
If an indicative timeline cannot be provided, what options are available to escalate this request?
Kind regards,
lancomdevteam
@lancomdevteam Unfortunately, there is no estimate yet regarding this issue, the issue is still postponed. We apologize for your inconvenience. You can try escalating this issue through paid support.
Hi team,
Any updates on the status of this issue or a potential ETA?
Cheers,
@lancomdevteam Unfortunately, there is no news regarding the issue yet. The issue is still postponed and is not yet scheduled for development.
Hi Team,
Any updates on the status of this issue or a potential ETA?
Cheers,
lancomdevteam
@lancomdevteam Unfortunately, the issue is still postponed and it not yet scheduled for development. The issue occurs because some elements of MS Word 2013 logic when positioning a wrapped shape not fitting onto the page are not imitated by Aspose.Words. This is a quite complex and very specific case; your request is the only request about this issue. That is why it was decided to postponed implementation this logic for now.
Hi Team,
Any updates on the status of this issue or a potential ETA?
Cheers,
lancomdevteam
@lancomdevteam Unfortunately, there is no news regarding this issue. It is still postponed and is not yet scheduled for development.