View Single Post
Old 03-18-2024, 10:05 PM   #13
geek1011
Wizard
geek1011 ought to be getting tired of karma fortunes by now.geek1011 ought to be getting tired of karma fortunes by now.geek1011 ought to be getting tired of karma fortunes by now.geek1011 ought to be getting tired of karma fortunes by now.geek1011 ought to be getting tired of karma fortunes by now.geek1011 ought to be getting tired of karma fortunes by now.geek1011 ought to be getting tired of karma fortunes by now.geek1011 ought to be getting tired of karma fortunes by now.geek1011 ought to be getting tired of karma fortunes by now.geek1011 ought to be getting tired of karma fortunes by now.geek1011 ought to be getting tired of karma fortunes by now.
 
Posts: 2,805
Karma: 7423683
Join Date: May 2016
Location: Ontario, Canada
Device: Kobo Mini, Aura Edition 2 v1, Clara HD
Quote:
Originally Posted by Aleron Ives View Post
Since KEPUB is just EPUB with extra span tags, the real question is why those tags are necessary. Are they used to calculate the 1 screen = 1 page metrics? Things like highlighting work fine in RMSDK without needing the extra span tags, so I don't really understand why KEPUB needs them, unless Kobo's WebKit implementation is just bad.
Developers probably got overwhelmed by EPUB CFIs and other stuff (it is a bit daunting at first, and somewhat easy to do incorrectly) and decided that they'd just add spans so it's easier to get locations without walking around stuff (just get the element at a point, then get the nearest span), and to provide some theoretical flexibility around updating the content of a book.
geek1011 is offline   Reply With Quote