"Failed to convert to PDF Font:"
"Failed to convert to PDF Font:"
I have to use the font family "Good OT" for marketing reasons in my title pages. Before I took this position in December, they had been generating the docs in Word and then converting them to PDF. I'd like to generate straight to PDF. Unfortunately, I'm now getting this message when I generate the PDF:
"Failed to convert to PDF Font: Good OT. Using default font: Helvetica"
Is there any way to fix this?
Or is this an issue with Adobe?
It's especially frustrating since I only need it for the title page. I've tried adding the styles under the @media print section of my stylesheet, but no luck there. Even when they weren't there, the font still shows up in Flare when I type in the Title and Version number.
Thanks in advance for any help!
"Failed to convert to PDF Font: Good OT. Using default font: Helvetica"
Is there any way to fix this?
Or is this an issue with Adobe?
It's especially frustrating since I only need it for the title page. I've tried adding the styles under the @media print section of my stylesheet, but no luck there. Even when they weren't there, the font still shows up in Flare when I type in the Title and Version number.
Thanks in advance for any help!
-
- Propellus Maximus
- Posts: 810
- Joined: Wed Jul 25, 2012 11:36 am
- Location: Ann Arbor, MI
Re: "Failed to convert to PDF Font:"
I came upon this article and thought the Modifying CSS Files section might be of interest (hope it helps): How to Embed Fonts in MadCap Flare WebHelp. I realize this is for WebHelp, but you may be able to apply the same technique.
"I'm tryin' to think, but nothin' happens!" - Curly Joe Howard
Re: "Failed to convert to PDF Font:"
Didn't work. I followed the instructions as best I could and I'm pretty sure I did it right, but no luck. Thanks for the suggestion, though!
Re: "Failed to convert to PDF Font:"
MaggieA4, I'm wondering whether you were able to resolve this issue? After using Flare successfully for a long time, I'm now encountering this for the first time after updating my PC to Windows 10.
-
- Propeller Head
- Posts: 25
- Joined: Fri Mar 07, 2014 2:43 am
- Location: Cambridge
Re: "Failed to convert to PDF Font:"
I encountered this error today after upgrading to Windows 10. My exact message was:
Failed to convert to PDF font: MS Gothic. Using default font: Helvetica.
I'm not using the MS Gothic or Helvetica fonts anywhere in my project, so it was a little confusing.
I fixed it by downloading and installing MS Gothic.
Failed to convert to PDF font: MS Gothic. Using default font: Helvetica.
I'm not using the MS Gothic or Helvetica fonts anywhere in my project, so it was a little confusing.
I fixed it by downloading and installing MS Gothic.
Re: "Failed to convert to PDF Font:"
I am getting the same message on my PDF outputs and am also not using MS Gothic or Helvetica. I am also using Windows 10 (which was updated from 8.1), but can't say for sure if the messages coincided with making that update.
--Stephen
Re: "Failed to convert to PDF Font:"
We paid $500 for two fonts (which look exactly like the free ones I wanted to use, but NOOOOOO), and I am getting this error, which is a show stopper because the substituted font prints as gibberish. Also on Win10. Anyone find resolution? I'm about to just go back to the free fonts and just not tell my boss
Re: "Failed to convert to PDF Font:"
In my case, I was able to resolve the issue by right-clicking the font and selecting "Install for all users." This instructs Windows to put the font in the Windows/Fonts folder, rather than the appdata folder for a user.
-
- Jr. Propeller Head
- Posts: 1
- Joined: Mon Jan 14, 2019 8:59 am
Re: "Failed to convert to PDF Font:"
The "install for all users" solved the problem for me. Thanks!
Re: "Failed to convert to PDF Font:"
A big Thank You to the above posters.
In case this helps others, my problem was that our Icomoon font would not embed in PDFs. Yet I could add the icons to MS Word and when Word generated the PDF, the icomoon font listed as Embedded, and the fonts appeared.
Then I noticed the Warning 40040 Failed to convert to PDF font icomoon etc in the Flare build.
I am on Windows 10 and Flare 2017 r3. Running the font's Install for all users option required admin privileges, so I had to call IT. But it worked.
Funny how MS Word was not affected by this problem. I guess Microsoft still plays the same old games.
In case this helps others, my problem was that our Icomoon font would not embed in PDFs. Yet I could add the icons to MS Word and when Word generated the PDF, the icomoon font listed as Embedded, and the fonts appeared.
Then I noticed the Warning 40040 Failed to convert to PDF font icomoon etc in the Flare build.
I am on Windows 10 and Flare 2017 r3. Running the font's Install for all users option required admin privileges, so I had to call IT. But it worked.
Funny how MS Word was not affected by this problem. I guess Microsoft still plays the same old games.
-
- Propeller Head
- Posts: 51
- Joined: Thu Dec 27, 2018 10:35 am
- Location: Goleta (Santa Barbara County), CA
- Contact:
Re: "Failed to convert to PDF Font:"
Our intern was having this problem and this fixed it. Thank you, thad!thad wrote:In my case, I was able to resolve the issue by right-clicking the font and selecting "Install for all users." This instructs Windows to put the font in the Windows/Fonts folder, rather than the appdata folder for a user.
Brian
Flare + Analyzer 2022, Central, Capture 7.0, Mimic 8.1
Re: "Failed to convert to PDF Font:"
Confirmed. Same issue, same error, different font (Inconsolata). Fixed with right-clicking the font and selecting "Install for all users." Thank you!
-
- Propellus Maximus
- Posts: 551
- Joined: Wed Mar 05, 2008 10:50 am
Re: "Failed to convert to PDF Font:"
Same problem for me with the IPAPGothic font that we use to generate Japanese PDFs. Right-clicking the font and selecting "Install for all users" fixed it for me too. THANK YOU!
Kellie
-
- Sr. Propeller Head
- Posts: 249
- Joined: Thu May 24, 2018 3:11 pm
- Location: Queensland, Australia
Re: "Failed to convert to PDF Font:"
Another thank you for this. An upgrade to new computer and I thought copying the fonts directly into the Windows/Fonts folder would be enough. Although Flare will display the font, it cannot embed it in a PDF unless it has been 'installed for all users'. Yet one more upgrade snafu to remember!
Re: "Failed to convert to PDF Font:"
And it's also a big thank you from me too.
This drove me crazy for an hour, as I thought I was using the wrong font family name.
I can stop swearing now.
This drove me crazy for an hour, as I thought I was using the wrong font family name.
I can stop swearing now.
Re: "Failed to convert to PDF Font:"
People, where are you right-clicking the font? I can view the font in various places, but nowhere do I see the option Install for all users.
Using Windows 10 Pro and my font is "Circular Std Book", among other "Circular Std" variations.
Thank you.
Using Windows 10 Pro and my font is "Circular Std Book", among other "Circular Std" variations.
Thank you.
Re: "Failed to convert to PDF Font:"
I right-clicked the font file in Windows Explorer, and got a Install for all users menu option.EileenP wrote:People, where are you right-clicking the font? I can view the font in various places, but nowhere do I see the option Install for all users.
Using Windows 10 Pro and my font is "Circular Std Book", among other "Circular Std" variations.
Thank you.
But I'd guess you might only see that option if your account is an Administrator in Windows, as it requires admin permissions.
Re: "Failed to convert to PDF Font:"
Thank you for this post - it worked for me as well (Flare 2022). I had previously downloaded the font (Gotham Book and many variations) to c:\fonts (a directory I created) and then used the Fonts Control panel to add those to my Windows 10 system. They were then displayed in C:\Windows\Fonts. When I generated a PDF file from Adobe FrameMaker or Microsoft Word, the font was properly embedded. When I generated a PDF from Flare, I received the warning described in this post. Because the font appeared to be installed properly, I did not expect the "Install for all users" solution described here to work. I right-clicked on each font file name in c:\fonts and selected Install for all users. IT provided the Admin credentials each time. Now I can generate a PDF from Flare without the font warning, and Gotham Book is properly embedded. Thus my excitement and a desire to post my results. However, I am curious to understand -- why did this work?
Re: "Failed to convert to PDF Font:"
I had this issue and tried just about everything. But got mine to work. I'm not sure why it worked, but here it is.
Failed to convert to PDF Font: Source Sans Pro
Failed to convert to PDF Font: PT Mono
I uninstalled these fonts from Windows using Personalization>Fonts . I also had links to the fonts in my style sheets, such as:
@import url('https://fonts.googleapis.com/css?family ... 00,700,300');
@import url('https://fonts.googleapis.com/css?family=PT+Mono');
When I ran the build, no font errors and the text was using the correct font.
Again, not sure why it worked but it did. Maybe MCF wasn't sure whether to use the Windows installed font or the font linked in the style sheet.
Anyway, I hope it helps.
Failed to convert to PDF Font: Source Sans Pro
Failed to convert to PDF Font: PT Mono
I uninstalled these fonts from Windows using Personalization>Fonts . I also had links to the fonts in my style sheets, such as:
@import url('https://fonts.googleapis.com/css?family ... 00,700,300');
@import url('https://fonts.googleapis.com/css?family=PT+Mono');
When I ran the build, no font errors and the text was using the correct font.
Again, not sure why it worked but it did. Maybe MCF wasn't sure whether to use the Windows installed font or the font linked in the style sheet.
Anyway, I hope it helps.
Re: "Failed to convert to PDF Font:"
Usually this is down to the font being installed for one user when it needs to be installed for all users.