View Single Post
Old 09-23-2022, 05:17 PM   #94
JSWolf
Resident Curmudgeon
JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.
 
JSWolf's Avatar
 
Posts: 80,238
Karma: 148951761
Join Date: Nov 2006
Location: Roslindale, Massachusetts
Device: Kobo Libra 2, Kobo Aura H2O, PRS-650, PRS-T1, nook STR, PW3
Quote:
Originally Posted by jackie_w View Post
I also looked at this a bit more and I think you're right. The ligatures in this particular font aren't very distinctive anyway. Perhaps the missing tables aren't essential for ligatures to work.

What is noticeable to me is that kerning for Regular in kepubs is not right. Epubs look OK kern-wise. It looks like the "missing" GPOS kern tables are important to kepubs but not to epubs.

In addition, I think the "missing" tables are already in there somewhere because when I opened the Regular ttf with FontForge and regenerated the ttf without making any deliberate changes the GPOS/GSUB tables miraculously "reappeared" in the regenerated ttf. For someone who understands what they're doing it should be fixable. Whether it *will* be fixed by Kobo remains to be seen.
There is a problem with kerning in the regular font. It's not showing up when I view the font at https://fontdrop.info. That's even after a generate.

My guess is that it's because of the GDEF table not being correct or missing.

Last edited by JSWolf; 09-23-2022 at 05:23 PM.
JSWolf is offline   Reply With Quote