View Single Post
Old 05-29-2013, 05:31 PM   #8
DiapDealer
Grand Sorcerer
DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.
 
DiapDealer's Avatar
 
Posts: 8,926
Karma: 40404050
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
A bad default option is better than no option at all. The newer Kindle Fire HDs simply ignore any embedded fonts if they're assigned to the 'body' element via CSS (even though Kindle Previewer's FireHD emulation mode indicates everything's hunky-dory). There simply IS no option to "use publisher fonts" on those devices. Embedded fonts for headers and special sections of text still work as expected, but they're making it harder and harder for ebook creators to dictate the standard paragraph font. And if you do succeed in dictating the standard paragraph font on those devices, you've effectively taken away the user's ability to change the font without hacking the ebook.
DiapDealer is offline   Reply With Quote