We're sorry Aspose doesn't work properply without JavaScript enabled.

Free Support Forum - aspose.com

Conflict grouped "shape" objects and DMLRenderingMode

Hello,



When converting a docx to pdf with grouped shapes and a rotated textbox,
the result is distorted.

While the rotation of textboxes has been fixed in WORDSNET-11898 (seen on
Rotated text box is not rotated when saved to PDF). The rendering of the groupobjects doesn’t seem to be correctly anymore.
However, when using DmlRenderingMode.FALLBACK, the grouped objects are rendered correctly, but without the correct rotating textboxes.

Would you be kind to look at this issue?

Code :

//correct rendering shapes, no correct rotating
Document doc = new Document(“grouped_rotated.docx”);
PdfSaveOptions saveOptions = new PdfSaveOptions();
saveOptions.setDmlRenderingMode(DmlRenderingMode.FALLBACK);
doc.save(“DIR_TO_grouped_result_fallback.pdf”, saveOptions);


//no correct rendering shapes, correct rotating
Document doc = new Document(“grouped_rotated.docx”);
PdfSaveOptions saveOptions = new PdfSaveOptions();
doc.save(“DIR_TO_grouped_result_nofallback.pdf”, saveOptions);


Source file: grouped_rotated.docx
Distorted file with correct rotation : grouped_result_nofallback.pdf
fallback file with incorrect rotatition : grouped_result_fallback.pdf

Using :
aspose.words version 16.1.0
JDK1.7

Thank you for your time
Hi there,

Thanks for your inquiry. We have tested the scenario and have managed to reproduce the following issues at our side. For the sake of correction, we have logged these problems in our issue tracking system as follow:

WORDSNET-13157 : GroupShape is rendered as black in output Pdf
WORDSNET-13158 : Rotated text box (inside GroupShape) are not rotated when saved to PDF

You will be notified via this forum thread once these issues are resolved. We apologize for your inconvenience.

Hello,


I forgot to mention, that this issue has been occurred and fixed when converting to XPS:

Problem rendering grouped Shapes?
Hi there,

Thanks for your inquiry. The issue reported in shared forum thread is different from the issue which you reported in this forum thread. Please check the attached images for detail of issues reported by you in this forum thread. We will update you via this forum thread once these issues are resolved.

Thanks for your patience and understanding.

Hi there

Thanks for your patience. It is to inform you that our product team has completed the work on this issue (WORDSNET-13158) and has come to a conclusion that this issue and the undesired behavior you're observing is actually not a bug in Aspose.Words. So, we have closed this issue as 'Not a Bug'. We are quoting developer's comments here for your reference.

If you unzip «grouped_rotated.docx» document and copy "w:pict" elemen from "mc:Fallback" to "w:r" and then remove "mc:AlternateContent" from this run. Then please try to zip it again, you will see that fallback implementation of this shape looks different then original Dml. So when you set DmlRenderingMode.Fallback you will get the same incorrect result. But with DmlRenderingMode.DrawingML the output looks exactly as original shape.

Please check the attached modified document and compare document.xml from "13158 from AW fallback.docx" and "grouped_rotated.docx" to check DmlRenderingMode.DrawingML (default mode) behavior.

Hello,


Thank you for your feedback about issue WORDSNET-13158.
It was very usefull information.

Just to be clear: the other issue (WORDSNET-13157) is still in progress, I assume.

Friendly regards!
Hi there

Thanks for your inquiry. We have asked from our product team about the ETA of WORDSNET-13158. As soon as any information is shared by them, we will be more than happy to share that with you.

Thank you for your patience and understanding.

The issues you have found earlier (filed as WORDSNET-13158) have been fixed in this .NET update and this Java update.


This message was posted using Notification2Forum from Downloads module by aspose.notifier.

The issues you have found earlier (filed as WORDSNET-13158) have been fixed in this .NET update and this Java update.


This message was posted using Notification2Forum from Downloads module by aspose.notifier.
(1)