View Single Post
Old 08-07-2025, 08:22 AM   #21
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,830
Karma: 8700631
Join Date: Mar 2013
Location: Rosario - Santa Fe - Argentina
Device: Kindle 4 NT
Quote:
Originally Posted by DNSB View Post
I agree that ePub2 is no longer a consideration.

However, I would have to disagree that Amazon is not king for commercial ebooks. For the authors, I do work for, even those who have gone wide, the majority of their income is from Amazon. For that reason, I can not and will not consider adding Javascript for any purpose where it's lack would be noticed. I will have to admit Kindle take down notices were responsible for a fair chunk of my early ebook cleanup jobs and a couple of those were due to ePub3 ebooks that used JavaScript.

For my personal use, I can go wild on using advanced features but for commercial work, KISS is definitely the only way to go. I do use a mix of ePub2 and ePub3 code but that is as far as I go at this time.
I think since this is the epub forum, we shouldn't speak about Amazon here, because the epub destined to be a .azw3 or .KFX format is another kind of epub. But of course, those epubs can't have js (and many others css3 properties).
RbnJrg is online now   Reply With Quote