Quote:
Originally Posted by library addict
No, I didn't even notice that really. I'm talking about all the extra "span" coding, like for the last word of every sentence/paragraph, having dropcap letters on the copyright page, etc. They never used to be so clunky.
|
I take it you are referring to the last words with potential runt, last word before potential runt, last word, etc. spans? While a bit ridiculous, they don't seem to have much effect on the reading experience. What my wife runs into with the scenebreaks is losing chunks of paragraphs when reading using the RMSDK renderer. The ACCESS renderer is happier with the scenebreaks but has done some odd bits for the last word/runts spans.
*
I have a set of saved search/replaces for Sigil that takes care of her issues so only takes about 3 minutes to clean the book but it shouldn't be necessary.
* For those who aren't familiar with some of the oddities of the Kobo ereaders. Except for the original Kobo/Kobo WiFi, they use two epub renderers. Adobe's RMSDK for epub2 and compatibility with Adobe's ADEPT DRM and ACCESS's Netfront BookReader EPUB edition/Kobo WebKit for epub3 ebooks using Kobo's proprietary DRM. When sideloading, a .epub extension uses RMSDK while a .kepub.epub uses ACCESS/Kobo WebKit. In theory, a .fxl.kepub.epub extension would work for a fixed layout epub3 ebook but I've never tested that feature.