We're sorry Aspose doesn't work properply without JavaScript enabled.

Free Support Forum - aspose.com

HELP - "Requested a name string that is not present in the font." ASPOSE WORDS

Im using a trial of ASPOSE words - dpownlaod v8 and get an issue when i runt he project and generate a pdf.

I get the following error "“Requested a name string that is not present in the font.”

It works fine when generating a RTF but fails on the PDF.

It works on a colleagues machine Vista but not mine - also vista

It also works on a sever Win 2003 but i need to find out what is the issue so i can resolve.

I attach the source template document and also a word doc that has a screengrab of the bug details.

Please help!!!

Hi

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.

Best regards,

The link to the zipped files is below.
FONTS.zip

Hi

Thank you for additional information. I will check your fonts and let you know which of them causes the problem.

Best regards,

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 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.

Best regards,

Although you say it doesnt like these fonts - is there a reason why.

Is it the type of font.?

The filename?

The underscores?

appreciate your help.

Hi

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.

To be properly read, font file should conform requirements described in TTF specification:
https://docs.microsoft.com/en-us/typography/opentype/spec/otff

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.

Best regards.

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?

Any other troubleshooting hints?

Hi

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.

Best regards.

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.


This message was posted using Notification2Forum from Downloads module by aspose.notifier.

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.