View Single Post
Old 06-25-2025, 05:12 PM   #50
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: 80,237
Karma: 148951761
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 RbnJrg View Post
As I said, it's useless for me to explain it to you, there is no one more blind than he who does not want to see.

I employ both; webkit code for those ereader that work with webkit code (Readium, Bibi Reader, JSReader, Thorium, Cantook, Kobo for Android, PocketBook, Reasily, Lithium) and standard code for those ereaders that doesn't honor webkit code. Have you ever read this by any chance?

https://webkit.org/css-status/#

That is webkit. And, how many properties are non-standard compared to standard?

I employ everything that work, for that reason my epubs can be read them practically on any ereader (on epub2 ereaders, the epubs look very nice and on epub3 ereaders, they look great).
But if the programs are ePub3 compliant, you don't need any webkit code. It matter not that they may be built on webkit.
JSWolf is offline   Reply With Quote