Quote:
Originally Posted by davidfor
It shouldn't be. I have done this in the past, but, I've just realised the recent times was to put an updated position on another device, but, I hadn't actually opened the books to check. And in these cases, the books were not changing.
But, I have just tested and am probably seeing the same problem. I used FFF to download just the first chapter of a two chapter book and sent it to the device. Then I opened it and went to the last page. Then I used FFF to download the rest of the book. After connecting the device and resending the updated book, I had a look at the generated kepub and the span numbering wasn't what I expected. Which means the bookmark position stored would not have matched the same place in the book.
The extended drive adds the spans around each sentence. They are numbered from the beginning of each file. The number increases for each paragraph (headings and some other tags count as a paragraph) and then sentence inside the paragraph. So, "kobo.471.1" means paragraph 471, sentence 1. Every time I have looked at this past, the paragraph number starts at 1 for each internal file. But, for this file it isn't. But for this book, the number is starting somewhere else. I checked a couple of books I sent earlier (not FFF created books). One does start at 1 for each file, the other doesn't. It looks like it is creating unique numbers across the whole book. I have a vague memory of some discussion of doing this, but, I didn't think it was done. I will have to have a look at the driver to work out what is going on.
And, I can be very pedantic. But, only when it suits me.
|
I figured out a solution to this sort of. Since FFF always uses the same filenaming scheme, I can manually set the bookmark to
OEBPS/file####.xhtml#kobo.1.1 with the number being +1 from the chapter I left off. I did this manually for a few fanfics that actually didn't have bookmarks (before I switched to reading exclusively on Kobo) and worked as expected.