View Single Post
Old 06-25-2025, 04:24 PM   #44
RbnJrg
Wizard
RbnJrg ought to be getting tired of karma fortunes by now.RbnJrg ought to be getting tired of karma fortunes by now.RbnJrg ought to be getting tired of karma fortunes by now.RbnJrg ought to be getting tired of karma fortunes by now.RbnJrg ought to be getting tired of karma fortunes by now.RbnJrg ought to be getting tired of karma fortunes by now.RbnJrg ought to be getting tired of karma fortunes by now.RbnJrg ought to be getting tired of karma fortunes by now.RbnJrg ought to be getting tired of karma fortunes by now.RbnJrg ought to be getting tired of karma fortunes by now.RbnJrg ought to be getting tired of karma fortunes by now.
 
Posts: 1,802
Karma: 8700631
Join Date: Mar 2013
Location: Rosario - Santa Fe - Argentina
Device: Kindle 4 NT
Quote:
Originally Posted by Falkor View Post
Ensuring backwards compatibility for a renderer with broken forward compatibility sure is a pain.
Not if you follow the correct method. You have to write a little more css code, but it's nothing special. It may be a little more difficult the first time, but in subsequent ebooks you use what you've already written; it's much more cut and paste.

Quote:
Might be one of the reasons why it's taking so long for epub3 to catch on.
It's slow because no e-reader device has properly implemented epub3 (though the Tolino Shine is close to offering adequate support). Android, however, boasts many e-readers with great epub3 support: Cantook, Reasily, Lithium, PocketBook, Kobo, and Infinity Reader (also is still good Gitden but you can't find it anymore in Play Store).
RbnJrg is offline   Reply With Quote