View Single Post
Old 04-01-2026, 06:05 AM   #25
JSWolf
Resident Curmudgeon
JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.
 
JSWolf's Avatar
 
Posts: 82,980
Karma: 153234783
Join Date: Nov 2006
Location: Roslindale, Massachusetts
Device: Kobo Libra 2, Kobo Aura H2O, PRS-650, PRS-T1, nook STR, PW3
Quote:
Originally Posted by Turtle91 View Post
You are correct that a user choosing to override the font would cause the font to be…. Overridden. But that is true for just about ANY styling you put in the css. You can’t force the user to read things exactly as the coder wishes in an ePub; you’d need to use a PDF for that. At some point the user needs to take responsibility for breaking the ePub when they use the nuclear override option.
But, if there is a solution that works for both ePub2 and ePub3 and it happens to be more complicated because of ePub2, as long as it can be done, then it should be done even if the ePub3 only solution is more elegant.

As for psuedo selectors, they aren't part of ePub2. And you have to take into account Kobo and it's older RMSDK.
JSWolf is offline   Reply With Quote