I am having real problems getting fonts that I upload to register within the app. I have followed the instructions here:
...but I can't get the fonts to register in my preview app when I assign them to card metadata.
I have rebuilt the app several times and reinstalled but no joy.
If anyone felt charitable enough to have a look at the code below and see where I have inevitably gone horribly wrong, I would be very grateful!
"description": "Example font file.",
"fileName": "Font Bureau - Amplitude-Black.otf",
"fileName": "Font Bureau - Amplitude-Bold.otf",
"fileName": "Font Bureau - Amplitude-Regular.otf",
"postScriptName": "Rockwell Bold"
"postScriptName": "Rockwell Bold Italic"
"postScriptName": "Rockwell Italic"
Usually the issue with descenders being clipped is the font file itself and the way the baselines were set up in the font file. What solved the problem in the few cases we encountered was opening the font in a glyph editing tool and adjusting the cropping line them so it is lower than the descenders.
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" font management in the near future.
I'm still having problems getting my fonts to pick up. Worth noting re: the above point about properly formed .json files, that when I download the sample font .json file from here:
....on my PC and run it through JSONLint, it reports an "unexpected token error"....!
However, I have got a valid font .json now, and I have been careful to copy the exact font names. I've rebuilt the app today, but no joy getting it to register in the app, I'm afraid. Is there anyone who I can send my files to to take a quick look? As someone has pointed out above, this is a fairly significant obstacle to development - not least because the default font weight is not editable so I can't add bold or italic formatting to my card metadata as I would like...
I'm running Windows 7 Professional to build the app. I then have to sign the app on my Macbook Pro running OSX Yosemite to upload it onto my iPad.
All help gratefully received!
Do make sure that your JSON is properly formed. This tool is a good way to
catch problems. Copy+Paste your font JSON into it.
sr. product manager | digital publishing | adobe | +1 415 832 2790 office
| +1 415 640 7206 mobile
Can you send me a screenshot with the cropped descenders? (you're using iOS, correct?)
Also, what font are you using? Does the same occur with other fonts you may have tested? (it would be great if you could provide us the font file so we can test it on our end). It may be a rendering glitch with that specific font.
This issue is happening on more than one card. But, as an example, here are the settings for one of the cards it's happening on...
Text is set to Middle, with 0 padding all around in Card Layout, leading 1 and 20 bottom margin in Metadata Style. I have 2 metadata fields and the descenders of the second metadata field are getting cut off.
Any ideas as to what I should change?
Your card design may cause the descender truncation.
If text is set to the bottom of the card, with 0 padding (Card Properties: Layout), 0 Bottom Margin and a small Leading value (Card Properties: Metadata Style) -- you could get truncated descenders.
But this depends on your card design.
We've been building on iOS. And to answer your questions...yes, we are able to see the content published in the app and all metadata is currently in the default font. We've matched font names exactly. We have an earlier version of the app with the fonts working perfectly. We had to go back in and change a few icons and splashscreens, so we had to resubmit the app. Once we did that, the fonts stopped showing up.
I've tried it myself with an iOS app, and worked for me.
Can you tell me what platforms are you trying this on? (iOS, Android, Win?)
Do you see the content you published in the app ? If yes, metadata are rendered with the default platform font, correct?
Are the font strings defined in the manifest an exact match with the strings you added to the card templates?
Thanks Andrei - yes, I can confirm we have the fonts and manifest at root - no extra unwanted folders. For what it's worth, I am running this off a PC, and so that's where I did my zipping (although I did try rebuilding the app on a mac as well, no joy there either).
We are looking into possible back-end issues that may be causing this.
Meanwhile, I just want to make sure that the .zip you upload has fonts and manifest right at the root of the .zip, and not within a folder in the .zip package. That is sometimes the "culprit".
Having the same problem here. We were able to get our fonts loaded into an app we've built. But, once we made a change to the app and re-signed the app, the fonts are no longer active. Wondering if there isn't something happening on the backend that's causing this.
Any assistance would be greatly appreciated.