Thanks for your help so far.
We have a particular issue. If we create a .doc or docx file that includes references to inserted images that are rotating banner images in .gif format.
For example. http://www.sdia.org.au/ has some banners that rotate.

Copy and paste the banner's URL into a word document, one of these images. - when we do a mail merge in word and send, the images are preserved as rotating .gif files. 

When we send via a aspose conversion, the images are converted into static .gif files showing only the first image in the rotation.

Is there anything we can do to preserve the animation of .gif files?

Hi

Thanks for your inquiry. I managed to reproduce this issue on my side. I will consult with our developers and provide you more information.

Best regards.

Hi

Thanks for your inquiry. I managed to reproduce this issue on my side. I will consult with our developers and provide you more information.

Best regards.

Hi

I created new issue #5917 in our defect database. The problem occurs because GIFs are stored in Aspose Document model as PNG so animation is lost.

Best regards.

Any indication on a fix time or even if it will be fixed?

Any way as an enterprise client we can push this one through... it is kind of an important one for us?

oh.. and thanks for the great help this far!

Hi

Thanks for your inquiry. Currently I can’t provide you any estimate. But I can tell you that we can’t fix this shortly. We must to figure out how GIFs are stored in Word document and do the same in Aspose.Words. This is not so easy to achieve as it sounds.

Best regards.

I have another document that is an easy conversion for word but is giving us only half the header for aspose. Would you mind taking a look and either letting us know why it fails so much or perhaps it is something you can address in a fix?

Additionally is there any news on that png to motion gif thing from the past posts?

Hi

Thanks for your inquiry. Your document contains STD tags (Content Controls). These controls are not supported yet. So this content is ignored. This is issue #4295 in our defect database.

Unfortunately issue #5917 is not resolved yet.

Best regards.