Quote:
Originally Posted by JSWolf
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.
|
Not at all true.
The pseudo-elements he was referring to were something like hr.ChDiv::after or h3::before.... IIRC these took a little longer to get widely adopted, but ::first-line and ::first-letter have been around forever. If kobo doesn't support them then kobo DRASTICALLY needs to update their software.
Quote:
Originally Posted by JSWolf
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.
|
If the devices in your target market refuse to transition into the 21st century then the fallback coding could be as simple as not displaying the first line in small-caps and instead showing a normal sentence....
for example:
The first paragraph supports pseudo elements.
The second paragraph doesn't and simply falls back to the older styling.
No spans were used in the making of this image...just a simple class (<p class="first">) and pseudo selectors. The paragraphs are otherwise identical.
It's certainly not as pretty, but it is definitely readable. If the user doesn't
like the basic look enough, then they can use a different/newer reader.
IF the publisher INSISTS on a "one ePub to rule them all" then this is perfectly acceptable. IF, however, the professional publisher has a different css file for different markets/devices then Bob's your uncle (I miss Hitch!).
You definitely are
not required to limit yourself to ePub2 ONLY coding just to accomodate the outdated devices...there are many other options!