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

RichinZ
Level 3
August 28, 2015

I looked at your json file and it validated just fine. I couldn't see anything wrong with it, granted I'm not an expert in json.

August 28, 2015

Thank you for looking at it, RichinZ I'm really not sure where the problem lies. Makes me think it's something in the setup of the cards, even though I've double & triple checked those. I'm sure an answer will present itself soon enough. But that being said, if anyone else has any ideas, I'm open to hearing them!

November 28, 2023

We encountered an issue while attempting to upload fonts during the font-manifest process. Despite following the steps outlined in the documentation, the fonts failed to load properly. Upon further investigation, we discovered that the font-manifest.json file contained hidden characters that were causing the invalidity. To rectify this issue, we recommend formatting the JSON as a plain text file. If this approach doesn't resolve the problem, it's advisable to contact support for further assistance, as the issue might be specific to the font files themselves.