View Single Post
Old 03-06-2025, 01:25 PM   #14
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,005
Karma: 147448039
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
I haven’t had any issues with pseudo-elements in ePub2. Most current devices/apps also don’t have a problem with them… and if your target market still supports old devices/apps then you should simply provide fallback coding:
Eg.
-Here is the old coding
-Here is the new coding

If your device doesn’t support new coding it will automatically ignore it (per the spec) and revert to the old coding…
The only way to do pseudo coding is to use spans for the fallback So no need to bother with the pseudo coding in the first place.

A Kobo using RMSDK will not work with pseudo coding. So there you go. That's a very good reason not to use code that's not compatible but can use other code that is compatible.
JSWolf is online now   Reply With Quote