[bug] Some fonts not loading properly

I have some font files that just won't load in resolve (DVR17 under linux)

* I put them at the right place (other fonts I put there work fine)
* The fonts should be perfectly valid (they work system wide in other apps and also when used on-line in browser).
* If I load the file in a font editor (FontForge) and re-export them, then I can load them.

So I have a work around, it's a bit annoying but it works.
However I think the dev team should still investigate what causes the original TTF file not to be loaded by Resolve.

I've included an example TTF font where this happens, both the original file and the file I "rewrote" by loading / re-exporting in FontForge.

What did you change in FontForge? That might be particularly helpful to BMD.

(Without details, it sounds like the font is not conformant to the TTF spec and FontForge supplies missing items. There are long threads about video files appearing differently on different systems, mainly caused by different software/OS's ignoring, or not, flags within the files. As another example, many browsers will -- in different ways -- close HTML sections that aren't properly closed, etc, because there is so much defective hand-made HTML out there.)

I didn't change anything.

Literally "Open" -> "Generate Font / TTF" ...
Didn't change any attribute or anything.

And yeah, it's possible the original TTF has some issues, but they originate from popular font forge, are used quite a bit, and don't throw any warning when loading anywhere so ...

I could spend a while learning the TTF spec and trying to figure it out, but I'm pretty sure one of their dev can just feed it to whatever custom font loader they use (obviously they don't use the system wide one since that one loads the file just fine in every other app) and see where it errors out.

I didn't change anything.

Literally "Open" -> "Generate Font / TTF" ...
Didn't change any attribute or anything.

I think this'll be a good clue to BMD. Sounds like the font is defective in a way that's fairly common (i.e. that various tools ignore or fix by rule-of-thumb) and it's something that FontForge fixes automatically. Things like that also happen where a spec has room for differing interpretations.