View Single Post
Old 03-15-2023, 11:49 AM   #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: 79,998
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 Nightjar View Post
Hmmm... Not so easy – at least for me – because I must find an effective fallback (ePub2-compatible) method for ePub3 and HTML5 tags, like for instance <section> and <figure>, without deleting them.
The easiest (IMHO) way to do it is to start over and create your sample in ePub 2. Then convert to ePub 3 and put in the accessibility code, But do not put in any code such as figure and section and header. Don't use them for anything other then a placeholder. Don't use them in CSS and don't use them in the HTML with classes. As you are building your ePub, make sure you don't put in things that break significantly with ePub 2. When done, you'll have a working ePub that will work for ePub 2 & 3.

And don't use multiple CSS. Put everything in one CSS file.
JSWolf is online now   Reply With Quote