Quote:
Originally Posted by DNSB
Jon, if you want an ePub2 compatible .ncx file, download the ePub version.
|
They are not compatible with RMSDK. One or all of the @media statements causes RMSDK to think the CSS is broken and ignores the entire thing. These @media statements are not needed. Not for such simply formatted eBooks.
Quote:
|
Since SE makes it rather clear that the kepubs are for Kobo ereaders and unless you import the kepub into calibre which it will lose the .kepub.epub for a single .epub file extension or otherwise rename it losing the .kepub.epub extension, simply copying the kepub to your Kobo will keep the .kepub.epub extension and render using the WebKit based renderer.
|
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.
Quote:
|
However since you appear to believe the WebKit based renderer does not offer anything tht the RMSDK renderer does not also offer, please try viewing Harry Potter: A Journey Through a History of Magic or any similar book making use of ePub3 enhancements using RMSDK and let us know how the experience was.
|
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?
Quote:
|
BTW, I'm not sure that I would refer to Standard Ebooks as a big publisher.
|
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.