PDF files created by e-Synergy cannot be converted

Aspose.PDF Product Family
1

My product uses Aspose.Total for .Net to display files in a web based viewer. For that purpose, the files are converted to png. That doesn’t work with the attached PDF file, created by the financial software e-Synergy:


Code to reproduce the problem is as follows:

string sPdf = “Fails.pdf”;
using (Aspose.Pdf.Document pdf = new Aspose.Pdf.Document(sPdf))
{
Aspose.Pdf.Page pg = pdf.Pages[1];
Aspose.Pdf.Devices.BmpDevice bmpDevice = new Aspose.Pdf.Devices.BmpDevice();
MemoryStream ms = new MemoryStream();
bmpDevice.Resolution.X = 300;
bmpDevice.Resolution.Y = 300;
bmpDevice.Process(pg, ms);
Bitmap bmp = new Bitmap(ms);
bmp.Save(sPdf + “.png”, System.Drawing.Imaging.ImageFormat.Png);
}


The cause is probably the image format used by e-Synergy. All PDF files of the customer having this problem are produced by this software and cannot be converted.

Best regards,

Berend




2

Hi Berend,

Sorry for the inconvenience faced. I've managed to reproduce the reported issue on my side and logged the issue in our bug tracking system for further investigation and resolution, the issue id is PDFNEWNET-35485. I've also linked your request to this issue and you will be notified via this thread as soon as it is resolved.

Please feel free to contact us for any further assistance.

<span style=“font-size:10.0pt;line-height:115%;font-family:“Arial”,“sans-serif”;
mso-fareast-font-family:Calibri;mso-ansi-language:EN-US;mso-fareast-language:
EN-US;mso-bidi-language:AR-SA”>Best Regards,

3

Hi Berend,


The development team is working on resolving the issue reported earlier however as a workaround, you may consider using Viewer application of our sister company named GroupDocs to view/display the PDF files directly in your web application.

4

Hi Berend,


Thanks for your patience.

<span style=“font-size:10.0pt;font-family:“Arial”,“sans-serif””>I
am pleased to share that the issue reported earlier has been resolved in latest
release version of Aspose.Pdf for .NET 8.3.0. Please try using the latest
release version and in case the problem still persists or you have any further
query, please feel free to contact.<o:p></o:p>

For your reference, I have also attached the resultant PDF which I have generated.