Image problems on linux mono

leftofcentre · February 9, 2015, 7:37am

Hi If you look at the attached files you will see the images does not convert correctly under linux and mono, it is ok on windows.

Any suggestions?

awais.hafeez · February 10, 2015, 5:04am

Hi,

Thanks for your inquiry. We tested the scenario over linux/mono environment and have managed to reproduce the same problem on our end. For the sake of correction, we have logged this problem in our issue tracking system as WORDSNET-11436. Our development team will further look into the details of this problem and we will keep you updated on the status of correction. We apologize for your inconvenience.

Best regards,

leftofcentre · March 10, 2015, 11:28am

Just checking to see when you think you might have a fix for this problem?

Thanks

Brian

awais.hafeez · March 12, 2015, 1:14am

Hi Brian,

Thanks for your inquiry. Unfortunately, your issue is not resolved yet. We have asked the ETA of this issue from our development team and will update you as soon as any estimates are available. We apologize for your inconvenience.

Best regards,

leftofcentre · March 16, 2015, 6:55am

Hi did you get an ETA yet?

Thanks

Brian

awais.hafeez · March 17, 2015, 6:41am

Hi Brian,

Thanks for your inquiry, Unfortunately, your issue is not resolved yet. Our product team is currently doing analysis of this issue to determine the exact root cause of this problem. Once the analysis of this issue is completed, we will then be able to share the ETA. We apologize for your inconvenience.

Best regards,

leftofcentre · March 19, 2015, 9:34am

This Bug is causing us serious problems is there anyway to get this fixed faster? Can we pay to get it prioritised?

awais.hafeez · March 20, 2015, 2:29am

Hi,

If this issue is important to you, and for the fast resolution of this issue, please have a look at enhanced support options - e.g. purchasing Priority Support will allow you to post your issues in our Priority Support forum and raise the priority of this issue directly with our development teams, if possible, we will then aim to get a resolution to your issue as soon as we can. Many Priority Support customers find that this leads to their issue being fixed in the next release of the software.

If you would like to take advantage of Enhanced Support then please request a quote in our purchase forum -https://forum.aspose.com/c/purchase/6

Best regards,

leftofcentre · April 7, 2015, 8:19am

Is there any update on when this bug will be fixed?

awais.hafeez · April 8, 2015, 12:58am

Hi,

Thanks for your inquiry, Unfortunately, your issue is not resolved yet. And there is no further news about this issue. Also, there is no reliable ETA available at the moment. We will inform you as soon as this issue is resolved or any estimates are available. We apologize for any inconvenience.

Best regards,

awais.hafeez · April 10, 2015, 12:42am

Hi,

Regarding WORDSNET-11436, our product team has completed the work on your issue and has come to a conclusion that this issue and the undesired behaviour you’re observing is actually not a bug in Aspose.Words. So, we have closed this issue as ‘Not a Bug’.

This looks more like a bug in Mono. It is quite difficult (or maybe even impossible) to modify our framework to fix that error in Mono, so we are not going to do it. But we have one workaround to suggest. If you save picture from this document as PNG (for example, from Word - Right click on the picture -> “Save As Picture”), remove old picture and insert the new one, you’ll obtain the document that can be proceeded in Mono without that error.

Best regards,

leftofcentre · June 3, 2015, 6:03am

Is there any ETA on fixing this bug? It has been over 4 months since it was first reported.

Thanks

awais.hafeez · June 3, 2015, 11:59pm

Hi,

Thanks for your inquiry. We had closed this issue sometime ago. It was ‘not a bug’ in Aspose.Words API. I am copying my previous reply here for your reference:

Regarding WORDSNET-11436, our product team has completed the work on your issue and has come to a conclusion that this issue and the undesired behaviour you’re observing is actually not a bug in Aspose.Words. So, we have closed this issue as ‘Not a Bug’.

This looks more like a bug in Mono. It is quite difficult (or maybe even impossible) to modify our framework to fix that error in Mono, so we are not going to do it. But we have one workaround to suggest. If you save picture from this document as PNG (for example, from Word - Right click on the picture -> “Save As Picture”), remove old picture and insert the new one, you’ll obtain the document that can be proceeded in Mono without that error.

Best regards,

leftofcentre · July 29, 2015, 9:28am

We are trying to get a work around for this bug. Can we ask what methods does aspose use in .net to generate images? Do you use any 3rd party code/libraries when generating images? We are trying to recreate that problem for Mono 4 framework in order to report it to Mono support.

Currently aspose.words is not very usable on mono because of the image problem. Fixing this bug will open up more sales for you on osx and linux.

awais.hafeez · July 30, 2015, 3:30am

Hi,

We are in coordination with product team to get answer pertaining to your queries. Soon you will be updated with the required information.

Best regards,

awais.hafeez · July 31, 2015, 12:26am

Hi,

We are not using any third party libraries for generating images. Now, we use only GDI+ for these purposes. As we know in Windows Mono uses GDI+ library that is included with the operating system while in UNIX it provides its own implementation of this API in the “libgdiplus.so” shared library. We suspect this problem might be caused by errors in that library. Hope, this helps.

Best regards,