Quote:
Originally Posted by jackie_w
It sounds like you'd prefer to change the koboSpan algorithm to one-per-paragraph. If so you'll need to figure out how to do that yourself. I doubt that it's a simple hack, given the variety of weird HTML markup that exists in the wild. On the other hand, developing something that works well enough with your own epubs is always easier than developing something that would also work well for everyone else.
Good luck!
|
thank you
Unfortunately what are the kepub expectations for the best rendering result is not very well documented. I understood during debug the KTE, that it handles the nodes, and the elements (plus the child elements...) separately and so creates the SPANS.
I am fully appreciated about your shared code. I played a lot with it as well.
My goal is to find out, what would be the best looking rendered result. (btw. If there is no tags between the <p></p>, Your hack does the same --> one spans per paragraph).
I simple wanted try out what is better: having long untouched texts or split them.
Having all my full appreciation for the KTE developer, I would like to ask, is that also a KOBO requirement to flatten the CSS, like calibre does?
I mean the calibre generated classes everywhere, instead of using the p+p, or h+p... approach for handling the paragraphs.