View Single Post
Old 03-17-2021, 03:44 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: 79,758
Karma: 145864619
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 hobnail View Post
I'm glad to hear someone say this; we keep hearing people say that epub3 "doesn't work" with the current ereaders. Whenever I redo a book from PG I always start with a blank epub3. The only epub3 stuff that I may use is some of the newer html tags but even that is minimal. So the html and css is mainly epub2 but the container is epub3. The metadata is epub3 probably; I'm using Sigil.
It's not that ePub3 doesn't work with current Readers. It's that some features do not work in a lot of cases with older software, older Readers, a lot of Android reading software, etc. So you just have to be careful how you code the ePub3 and you have to know what your audience is. You can make a simple ePub3 with accessibility that will work in most cases.
JSWolf is offline   Reply With Quote