View Single Post
Old 09-15-2023, 01:48 PM   #20
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: 517
Karma: 8500000
Join Date: Aug 2013
Location: Hamden, CT
Device: Kindle Paperwhite (11th gen), Scribe, Kindle 4 Touch
Quote:
Originally Posted by Turtle91 View Post
Section dividers, fleurons
Both of these can be handled by using embedded fonts that contain the correct glyph. Using embedded, subsetted fonts solves a lot more problems than it creates...only if you want to support MOBI is it a real problem. And, I'm pretty sure that wanting to support MOBI is a bigger problem.

Even if you are distributing commercially, embedded fonts are not a problem...an Adobe font subscription is $60 per year (get the "InCopy plan" and just ignore everything but the fonts), and you only need the subscription active at the time you perform the embed. All the fonts in the subscription are licensed for embedding.
nabsltd is offline   Reply With Quote