View Single Post
Old 05-10-2013, 12:01 AM   #33
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,361
Karma: 20212223
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
It seems most of the argument here has been about font type/style with a couple "I hate backgrounds" thrown in. That seems to ignore the artistic desire of the creator. If the author wants a specific font, they need to embed that in the ePub; likewise with a background. The real issue for those people who don't like the font/background is the ability to turn it off or change it with their current reader/app.

I continue to be chagrined at how much we limit ourselves because device x or app y doesn't support a particular feature...we cater to their limits. Some of that is understandable - I wouldn't create a book that only reads properly on a holo-projected wristwatch - but I should be able to create based on current technology. There are readers/apps that DO support changing font/background. If the end user wants that ability, then it is incumbent upon them to purchase the device that supports it - not force creators to limit themselves to old devices/technology.

Device/app developers provide what the customers demand...

Last edited by Turtle91; 05-10-2013 at 12:03 AM.
Turtle91 is offline   Reply With Quote