View Single Post
Old 09-29-2020, 11:01 PM   #3
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
edit: Dang-it, ninja'd again!!

Some readers/devices think they know better how to display a book than the publishers that created them. Unfortunately, a lot of publishers prove them right... Also, there are many devices that simply can't display color - like eink...

Some of those readers/apps have the option to view in "publisher's mode", but that would require the user to select that option. Apart from that, you can't really "force" the reader to follow your css.

The best you can do is keep your css as simple as possible.... and possibly use media queries to determine how to style your spans.... a color display that is friendly to publisher's css => colored font; an older eink display => might need to be highlighted with an <em> tag with bold and/or italic styling.
Turtle91 is offline   Reply With Quote