View Single Post
Old 05-09-2024, 03:27 PM   #28
DNSB
Bibliophagist
DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.
 
DNSB's Avatar
 
Posts: 47,260
Karma: 171291590
Join Date: Jul 2010
Location: Vancouver
Device: Kobo Sage, Libra Colour, Lenovo M8 FHD, Paperwhite 4, Tolino epos
Quote:
Originally Posted by JSWolf View Post
SE claims it's a compatible ePUb and it's not. So SE is not telling the truth. Either it's compatible or it's not.
They are fully compliant with the ePub2 or ePub3 specification. Is it their fault that you persist in believing that any ePub that does not display in ADE 2.01 is borked?

Quote:
Originally Posted by JSWolf View Post
The rule of thumb is to keep the code as simple as possible. SE's rule of thumb is make the code a complicated as possible. Would you ever use such convoluted code as SE does when there is zero need to do so?
To you, there is zero need to do so. For SE, there are reasons to do so. For myself, when modifying ePubs for my personal use, I will use more complex styles since I know what my devices and apps can handle. I will also use simpler CSS and rather often a mass of media queries when working on ebooks for others. This helps to avoid Kindle takedown notices which authors prefer not to see.

Quote:
Originally Posted by JSWolf View Post
SE is not a big publisher. But as we've found out from the OP, even the KePub is broken. Not broken in that it cannot be read, but broken in a way that some things do not work. If the code was made simple, then the KePub would work without error.
I would disagree. The OP does not see the ToC. This would happen if they have changed the extension from .kepub.epub to .epub such as by importing the kepub into calibre and not manually added a .ncx file. A PEBKAC error since that change would have your Kobo ereader using the RMSDK renderer rather than the WebKit based renderer. No matter what changes were made to the CSS, that ToC would not display.

As for not displaying the cover image while reading the ePub? Sorry, Jon, that is not a requirement. I have purchased and borrowed multiple ebooks that do not display a cover image from major publishers and indie publishers. Again, simplifying the CSS would not miraculously display the cover image when reading unless you add complexity to the ePub such as a xhtml file to display the cover image.

I did find your volte-face on whether SE is a "big publisher" to be rather amusing.

You have your way, I have my way, as for the right way, the correct way and the only way it does not exist.—Friedrich Nietzsche
DNSB is offline   Reply With Quote