Quote:
Originally Posted by daniel1591
hello, I restart this discussion because the answer does not seem to be satisfactory.
Indeed, why is it not possible for a developer to create a patch that would obtain a correct pagination in relation to the size of the characters?
|
PAtching to replace a character or two in different places works. Or to skip a bit of code. But, what you want is completely new function that somehow has to be added to the executables and called. It might be possible, but it is probably an order or two of magnitude more difficult.
Quote:
Pagination by chapter does not interest me. I want to know the number of pages remaining to read on the whole ebook (epub or kepub).
Knowing that mobi files are very badly managed, I only load kepub with template.
Why an alternative reader like koreader handles this question well whereas niquel can not do it? This is the only negative point of the latter.
Koreader is less friendly and the translation is incomplete which explains why I do not keep it
|
As I stated, this is a
design decision. Kobo decided to do it this way. Koreader decided to do it a different way. Which is correct is up for debate. And if you want the debate, go to the general discussion forum and make
your statement: "The only correct page numbering system is counting screens for the whole book." I won't be joining in because I have no idea what the correct page numbering system is, but I do know what works for me. But, I will be watching the fun with
If you think that the way Kobo is doing it is wrong, tell Kobo. They do actually listen and do make changes. But, whether they agree with you is another matter completely. The alternative is to use Koreader. If it works the way you want it to work, then why not use it?