View Single Post
Old 12-27-2020, 08:51 AM   #46
davidfor
Grand Sorcerer
davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.
 
Posts: 24,905
Karma: 47303824
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
Quote:
Originally Posted by JSWolf View Post
Most novels do not have pictures or footnotes. I know some do and it you want to read the footnotes or be able to zoom the graphics, yes, KePub is better. But some books I've recently read that had footnotes I did not need t use a single footnotes as the footnotes were references to citations that I was not going to read. I don't need to know what publication some bit of the book was taken from. But be that it may, the problem is that these eBooks do not work with RMSDK.

If you look at Sony, nook, and Pocketbook, they all use some version RMSDK. Not everyone installs KOReader or even knows about it. So why insist on code that doesn't work?

I tested with @Davidfor's fix and it did not work, but removing that media query did allow the eBook to mostly work. But it still needs fixing because not all formatting working. But the code does not need to be so complicated I formatted the eBook with a lot simpler CSS code. And it's much more compatible.
Firstly, it does work. I was careful in my testing. I tested it on more than one book, including the original version of the one you edited, and more than one device. If you think it is broken, post the book to prove you got it right. Did you actually put it on a Kobo device?

And I'm curious about what formatting didn't work. I can think of some, but, that is stuff that would fail because it is not supported under ePub2 or the RMSDK, but, that is expected and they fail gracefully. I'm thinking of things like small-caps.

And you are wrong overall here. Your code will work for the RMSDK based ereaders, but, does not take advantage of newer features in other ereaders or apps. Some of those things are good to do. Including that @media query, if it is doing what I believe it is doing. Unfortunately, I don't have something I can test it on. They are trying to produce books with some style and automate the build as much as possible. That will mean some concessions, but, overall, I think the books look good where they work. I'm mainly disagreeing with what the base level support should be. I can demonstrate the "Compatible epub" does not work in two environments. I can think of at least one more where I am sure it won't, plus a couple of others where it probably won't work. That makes use of the word "Compatible" questionable.
davidfor is offline   Reply With Quote