Some fonts are rendered as boxes

Hi, I am running into a bug with displaying of the fonts, some fonts show up as boxes in fontbase but work elsewhere on the system.

It seems like an OTF issue because I manually converted the problematic fonts to TTF and fontbase showed the correctly. Weirdly when I covert the TTF back to OTF the issue goes away and they still display fine!

  • This is happening on both Mac OS Catalina and Windows 10 with the same fonts
  • FontBase version 2.16.0 with Awesome subscription.

4 Likes

Can you send me these specific fonts in a direct message so I can take a look?

Im experiencing the same issue
Windows 10
Fontbase 2.16.`0
fontbase monthly subscription

Im experiencing the same issue. How do i send you a direct message?

Click on my photo, there will be a message option.

It doesn’t give me a message option. Could it be becuase I just signed up for the forum a few hours ago?

Maybe. Can you send us an email to mail[at]fontba.se?

this must be a silly reply, but my understanding was that you get boxes when that font does not have those characters in its character set (or possibly, your screen char set can not display those characters)?

Not every font has every character in it. The fonts on the screenshot do not contain the characters that you have entered in the text box.

But the issue in the original post is different from this.

Is there any progress with this? I have a bunch that display this way
Thanks

Edit: I just converted a TTF file with this issue to otf. The font immediately showed. Once I deleted the test file it was back to boxes even when I overwrote the original TTF file with one that had been converted to OTF and then back to TTF. This is some odd behavior :grin:

1 Like

this is true and is known.

THIS is something a whole lot different!

this is almost ALL some 4,000 fonts not displaying

and for your additional info, i had a collection of fonts that i had specifical;l;y selected because they DID display all the Vietnamese diacritics - and NOW many of them do not display all. wht is actually suprising is for this selected font subset with diacritics, how many of them DO display

of the total font list, i would estimate that some 90% of fonts do NOT display ANY characters

and what should be noted is that ALL the characters of a font do not display - NOT just selected letters. even when the text is only the default QBF text

1 Like

I have the same problem. All my added fonts (5000) are just showing as boxes. They are all TTF and show up fine in the Windows Installer, and also work.
I run version 2.18.1 on win11 and tryed reinstaling, restarting and refreshing, with no positive result.

pleas help ^^’

Hello @Zneb, thank you for the post and welcome to the forum:)
Is it possible that the fonts are missing the glyphs you’re trying to view via the preview text?
If you open the Family page and go to the Glyphs tab - can you see the characters properly there?
Hope this helps,
Yuriy
FontBase Dev Team

Hello @dec, thank you for the post and a good explanation.
What do you mean by “did” and “now”? Which dates or app versions are you referring to?
This can help us better understand what the problem might be
Thank you again,
Yuriy

Hi Yuri. This is not a problem with the font files and rathe a problem with Fontbase. I have been able to mitigate it by deleting the fontbase folder from my ~/Library/Preferences/Fontbase folder which resets the preferences but fixes the problem but it can come back again but I can verify that doing this fixes those missing font previews at least temporarily.

2 Likes

They all have the same Glyphs prevew, i also found out, that for some reson the family is not grouped so all the different font types like italic and bold are seperate. (Just in fontbase, windows is doing fine)

Thank you for the investigation and for posting the workaround :pray:
Could be some internal issues with the platform FontBase is based on.
We’ll try to investigate further to find what the root cause might be and fix it.
Thank you again,

Thank you for checking :pray:
As for grouping - it would strongly depend on how font designers chose to input data in the font file itself and yes, this type of situation can happen with certain fonts, unfortunately.
Will take this into account when designing future improvements.
Thank you again,

so there is no way to use fotbase for me at the moment? Is there a way to eddit my font so that it will work with fontbase? So that I at least can see the correct font in the glyphs tab?

Thank you for the quick reply.
Have you perhaps tried the workaround suggested here?

Do keep in mind that will probably remove some app data as well, so be careful, perhaps making a copy of the folder before trying the workaround can be a good idea.
Hope this helps,