View Single Post
Old 09-18-2023, 04:06 PM   #15
Karellen
Wizard
Karellen ought to be getting tired of karma fortunes by now.Karellen ought to be getting tired of karma fortunes by now.Karellen ought to be getting tired of karma fortunes by now.Karellen ought to be getting tired of karma fortunes by now.Karellen ought to be getting tired of karma fortunes by now.Karellen ought to be getting tired of karma fortunes by now.Karellen ought to be getting tired of karma fortunes by now.Karellen ought to be getting tired of karma fortunes by now.Karellen ought to be getting tired of karma fortunes by now.Karellen ought to be getting tired of karma fortunes by now.Karellen ought to be getting tired of karma fortunes by now.
 
Karellen's Avatar
 
Posts: 1,622
Karma: 9500498
Join Date: Sep 2021
Location: Australia
Device: Kobo Libra 2
I've come across this error a few times also. Sometimes I have ignored it, other times I have modified the metadata of the font file.

I am no expert on fonts, but as far as I can tell, if you check the internal metadata of the font file using something like FontForge or similar, you can check the internal naming.

I am not really sure which field is used, but looks like "Name for Humans" is the correct font name. Maybe one of the guru's could confirm?

But for this particular font, it seems to be full of errors according to the warnings in FontForge

-Edit-
I gave up on using smallcaps fonts. Instead I use, when necessary, fake smallcaps...
PHP Code:
.smallcaps {
  
font-size0.8em;
  
text-transformuppercase;

I have noticed that the Libra2 does not respect the text-transform: uppercase anymore. Something changed in one of their updates.
Attached Thumbnails
Click image for larger version

Name:	fontin.jpg
Views:	100
Size:	91.8 KB
ID:	203860  

Last edited by Karellen; 09-18-2023 at 04:21 PM.
Karellen is offline   Reply With Quote