We tried to fix it by setting the flag for embedding truetype fonts to false, but that didn’t help:
PdfOptions pdfOptions = new PdfOptions();
pdfOptions.setEmbedTrueTypeFontsForASCII(false);
pdfOptions.setEmbedTrueTypeFontsForAsciiChars(false);
pptxPresentation.save(out, SaveFormat.PDF, pdfOptions);
The problem occured on a Linux platform: SUSE Linux Enterprise Server 11 (x86_64) VERSION = 11,
PATCHLEVEL = 1, but not on Windows 7 (probably because the required font is installed there)
Question: Should the embed flag have fixed the problem and can you help me analyze why id didn’t ?
I like to suggest you to please try using Aspose.Slides for Java 3.0.0 on your end. If there is still an issue then please share the sample presentation with us along with platform information where you are using Aspose.Slides for Java.
My code doesn't run with aspose.slides-3.0.0-jdk14 because of:
java.lang.UnsupportedOperationException: Culture "English" is a neutral culture. It can not be used in formatting and parsing and therefore cannot be set as the thread's current culture.
Is this the same issue reported by you in other forum thread as shared here or is a separate issue. If it involves separate presentation then please share the sample presentation as well. I am also assuming that you are using JDK 1.5 on your end.
Thanks for clarification. In this thread you have mentioned that you have been able to reproduce the issue in SUSE Linux Enterprise Server 11. However, in this thread that you have mentioned are the same the environment shared has been Websphere v6.1 JRE (J2SE 1.5). Please confirm that you have been able to reproduce the issue in both environments using JDK 1.5 with Aspose.Slides for Java 3.0.0.
I have also linked this thread with issue SLIDESJAVA-33580 as in other forum thread shared by you.
The issues 423301 and 423276 are related. They occur within the same application that runs on a Websphere 6.1 application server on a SUSE Linux Enterprise Server 11 operating system. So these are not two different environments but one and the same. You're right to link these issues.
Thank you very much for the clarification. I have updated the issue status accordingly and once updates will be shared by our development team I will share them with you.
I have discussed the issue status with our development team and they have scheduled it for investigation during week 46 (next week) of 2012. I will be able to share the further information by next week end once information will be shared by our development team for the status of the issue. I will really appreciate your patience for this.