Quote:
Originally Posted by davidfor
I wasn't quite sure whether you were asking a question or making a joke. So, I decided to answer it. And I generally agree with you on this. When I edit a book I try to keep the overall style the same. And make as little impact on the internal code as possible. Occasionally, it is so bad, that I just throw it away and start again. There are some book sources, that I automatically do this. Smashwords tends to be one.
But, splitting the chapters, like @DNSB has done, is something I generally do. For a book like this, I would assume each chapter started on a new page in the original paper version, so splitting it won't harm anything. And produces a book that works better.
|
No I didn't understand in the beginning, so the explanation was necessary. Sorry, communicating with emojis is complicated...
Regarding the book internals I have a similar policy too, with the only difference that if I don't like a file I try to find a better version. Sometimes you can't though and you must work on the bad version. I agree that having a file per chapteris the best thing, no problems with ToC and the book loads faster as the files are tiny.
Quote:
|
From a comment you made, I realised the problem was when the destination was not near the top of the book. I was able to test and prove this didn't work in the calibre viewer and the editor preview. I assume this is a bug, but, I honestly don't know what the ebook specs say about this.
|
About this I think I'll open a bug in calibre, after taking a look at the epub specs. I already verified that it happens with EPUB3 and AZW3 too, so there's that.