View Single Post
Old 06-15-2023, 11:55 AM   #3
nabsltd
Fanatic
nabsltd ought to be getting tired of karma fortunes by now.nabsltd ought to be getting tired of karma fortunes by now.nabsltd ought to be getting tired of karma fortunes by now.nabsltd ought to be getting tired of karma fortunes by now.nabsltd ought to be getting tired of karma fortunes by now.nabsltd ought to be getting tired of karma fortunes by now.nabsltd ought to be getting tired of karma fortunes by now.nabsltd ought to be getting tired of karma fortunes by now.nabsltd ought to be getting tired of karma fortunes by now.nabsltd ought to be getting tired of karma fortunes by now.nabsltd ought to be getting tired of karma fortunes by now.
 
Posts: 524
Karma: 8500000
Join Date: Aug 2013
Location: Hamden, CT
Device: Kindle Paperwhite (11th gen), Scribe, Kindle 4 Touch
Quote:
Originally Posted by gonzalo_diaz View Post
What does that error mean, and how can I correct it?
My guess is that the mime type for the font in the manifest is "font/otf", which means an OpenType font, while Check Book expects that a .ttf extension would require a mime type of "font/ttf", meaning a TrueType font. It's an exceedingly minor nitpick and won't make any difference, because OpenType is pretty much a proper superset of TrueType, and the same rendering engine is used for both in every implementation.

I've seen fonts from commercial foundries where the file extension doesn't match the actual contents, and it goes both ways (TrueType in a .otf and OpenType in a .ttf).

Changing the extension to .otf and setting the mime type to "font/otf" wouldn't hurt anything, even if the font really is a TrueType font, and it should fix your error.
nabsltd is offline   Reply With Quote