We have tested the scenario and managed to reproduce the same issue at our side. For the sake of correction, we have logged this problem in our issue tracking system as WORDSNET-22916. You will be notified via this forum thread once this issue is resolved.
While I understand a fix may take some time, would it be possible to pinpoint the exact reason for this behavior and if so, can we do some sort of check in our code to make sure we’re not continuing the conversion?
In our software it’s highly important the converted file (visually) contains the same information as the original document, so any indication something might be wrong would be very useful.
Aspose.Words imports the image into Shape node. The problem occurs because drawing element (image) is direct child of Body node. So, it is not imported correctly into Aspose.Words’ DOM. Once there is any further update available, we will let you know.
Sets consent for sending user data to Google for online advertising purposes.
Sets consent for personalized advertising.
Cookie Notice
To provide you with the best experience, we use cookies for personalization, analytics, and ads. By using our site, you agree to our cookie policy.
More info
Enables storage, such as cookies, related to analytics.
Enables storage, such as cookies, related to advertising.
Sets consent for sending user data to Google for online advertising purposes.
Sets consent for personalized advertising.
Cookie Notice
To provide you with the best experience, we use cookies for personalization, analytics, and ads. By using our site, you agree to our cookie policy.
More info
Enables storage, such as cookies, related to analytics.
Enables storage, such as cookies, related to advertising.
Sets consent for sending user data to Google for online advertising purposes.