|
There's another thing that can be a (small) problem with omnibuses, especially with the Delphi books.
First, I thought that the Kindle measured chapters by file, like so:
- Book1_Chapter-1.html
- Book1_Chapter-2.html
- Book2_Chapter-1.html
- Book2_Chapter-2.html
So, it would state the time to read a chapter, based on the number of characters in the file. If chapter was split into two files, it'd see that as two chapters.
Well... WRONG ASSUMPTION.
The Kindle calculates its Time To Read per chapter using the Table of Contents in the book. Now, if the Table of Contents looks like this:
- Book 1
-- Chapter 1
-- Chapter 2
- Book 2
-- Chapter 1
-- Chapter 2
It will work perfectly, even if chapters are divided into multiple files. The Kindle seems to just calculate on the basis of all the files starting at "Chapter 1", up to and including the file just before Chapter 2.
Now, Delphi Classics mostly don't have chapters in their TOC:
- Book 1
- Book 2
- Book 3
When you jump to a book, there is an inline HTML TOC for the chapters of that book.
However, because of this, the Kindle treats the books as chapters (so it sees the entire omnibus as one book), with chapters called "Book 1, Book 2", and so on. So, the Time To Read for a "chapter" basically becomes TTR for the book you're reading, and TTR for the book becomes the time for the entire omnibus.
Is it a problem? Not really, but it makes TTR a bit useless. You'll only know how long the book will take you if you set it to chapter mode.
|