Skip to main content
davis_navickas
davis_navickas
Known Participant
August 13, 2018
Answered

Font embedding issue

  • August 13, 2018
  • 1 reply
  • 3021 views

Hi, I'm currently having an issue with a font that I purchased to use for a form on a PDF file.

So let me explain this.

I installed a font from 'Google Fonts' and made a design with it.

Exported to PDF and made a form that clients can change the info with that font too.

Sent it and everything worked alright. They didn't have to download that font because it was embedded already in the PDF.

So I made another design with a font that I purchased because the free version of it didn't allow font embedding and I actually got an error when I tried doing that.

That's why I bought it so it would allow me to embed the font for clients to use too.

I installed the font, embedding was done but when I send it to clients they don't see that exact font, they see another one.

So it's like the embedding isn't quite done.

I reached out to the maker of the font and he said quote : if you want to display this font on another computer, then you must also install it

What is the point of paying for a font for it to be allowed to be embedded so others wont have to install it themselves. THAT'S what it means isn't it.

And just to find out that's not the case?

This topic has been closed for replies.
Correct answer Dov Isaacs

A font that has the embeddability flags set to allow preview and print should be embeddable within a PDF file, although not for purposes of forms fields. Forms fields require embeddability set for editable. Thus, when you choose a font for a particular purpose, you must ascertain that (1) the actual end user license agreement (EULA) allows for such use and (2) that the font's flags correspond to what you need the font for.

For example, a font's EULA may allow for embedding, but the flags in the font don't allow such embedding and Adobe software does comply with those flags. This technical problem is something you need to bring up with the font's vendor since you obviously are not getting what you paid for. They should issue you a fixed font file.

Another situation is the converse where the font's embeddability flags permit embedding for a particular purpose, but the EULA prohibits it. Legally, the EULA supersedes those font flags.

And finally, there is a situation, increasingly more common, where the EULA permits embedding and flags comply, but the EULA also requires payments of royalties when you distribute PDF files with the font embedded and/or use the font in a commercial design or logo.

For the record, none of the Adobe fonts licensed directly from Adobe or via its partner Fontspring or any fonts available via Typekit have any of the three issues mentioned above.

          - Dov

1 reply

davis_navickas
davis_navickasAuthor
Known Participant
August 13, 2018

That MathanifoScript font doesnt show up as Embedded even though I purchased it.

But the free font EBGaramond from Google Fonts works fine

davis_navickas
davis_navickasAuthor
Known Participant
August 13, 2018

I just found out :

The free version of this font has the same Font embeddability value : Preview/Print

So basically that means they did it so I couldn't use it for embedding... so only they can make it work for me.

There's no work around is it or am I just being robbed?

Dov Isaacs
Dov IsaacsCorrect answer
Legend
August 13, 2018

A font that has the embeddability flags set to allow preview and print should be embeddable within a PDF file, although not for purposes of forms fields. Forms fields require embeddability set for editable. Thus, when you choose a font for a particular purpose, you must ascertain that (1) the actual end user license agreement (EULA) allows for such use and (2) that the font's flags correspond to what you need the font for.

For example, a font's EULA may allow for embedding, but the flags in the font don't allow such embedding and Adobe software does comply with those flags. This technical problem is something you need to bring up with the font's vendor since you obviously are not getting what you paid for. They should issue you a fixed font file.

Another situation is the converse where the font's embeddability flags permit embedding for a particular purpose, but the EULA prohibits it. Legally, the EULA supersedes those font flags.

And finally, there is a situation, increasingly more common, where the EULA permits embedding and flags comply, but the EULA also requires payments of royalties when you distribute PDF files with the font embedded and/or use the font in a commercial design or logo.

For the record, none of the Adobe fonts licensed directly from Adobe or via its partner Fontspring or any fonts available via Typekit have any of the three issues mentioned above.

          - Dov

- Dov Isaacs, former Adobe Principal Scientist (April 30, 1990 - May 30, 2021)
Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices