Quote:
Originally Posted by Stevex
David
I understand why the epub acts as it does, but have 2 questions
- would it not be possible to have the epub work like the kepub ("epub spec" or not, after all the reality is that a superscripted link is always a footnote). I mean the kepub must be isomorphic to the epub but works differently.
- it seems to me that with epubs, the kobo looks first if you have hit an area of the screen for a kobo-defined action, i.e page forwards etc and only second if you hit a link in the epub
|
I don't really know how all this is implemented. My description above is an educated guess. But, the epub and kepub renderers are based on completely different libraries. What and how they implement things affects what can be done elsewhere. And of course someone at Kobo decides exactly what to implement and how.
But I doubt that it is looking at the Kobo defined actions first. If it did, no links in the text would work. I'm pretty sure this is a place where size does matter.
And we are mixing up two different thinks: link detection and activation with footnotes. The problem is that the smaller the link is, the harder it is to hit. For kepubs, Kobo does something to make it easier to hit. Handling the link as a footnote instead of a navigation link is a different thing. The epub renderer treats all links as navigation links. The kepub differentiates between them somehow.
Quote:
By the way I noticed that in the book I converted EVERY link got treated in the kepub as a footnote, is that a function of the conversion or the reader?
|
The driver/conversion isn't doing anything with the links. The kepub renderer is using heuristics to work out what they are. I don't know what they heuristics are, but, they seem to be based on where the link goes to more than the actual link. I think it respects epub3 notation, but my test case for this would match the destination heuristics that I think are in use. And, I've just tested a book on my Aura H2O. The contents page works as links, not footnotes as expected.