Quote:
Originally Posted by milady133
Just from your screenshot, I think it might be more complex than what you imply. Your page just shows a lot of hyperlinks (footnotes) in just one page. That possibly will break havoc in the calculations for the stats, depending on how they are internally stored:
- A file for each footnote?
- One dedicated file for all of them?
- The footnotes stored at the end of the chapter file?
...
Just my two cents
|
It is more complex that what @Uncle Robin implies. And he knows that. But, before you suggest some things, make sure you actually read the all the thread. Especially posts that explain something about how the calculation is done.
And:
- Links do not have an affect. Except that one part of the calculation uses the file size. And if there are links with hrefs, that increases the file size without increasing the displayed text.
- The calculation takes into account each file and anything in it, whether it is a footnote or note.
- If the footnotes are at the end of the chapter, then is just normal text for reading and progress calculations. To page to the next chapter, you must go through these footnotes. If you navigate to it, the page position and percent read should update. If, as is common, the footnotes are in a smaller font, it will reduce the total pages but not the percent read as you go through it.
And two things I didn't think of mentioning in my explanation above:
- The internal files are referenced in the manifest, spine and ToC. The latter two have a subset of the first. I don't know what happens if there is a file that does not have a ToC entry or for a file in the spine with attribute 'spine="no"'.
- There is an option to ignore end matter from the reading progress. I don't know how that works. I don't know if it affect the page count, the percent read or the time to read. Or how the end matter is determined. Though the latter probably requires the book to be ePub 3 as that does have markup for sections of the book.