Checking on the status here: still waiting on a new release?
For review, the problem still reproduces using Aspose.Words v8.0.0.0
The fonts on the server have all been refreshed, but the error still occurs.
The server fonts have been zipped up and are available for inspection/review at
Fonts.zip
An ETA on the fix or the identity of the offending font would be most welcome.
Thanks!
Hi
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.
Best regards,
Confirmed: removing the MICR____.TTF font allowed the conversion to PDF without error.
(Of course, now they can’t print checks - but this is only a temporary workaround).
Thanks for the quick reply. I’ll be watching for the release with the permanent fix.
Hi
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?
Best regards,
The issues you have found earlier (filed as 12061;13376) have been fixed in this update.
I still experience the same symptoms with v8.1.0.0 I have attached the font that causes the problem
Hi
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.
Best regards,
Hello,
It looks like the problem is in a version of font you use. Please try to use the one in attach.
Yours sincerely,
Alex
Hi,
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)
Hi Krzysztof,
Thank you for additional information. I will consult with Alex regarding this issue and provide you more information.
Best regards.
Hi Krzysztof,
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.
Best regards.
I am having a similar problem with Aspose.Words 9.1.0.0, with the following stack trace:
"Requested a name string that is not present in the font."
at ఆ..్( ో)
at ఆ.ౠ.౼(String ֺ)
at ఆ.ౠ.ಜ(String ಝ)
at ఆ.ౠ.get_()
at ఆ.ౠ.ಂ(String ఴ)
at ఆ.ౠ.౺(String ఴ, FontStyle ୢ, Boolean ౻)
at .ః.(String ࡉ, Font ଆ)
at ◽.☵.మ(String ࡉ, Font ଆ)
at ◽.☵.☻(Run ᛟ, Int32 ࡐ, Int32 Ӗ)
at ◽.☵.☹(Run ᛟ, ◼ ☺)
at ◽.☵.☸(Paragraph ወ)
at ◽.☁.☧(Cell ጔ)
at ◽.☁.☛(Cell ጔ, ဃ)
at ◽.☁.☙()
at ◽.☁.☗()
at ◽.☁.☖()
at Aspose.Words.Document.UpdateTableLayout()
Hi Will,
Thanks for your request. During converting document to PDF Aspose.Words reads font files and creates subsets of fonts, which are used in PDF. 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. Or you can try finding the font which causes the problem yourself, and attach this font here.
Also could you please attach your input document here for testing?
Best regards,
Hi Andrey,
It isn’t really practical for me to upload my fonts to you, they make up a 200+ MB zip. Would it be possible to simply not load the fonts which can’t be loaded?
My document is the same one uploaded to here: Differences between tables printed to .doc vs .tif which I was having problems with earlier. It looks like you can print it to an image fine, so ignoring whichever conflicting fonts are on my system would be preferable. It looks like this has been affecting a few people.
Could you recommend a way for me to narrow down which fonts are causing the problems? I’ve attached a list of my installed fonts if that is any help.
Hi Will,
Thank you for additional information. One more question, which version of Aspose.Words are you using? To check version of the library, right click on the dll, select Properties from the context menu, then select Version tab. You will see File version.
Could you please try using the latest version of Aspose.Words 9.1.0, and let me know how it goes on your side.
Best regards,
Hi Andrey,
Yes, I’m using 9.1.0.0, product version 2010.05.14, Aspose.Words for .NET.
Cheers
Edit: I diffed my fonts folder with a list of fonts from another machine which worked with the UpdateTableLayout call, and deleted some of them, and now it is running. I’ve not tracked down exactly which font file was in conflict. I’d still like to see a more robust fix to this in a future version, since I will have less control over installed fonts as we move towards deploying this code, particularly if the conflicting fonts are not even in use in the documents rendered.Thanks for the help all the same.
Hi Will,
Thank you for additional information. It is perfect that you already resolve the problem. But without your fonts I cannot reproduce the problem on my side. The current version of Aspose.Words already has mechanism for filtering “bad” fonts. It seems there is some different problem with your “bad” font.
Best regards,
I’m sorry to report that I have restored my font files, and it appears to still be working… which means I am not able to track down which font caused the problem. Perhaps one fell through the cracks when I backed up.
The issues you have found earlier (filed as 14623) have been fixed in this update.
The issues you have found earlier (filed as 12586) have been fixed in this update.