View Single Post
Old 02-10-2016, 03:25 PM   #20
eschwartz
Ex-Helpdesk Junkie
eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.
 
eschwartz's Avatar
 
Posts: 19,421
Karma: 85400180
Join Date: Nov 2012
Location: The Beaten Path, USA, Roundworld, This Side of Infinity
Device: Kindle Touch fw5.3.7 (Wifi only)
Quote:
Originally Posted by JSWolf View Post
Is there a way to do it the graphic way for Mobi and the font way for KF8? If not, I'd say screw Mobi and just left KF8 work properly.
That attitude is exactly why you don't actually work in the ebook publishing business...



The usual solution for Kf8 vs mobi7 (ask @Hitch) seems to be the use of media queries to produce a graceful styling fallback.

If you need an embedded font because the system fonts don't actually cover your character set, then there is no solution I can think of other than images. You could use media queries to only show the version applicable to the target format, although I think you will end up with those images padding the size of the AZW3.

Last edited by eschwartz; 02-10-2016 at 03:30 PM.
eschwartz is offline   Reply With Quote