View Single Post
Old 10-22-2025, 05:01 AM   #11
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: 80,740
Karma: 150249619
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 DNSB View Post
Jon, isn't about time that you stopped whinging about eBook coding choices that you don't agree with?
  1. calibre will strip the extra spans that are 99% of the added code for kepubs. Or you can use the ModifyePub plugin which will do the same.
  2. Standard Ebooks like Vellum uses consistent code which, for me, means that using Sigil's saved searches especially with the new conditional run option or calibre's Editor Chains plugin makes it very easy to clean up the code.
  3. Standard Ebooks uses semantic markup. Very good for accessibility which is something I personally support.
  4. At this time, ePub3 has been the current ePub standard for over a decade. Isn't time that you gave up whinging that some ebooks just do not display well using ADE 2?

Yes, very few apps and ereaders will display Standard eBook's Advanced coding well. Oddly the ePub3 renderer on Kobo ereaders does render them well. Ditto for Thorium and Sigil. Perhaps you might want to re-read the warning? The one that reads: "Advanced epub—An advanced format that uses the latest technology not yet fully supported by most ereaders".
There's no reason the eBooks cannot properly display with RMSDK on a Kobo. It's stupid code that they don't need that's causing the problem. The code could be very simple and still be ePub3 with accessibility. But they choose to use really bad code that a lot of software won't understand.
JSWolf is offline   Reply With Quote