Font upload problem (2) | Community
Skip to main content
August 13, 2015
Solved

Font upload problem (2)

  • August 13, 2015
  • 23 replies
  • 7186 views

We did all the steps of the font-manifest (https://helpx.adobe.com/digital-publishing-solution/help/cards-layouts.html#fonts-cards‌), but we are unable to upload our fonts on our build. We read the last topic about it and we followed the steps indicated by Andrei, but without success.

"When creating the manifest, please make sure the json file is actually named "font-manifest.json". If you name it fonts.json, fonts won't be baked in the app properly and won't work. (this was the problem this time around) We're looking at "manifest-free"

Here is our manifest: https://www.dropbox.com/s/6g4i7to7f1ojrc9/font-manifest.json?dl=0

Could you help us?

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by nathanm206

I took all you font-manifest.json text and copied it into a couple different online online JSON validator tools and they all came back invalid. It looks like there are a number of hidden characters that is causing the failure. The first three hits with this query return some tools: json validator‌.

To clear up these hidden characters you should format the JSON as a plain text file. I hope this helps. If not, I suggest contacting support, this may be specific to the font files.

23 replies

Neil_Enns_-_Ado
Employee
August 18, 2015

Yeah, that’s my guess. We saw this with another customer and it’s entirely at the OS level. We ask for the font and the OS refuses to provide it.

Neil

RichinZ
New Participant
August 18, 2015

Some of them are print/preview and others are listed as installable. I'm guessing if they're print/preview they won't work.

Neil_Enns_-_Ado
Employee
August 18, 2015

Hi Zac,

For Windows it's possible your fonts are tagged with a setting that indicates they can't be embedded, and if that's the case the Windows OS won't load them in our app. You can verify this by looking at the font properties in Windows (right click on the font file, select properties, details tab) and look at the font embeddability field.

Neil

RichinZ
New Participant
August 14, 2015

I've got it woking on iOS and Android now. Is there a bug with Windows? Because it's not working on Windows.

New Participant
August 14, 2015

It worked here! Thanks!

RichinZ
New Participant
August 14, 2015

You're right, it was the file. The problem with the validator tool you suggested is that it doesn't highlight hidden characters, so it's basically only helpful by telling me that my JSON file sucks. I did find this validator tool, however, that not only highlights the hidden characters but even allows me to edit the file while testing it: http://codebeautify.org/jsonvalidate

Now my fonts are working great.

New Participant
January 13, 2023

hi, @Richiinz thanks for the answer it is really helpful for me. 

nathanm206Accepted solution
Employee
August 14, 2015

I took all you font-manifest.json text and copied it into a couple different online online JSON validator tools and they all came back invalid. It looks like there are a number of hidden characters that is causing the failure. The first three hits with this query return some tools: json validator‌.

To clear up these hidden characters you should format the JSON as a plain text file. I hope this helps. If not, I suggest contacting support, this may be specific to the font files.

New Participant
January 6, 2023

Hi, @

thanks for the answer it is really helpful for me. 

best wishes for you.

RichinZ
New Participant
August 14, 2015

The other funny thing is the fonts are working just fine in my HTML articles.

New Participant
August 14, 2015

Hello Nathan, it's the first scenario: the fonts aren't properly applied when we view our app on the device.

Thanks,

Alberto

RichinZ
New Participant
August 14, 2015

What sucks too is that I had them working during the Beta.