Problem converting a pdf

Hello, we have a problem converting a pdf file into image (see pdf and result image in attachment).
This pdf is created with adobe illustrator but we have this kind of problem only with this file (other files created in the same way are fine converted)
Can you see?

this is the code we use for converting pdf files
Aspose.Pdf.Devices.Resolution ResolutionP = new Aspose.Pdf.Devices.Resolution(120);
Aspose.Pdf.Devices.PngDevice PngDeviceP = new Aspose.Pdf.Devices.PngDevice(ResolutionP);
PngDeviceP.Process(((Aspose.Pdf.Document)m_oDocument).Pages[++_iPageIndex], _oOutputStream);

Hi Valerio,


Thanks for using our API’s.

I am working on replicating the issue in my environment and will keep you updated with my findings.

Hi Valerio,


Thanks for using our API’s.

I have tested the scenario and have managed to reproduce same problem. For the sake of correction, I have logged it as PDFNEWNET-40793 in our issue tracking system. We will further look into the details of this problem and will keep you posted on the status of correction. Please be patient and spare us little time. We are sorry for this inconvenience.

if it can help, the same file was fine converted with previous version of the same library, but we do not know which version has the error introduced

Hi Valerio,


Thanks for sharing the details.

The information has been shared with product team and we will consider it during the resolution of this problem. However if you figure out the version which previously worked, please do let us know as it will help us in identifying the API change when this problem was introduced.

Please be patient and spare us little time.

sorry, this is only a note from our customer, we cannot say it is true. We can only experience that some other files, bigger in file dimension too, created in the same way (adobe illustrator and a lot of layers) have no problem but this file has…
my apologies

Hi,


Thanks for the acknowledgement.

The information has been associated with earlier reported issue and we will consider it during the resolution of issue. In case you have encountered similar issue using other files, or you have any further query, please feel free to contact.

Please be patient and spare us little time.

hi, any news?

Hi Valerio,


Thanks for your inquriy. I am afraid the reported issue is still not resolved as product team is busy in resolving other issues in the queue, reported earlier. We will notify you as soon as we made some significant progress towards issue resolution.

Thanks for your patience and cooperation.

Best Regards,

Hi, again no news about it?
thanks

Hi Valerio,


Thanks for your inquiry. I am afraid the issue is still pending for investigation, as product team is busy in resolving other issues in the queue. However we have raised your issue priority, requested our team to complete the investigation and share an update/ETA as soon as possible. We will notify you as soon as we get a feedback.

Thanks for your patience and cooperation.

Best Regards,

hello, any update about it, so long?

Hi Valerio,


Thanks for your patience.

The product team has started investigating earlier reported issue but I am afraid its not yet resolved. However I have intimated the team to share the possible updates regarding its resolution.As soon as we have some definite updates regarding its resolution, we will let you know. We are sorry for this delay and inconvenience.

please share some news about it! it’s passed a very long time.

Hi Valerio,


Thanks for your patience.

I am afraid the earlier reported issue is not yet resolved. However I have inquired latest updates regarding its resolution from product team and as soon as we have some further updates, we will let you know.

Please be patient and spare us little time. We are sorry for this delay and inconvenience.

sorry but any news about it?
i attach again a sample file (the original file and the resulting of aspose elaboration)

you can get it here (https://test.boolebox.com/app/index.html?obj=3400390030003100300034003500390036003000310036003400340033003700320033003900).

@BooleServer,

Thanks for sharing the updates. I am testing the scenario against latest file and will get back to you soon. We are sorry for this delay and inconvenience.

@BooleServer,

I have tested the scenario and have managed to reproduce the same problem. For the sake of correction, I have logged it as PDFNET-43372 in our issue tracking system. We will further look into the details of this problem and will keep you updated on the status of correction. Please be patient and spare us little time. We are sorry for this inconvenience.

PDFNET-40793 Open since may 2016 (!)
PDFNET-43372 Open since september 2017

can we have some news about theese issues?
thanks

@BooleServer,

Unfortunately, there is no update on this. We have inquired for the latest updates and let you know as soon as the latest update is available to us.

It has just been identified and our product will investigate as per their development schedules. We will let you know once a significant progress has been made in this regard.