Different Non Visual Properties for images (nvPicPr) in the same document


#1

Hi,

When creating the same document with a template including images using Aspose words two or more times, the property nvPicPr with different id is generated which leads to having unwanted changes in the generated documents.

For example, we create the same document twice and as you see in the following property pic:nvPicPr with different ids was generated.

First time:

<pic:nvPicPr>
   <pic:cNvPr id="1201590499" name="default-space-logo-256.png"/>
   <pic:cNvPicPr/>
</pic:nvPicPr>

Second time:

<pic:nvPicPr>
   <pic:cNvPr id="2095232079" name="default-space-logo-256.png"/>
   <pic:cNvPicPr/>
</pic:nvPicPr>

Is this an issue in Aspose?

Regards,
Behrouz


#2

@behrouz,

To ensure a timely and accurate response, please ZIP and attach the following resources here for testing:

  • Your simplified input Word document
  • Aspose.Words 19.8 generated output documents showing the correct/undesired behaviors
  • Please also provide a comparison screenshot highlighting the problematic areas in Aspose.Words generated DOCX file and attach it here for our reference. Please point out the exact problematic places for this issue
  • Please also create a simplified standalone console application (source code without compilation errors) that helps us to reproduce your current problem on our end and attach it here for testing. Please do not include Aspose.Words DLL files in it to reduce the file size.

As soon as you get these pieces of information ready, we will start investigation into your issue and provide you more information. Thanks for your cooperation.


#3

@awais.hafeez

I attach an application here demonstrating the issue.
If you compare the outputs using compare feature in MS Word, it shows that images are different while we are generating the same document twice using the same code.

image-diff.zip (160.2 KB)

regards,


#4

@behrouz,

For the sake of any correction, we have logged this problem in our issue tracking system. The ID of this issue is WORDSNET-19042. 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.