When exporting a ppt to pdf, the line border around an image exports with differing thicknesses around the border. So the top and bottom border are too thin compared with the sides. This worked ok in 2.9.2 but the latest 3.1.1 version of aspose.slides broke the image border on export to pdf. I tried this at varying point sizes from .75 to 2.5 and it always exports to pdf at different thicknesses on different sides of the image box. I have attached a sample ppt and exported pdf. I tried printing the ppt to a pdf driver and that worked fine so I believe this is a bug in 3.1.1. Also, it worked fine in 2.9.2.
Hello,
The thickness of lines is the same but it looks like image overlap top and right lines partly. We will investigate it and fix.
Hello,
The issue was fixed. Please try latest 3.1.1.9 version of Aspose.Slides for .NET attached in this thread or use direct download link.
With 3.1.1.9 the image overwriting the line border bug is now fixed but some images now export with messed up colors. On the attached sample the orange & blue image bar gets totally scrambled colors when exported to pdf. I tried this on both Vista and XP at various color resolutions and it gives the same result.
This issue is under investigation.
I just re-confirmed that the color problem did NOT exist in version 2.9.2.0 but does have the problem in the latest 3.1.1.9 release. Have you investigated and determined when you will have a fixed build?
Hello Jeff,
This problem already fixed but it’s temporary not possible to publish new Aspose.Slides for .NET version. Most probably it will be available on weekends.
When you get a chance, please post the link to the release that has the color fix. I don’t see it on the downloads page. Thanks!
Hello,
Sorry but I’m afraid it will be delayed for several days. We updated our pdf rendering and there are large improvements in memory use and speed but we have to fix 2 serious problems before release.
The issues you have found earlier (filed as 10443;10287) have been fixed in this update.
This message was posted using Notification2Forum from Downloads module by aspose.notifier.
I changed the call from SaveToPdf to the new Save as follows and it immediately throws an exception. It is outputting great to PPT but crashes on save to PDF with just the 10-byte header in the PDF file. You can use the same colortest.ppt I uploaded earlier to test.
//pres.SaveToPdf(m_powerPointDest + ".pdf");
pres.Save(m_powerPointDest + ".pdf", Aspose.Slides.Export.SaveFormat.Pdf);
Here is the exception output:
9/28/2009 8:13 AM: Saving Presentation to "colortest.pdf" ...
9/28/2009 8:13 AM: *** Error Writing Presentation file (colortest.pdf):Method 'GetObjectData' in type 'bzs' from assembly 'Aspose.Slides, Version=4.0.0.0, Culture=neutral, PublicKeyToken=716fcc553a201e56' does not have an implementation.
at sz.set_a(Matrix value)
at bd.a(SizeF a)
at bd..ctor(Int32 a, Int32 a, Single a, Single a, Boolean a)
at Aspose.Slides.Slide.a(Boolean a)
at ve.a(Presentation a, Stream a, Int32[] a, PdfOptions a)
at Aspose.Slides.Presentation.Save(Stream stream, SaveFormat format, SaveOptions options)
at Aspose.Slides.Presentation.Save(String fname, SaveFormat format)
at TkPpt.TkPpt.Run()
Hello Jeff,
I have updated downloads page with new installer. Please download it and reinstall. It looks like there was obfuscation problem.
With the updated installer the export now works and all of the bugs in this thread are now fixed. Great job!
Embedded fonts no longer get used on the save to PDF. This was working on the 3.9.2 version. You fixed a bug for the font matching but this now broken with 4.0.0. I have attached a sample template that has an Aldine BT font embedded and the settings in Powerpoint are set to embed the entire font. When I save to a new PPT, it does keep the fonts, but when I save to PDF, it changes the font to Times New Roman. It doesn't seem to make a difference if the fonts are installed or not (and it shouldn't since they are embedded in the original ppt file).
NOTE: This is the same font matching bug as originally reported a few months ago. The fonts match as long as they end in bold and/or italic. But this font ended in the word "BT". You fixed this but I suspect when writing your new PDF export engine this bug fix was lost. This whole change of required fixes was due to this bug so I really would like to have this fixed in the latest release. Thanks!
Hello,
I think there is a mistake. Aspose.Slides never could read embedded to a ppt file fonts so font always should be installed in the system. Also we didn’t change fonts processing in the last release. Most of changes were done for images, fill styles and shapes rendering.
If I’m not mistaken we fixed exception (when search for Aldine 401 BT font) in previous versions but anyway, this font was replaced with font by default.
Yes, the fonts must be installed, but it keeps the embedded fonts when writing the new ppt file, but it substitutes Time New Roman for the font when exporting to PDF. If the fonts are installed, shouldn't it use the same font in the exported PDF? Attached are the font files you can install and a sample ppt file that uses this font. After installing the fonts files, run a Save to PDF and you will see it doesn't keep the correct font usage. You are correct that you fixed the exception but the PDF export still has this bug. Will you be fixing this pdf export font problem? Note: If I use a font without the extra word in the font name, it does export to PDF with the correct font.
There is additional hot fix for the correct search and embedding such fonts.
I made sure the “American Garmond BT” font was installed (see my previous attachment) and tried 4.0.0.2 hotfix build and the exported PDF still does not use the correct font but substitutes with Times New Roman. To reproduced the bug with 4.0.0.2, install the four AMRGA*.TTF files and load fontbug3.ppt and Save to PDF. You can also save to PPT. Notice the saved PPT still uses the correct font but the exported PDF file does not. There is no exception crash, but the font bug is still there.
Hello,
We have implemented improved 2 pass font search algorithm. First pass will search font by short name or family name like “AmeriGarmnd BT” or “Aldine401 BT” and the second one search by parts of the full name like “American Garamond BT” or “Aldine 401 BT”. It works now for all fonts installed on my system. Please write if you will have problems with any other fonts.
I ran various tests with the two fonts and a variety of other fonts and they all embedded correctly in the exported PDF as well as the generated PPT with the latest 4.0.0.3 release. Thank you for the fast turnaround and fix for this!