View Single Post
Old 06-12-2017, 10:11 PM   #9
Turtle91
A Hairy Wizard
Turtle91 ought to be getting tired of karma fortunes by now.Turtle91 ought to be getting tired of karma fortunes by now.Turtle91 ought to be getting tired of karma fortunes by now.Turtle91 ought to be getting tired of karma fortunes by now.Turtle91 ought to be getting tired of karma fortunes by now.Turtle91 ought to be getting tired of karma fortunes by now.Turtle91 ought to be getting tired of karma fortunes by now.Turtle91 ought to be getting tired of karma fortunes by now.Turtle91 ought to be getting tired of karma fortunes by now.Turtle91 ought to be getting tired of karma fortunes by now.Turtle91 ought to be getting tired of karma fortunes by now.
 
Turtle91's Avatar
 
Posts: 3,355
Karma: 20171571
Join Date: Dec 2012
Location: Charleston, SC today
Device: iPhone 15/11/X/6/iPad 1,2,Air & Air Pro/Surface Pro/Kindle PW & Fire
You should use classes and CSS to style your files. Inline or embedded styling should be kept to a minimum.

As far as using a device's default fonts - or specifying any font for that matter - IMO you should avoid defining fonts at all. Let the user determine what font they wish to read in via their own device settings. Only if the font is very specific and helps tell the story should it be defined in the CSS - and then it is safest to embed the font in the ePub to ensure that it is used on the widest number of devices possible.

Of course, there are some devices that just don't play well with fonts (and other standards) - you will just need to accommodate them if you must sell on that platform.
Turtle91 is offline   Reply With Quote