Font upload problem (2)

[Former Community Member]

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?

[RichinZ]

I'm also having this problem. I've been working on it for the last day and can't get anywhere.

Here is our manifest: https://dl.dropboxusercontent.com/u/19036466/font-manifest.json‌

FYI, I'm building an iOS App running on iOS 9.

[NMarroquin]

Is the problem that you cannot upload the fonts, or that the fonts aren't properly applied when viewing your app on the device? If it is a problem uploading please post a screenshot.

[RichinZ]

They're not properly applied for us.

[RichinZ]

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

[dpsa53128946]

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

Thanks,

Alberto

[RichinZ]

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

[NMarroquin · Accepted solution]

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.

[Edythe987]

Hi, @NMarroquiin

thanks for the answer it is really helpful for me. 

best wishes for you.

[RichinZ]

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.

[jhon121212]

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

[dpsa53128946]

It worked here! Thanks!

[RichinZ]

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

[Neil_Enns_-_Ado]

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]

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]

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]

Would this be the same case for using fonts in HTML articles on Windows? The fonts are packaged with the article.

[Neil_Enns_-_Ado]

Not sure on that one. We just have the web control render the HTML, the DPS app is totally uninvolved in that portion.

Neil

[RichinZ]

The articles are working fine on iOS and Droid...

Can I email you my article file so you can take a look?

[Neil_Enns_-_Ado]

You should call enterprise support and ask them to investigate the issue for you.

Neil

[RichinZ]

Okay, thanks.