View Single Post
Old 03-27-2025, 09:48 AM   #12
RbnJrg
Wizard
RbnJrg ought to be getting tired of karma fortunes by now.RbnJrg ought to be getting tired of karma fortunes by now.RbnJrg ought to be getting tired of karma fortunes by now.RbnJrg ought to be getting tired of karma fortunes by now.RbnJrg ought to be getting tired of karma fortunes by now.RbnJrg ought to be getting tired of karma fortunes by now.RbnJrg ought to be getting tired of karma fortunes by now.RbnJrg ought to be getting tired of karma fortunes by now.RbnJrg ought to be getting tired of karma fortunes by now.RbnJrg ought to be getting tired of karma fortunes by now.RbnJrg ought to be getting tired of karma fortunes by now.
 
Posts: 1,827
Karma: 8700631
Join Date: Mar 2013
Location: Rosario - Santa Fe - Argentina
Device: Kindle 4 NT
Quote:
Originally Posted by theducks View Post
I think you are ignoring:
Fallback encoding is INVALID, thus tossing the WHOLE CSS on some devices.
I know this to be true on my old EZReader 100% or none
No, you didn't understand what Turtle91 wanted to say; in fact, the technique described by him is the best to deal with the ADE bug for epub2 ebooks. You need to employ TWO stylesheets; one of them is ONLY for ADE properties, the other one is for properties supported for Webkit/Readium ereaders. When ADE finds one property in the stylesheet for Webkit/Readium that doesn't like it, it will fully ignore THAT stylesheet BUT NOT ALL STYLESHEETS; the .css with ADE properties still will be honored by ADE. Watch the epub I attach and the .css I include; try opening it in ADE 2.x and in any other ereader not based on RMSDK; you'll understand better what I want to explain
Attached Files
File Type: epub ADE CSS Test.epub (2.4 KB, 83 views)
RbnJrg is offline   Reply With Quote