Quote:
Originally Posted by davidfor
What font are you using? I did see something different with Gothic and Ryumin but it might be part of the test case rather than a real difference.
From memory, the first purchased kepub I looked at only had odd numbers in the spans. I remember wondering why, but can't think of a reason it would affect things. I think it was just that someone messed up a loop counter and incremented it twice.
Is there any chance of seeing the books? I can see if they behave the same on the beta firmware. And I think would manually fix the span count just to see what happens.
One thing I did just see when comparing a DRM free purchased kepub and a sideloaded kepub is where the space is between sentences and spans. For the purchased kepub, the space after the full stop is inside the span. For the sideloaded, it is between the spans. The examples are:
Code:
Purchased: tomb. </span><span class="koboSpan" id="kobo.3.2">He awoke
Sideloaded: indifferently.</span> <span class="koboSpan" id="kobo.8.2">“It would
The only way I could see that affecting things is if the space happened to be the place that was needed to be stored as the reading position. That might break something, but I would expect the book to open to the start of the chapter.
The other problem it could cause is with highlighting. If it starts or ends on the space, that could cause a problem. |
Haha, sorry about the late edit; felt a bit silly missing something so simple. The span/space issue could be realistic; in some books when I highlight a block of text, when I'm done there will sometimes be a single space that is not highlighted in the middle of the text; seems likely that it's connected to this issue.