Font Embed does not add fonts to prototype correctly, will not render correctly

Julian Dyer shared this problem 2 years ago
Known

When sharing prototypes the font embed message comes up. I try and embed the fonts required, I can add one font which will give a green tick symbol in the left pane, but when trying to add the second font file the font will not add to the right pane.


If I select the regular weight of the font, all of the fonts listed go green, but when rendering the prototype from a shared link, they do not render in the correct weight.


This causes fonts in the shared prototype. It is essential that out reams can see the correct rendered font weight. Please fix this bug.

Comments (13)

photo
2

Hi Julian,

There are two issues which I have encountered that seem related to your issues, and I have been discussing solutions for both of them directly with JIM. The first one is regarding the ability to embed fonts. Here is the latest response I received regarding this issue:

"JIM wouldn't accept [my files] as the correct font files. --> You are right, there is a bug associated when trying to embed a font with any of the following family styles (Black, ExtraBold, Bold, SemiBold, Medium, Regular, Light, UltraLight, Thin ) . Our development team has already resolved that and will be available on our next release."

The second issue has to do with font weights not rendering correctly and. I am still awaiting a response on this particular issue. You can check to see if you are having the same issue I am having, which arises for me when I change the font of an element from its default (usually Roboto, I believe) to Avenir Book. With an element selected, I set its font and font weight in the Properties panel/tab by selecting Avenir Book within the Font property. In CSS terms, the font-weight of Avenir Book is 400. Yet, with the same element still selected, if I look at the CSS panel/tab, the font-weight has an incorrect value of 800. If, in the Properties panel/tab, I change the font weight from Book to Light then back to Book and check the CSS panel/tab again, then font-weight in CSS now has the correct value of 400. So, something isn't properly synching the Properties panel/tab and the CSS when initially changing the font of an element.

When I receive a response regarding this issue, I will follow up here.

Hope this helps. Cheers!

photo
2

Do you know when this problem will be fixed? It is causing serious issues when we are showing client and dev teams work.

photo
1

We are releasing a patch for this bug in our next update, which is coming in the next few weeks.

photo
2

Hi Danielle, I am still experiencing this issue when I go to share the prototype. I will try to add the font to the embed list but it will either say "This file doesn't have any of the fonts listed" OR it will not upload and stay grey as if I did nothing at all (no green checkmark). Above you said you released a patch for this bug, but I'm still experiencing. Can you advise? Thanks!

photo
1

This seems to be a different issue. The issue is likely related to subtle differences in the font files that Justinmind can't parse, and so the font files appear to be different, and won't embed correctly. This is something we're working on fixing for future releases, but unfortunately there's no solution for this right now.

photo
1

Still having the same type of problem, it doesnt let me embedd the files just like Stephanie's situation. Is there a solution to this already?

photo
1

Unfortunately no, but I will let our team that more people are looking for a solution.

Fixing this requires a fundamental restructuring of how fonts work in Justinmind, so it is a difficult issue to solve.

photo
1

is there a way that my final product can have the font that im trying to use?

photo
1

You may need to download the font from another source. Can you attach the font file here so we can test it out? We may be able to find a way to embed it, or find a different source for it that will work with the embedding process.

photo
1

This are the files

photo
1

It looks like there is an error with the naming convention for the fonts. It shows an extra character at the end of the name, which Justinmind can't recognize.

eeb0a24c4729acf0888de3ec02dbd256

photo
1

Is there a way to correct that?

photo
1

Yes, you'll need to use Font editing software to rename the fonts. The linked version is for non commercial use, you'll need to download the professional version for commercial use. Before you do so, you should contact the creator/license distributor of the font to verify you have the permission to modify the fonts.

photo