Thanks for your request. During converting document to PDF and XPS Aspose.Words reads font files and creates subsets of fonts, which are used in PDF and XPS. Maybe the problem might occur because some of your fonts cannot be read. If it is possible, could you please archive all your fonts and share the archive somewhere. I will check all your fonts on my side and provide you more information.
Thank you for additional information. I managed to reproduce the problem on my side. Your request has been linked to the appropriate issue. You will be notified as soon as it is resolved. The problem occurs because Aspose.Words cannot read the following fonts properly:
Frutiger-Bold
Frutiger-Black
Frutiger-BlackItalic
Frutiger-Italic
Frutiger-Light
Frutiger-LightItalic
Frutiger-Roman
Frutiger-UltraBlack
Perpetua
Perpetua-Bold
Perpetua-BoldItalic
Perpetua-Italic
As a workaround you can remove these fonts from your PC.
Thanks for your inquiry. During rendering Aspose.Words needs to read all fonts to create map of font name to font file names. Then, when you convert some document to PDF, XPS the appropriate font files are read in order to create font subset, which will be stored in the file.
It seems in your case, there is something wrong with these fonts. It is difficult to say what exactly is wrong at the moment. We will deeply investigate the problem and provide you more information.
This issue has just come up for us on a single client’s Windows 2008 SP1 EE server – so our access and remote cooperation are limited. They are not even sure they want to believe it is likely a corrupt font.
Clearly, you identified the list of bad font files – Do you have a tool that can scan the hundreds of files?
Thank you for additional information. Unfortunately, there is no tool for analyzing all fonts. But we already fixed few similar issues, so, I think your problem will also be resolved in the next version of Aspose.Words, which will be release in a week.
Thank you for additional information. I managed to reproduce the problem on my side. Your request has been linked to the appropriate issue. You will be notified as soon as it is resolved. The problem occurs because Aspose.Words cannot read the following font properly:
MICR____.TTF
As a workaround you can remove this font from your PC.
I have good news for you. The problem with font is already resolved in the current codebase. The fix will be included into the next hotfix, which will be released within few weeks. You will be notified. Also, could you please attach your input and output documents here for testing?
Thank you for additional information. I managed to reproduce the problem with this font on my side. Your request has been linked to the appropriate issue. You will be notified as soon as it is resolved.
Exception still exists in version 9.0.0.0
I have over 1000 clients. I can not control the fonts installed on their systems. If the font is incorrect, it shall be omitted or changed to another.
Best regards,
Krzysztof Radzimski
Administration & Business Consulting
Requested a name string that is not present in the font.
w ㌧.㍜.㍠(㍦ ㍞)
w ㌧.㍸.㎑(String ԋ)
w ㌧.㍸.㎯(String ㎰)
w ㌧.㍸.get_୫()
w ㌧.㍸.㎖(String ㍍)
w ㌧.㍸.㎏(String ㍍, FontStyle ૐ, Boolean ㎐)
w ㌧.㍸.(String ㍍, FontStyle ૐ, Boolean ㎐)
w 䳺.䶘…ctor(䵊 context, String familyName, FontStyle requestedStyle)
w 䳺.䶶…ctor(䵊 context, String familyName, FontStyle requestedStyle)
w 䳺.䶘.䶡(䵊 ෲ, String ㍍, FontStyle ୧, Boolean 䶢)
w 䳺.䶧.(String ㍍, FontStyle ૐ, Boolean 䶢)
w 䳺.仵.份(㕙 代)
w 䳺.仝.䧞(㕙 代)
w 䳺.䴐.VisitGlyphs(㕙 glyphs)
w 㔶.㕙.Accept(㕄 visitor)
w 㔶.㕁.Accept(㕄 visitor)
w 㔶.㕫.Accept(㕄 visitor)
w 㔶.㕁.Accept(㕄 visitor)
w 㔶.㕫.Accept(㕄 visitor)
w 㔶.㕁.Accept(㕄 visitor)
w 㔶.㕫.Accept(㕄 visitor)
w 㔶.㕁.Accept(㕄 visitor)
w 㔶.㕫.Accept(㕄 visitor)
w 㔶.㕁.Accept(㕄 visitor)
w 㔶.㕫.Accept(㕄 visitor)
w 㔶.㕁.Accept(㕄 visitor)
w 㔶.㕅.Accept(㕄 visitor)
w Aspose.Words.Document.SaveToPdf(Int32 pageIndex, Int32 pageCount, Stream stream, PdfOptions pdfOptions)
w Aspose.Words.Document.Ԕ(Stream ԍ, String ԋ, SaveFormat ԕ)
w Aspose.Words.Document.Save(String fileName, SaveFormat fileFormat)
The issue is already resolved in the current codebase. The fix will be included into the next hotfix, which will come out in 3-4 weeks. You will be notified.