Thread: First Line Pseudo Element in epubs
View Single Post
Old 04-09-2024, 08:34 AM   #13
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: 74,455
Karma: 129358310
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
Why, all of them, of course!

The devices should be maintained with soft/firm-ware updates with the latest versions. They also need to be backwards compatible to support all the older books. The opf states what version (2/3) the epub is, so it shouldn't be too hard for a reader to apply the correct function...if there are any differences.

Pseudo elements, in particular, have been around for a very long time. A device that doesn't support that css is, imho, broken...

That standard of treating unknowns as a null operation is to prevent books from crashing. If your device is old (no longer supported and/or company is out of business), or can't do color (eink), or something, then the device would ignore that css.
Sony Readers use an old RMSDK and there will not be an update. StandardEbooks eBooks won't work on a Sony Reader as they have code in the CSS that is taken as an error o the entire CSS gets ignored. I have pointed out the problem to them and they've ignored the report.
JSWolf is offline   Reply With Quote