Font upload problem (2) | Community
Skip to main content
A
Anonymous
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

    Show previous replies
    Neil_Enns_-_Ado
    Adobe Employee
    Neil_Enns_-_AdoAdobe Employee
    Adobe 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
    RichinZ
    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
    Adobe Employee
    Neil_Enns_-_AdoAdobe Employee
    Adobe 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
    RichinZ
    August 18, 2015

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

    Neil_Enns_-_Ado
    Adobe Employee
    Neil_Enns_-_AdoAdobe Employee
    Adobe Employee
    August 18, 2015

    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
    RichinZ
    August 18, 2015

    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
    Adobe Employee
    Neil_Enns_-_AdoAdobe Employee
    Adobe Employee
    August 18, 2015

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

    Neil

    RichinZ
    RichinZ
    August 18, 2015

    Okay, thanks.

    RichinZ
    RichinZ
    August 19, 2015

    I just heard back from support and it looks like the installable font problem isn't just at the app level.

    According to support I can't use the fonts in an HTML article on Windows if they don't have the correct permission to install (just like you mentioned above).

    I guess it's time to contact the font designer.

    Q
    QuantumSwebb
    August 28, 2015

    Hello Nathan Marroquin‌

    Sorry if this is already answered, but I've read the entire thread and don't see anyone having a similar problem.

    I've validated my JSON file using several tools, so I'm sure that it's at least valid. I've double-checked that the friendly names I've given my fonts are the same that I'm using in my Cards. And yet, my fonts will not apply in my app.  Is there something else I could be missing? Here's the .zip file. I'm sure it's something obvious I've overlooked, just don't have another set of eyes to see it.


    Do you mind taking a look at it?

    Show more replies
    Terms & ConditionsAccessibility statement

    Loading footer...