Quote:
Originally Posted by skillachie
Re: book size it is useful for some readers especially those with comic books or very large PDFs. They need to see how much and which books are using up space on their device so they determine what to remove from the device and leave on the cloud.
Give me some credit man  . We have already implemented a few items you suggested. If after exploring further we do not plan to implement it then I will let you know for sure. Currently it is just an item to explore, we have several other tasks ahead before it gets prioritized. As you have seen we try to implement what is requested mostly first based on feedback.
The job to be done for your request for ADE Page number is that you would like to be able to tell how long a book is to try to estimate the time and effort . This can be achieved in multiple ways including:
- Estimated Time to Read & Time Remaining ( Using word count)
- Providing the concept of a physical page number
Estimated Time to Read & Time Remaining derived from number of words
This was already planned and will come before physical page numbering concept:
Concept of a Physical Page
There are different ways to do this and we will likely support the page numbering that is EPUB3 compliant. EPUBs are starting to be created using this type of number.
This would still achieve the same job.
Now the other way would be to support ADE Based Page numbering or simply use ADE Based Page numbering as a fall back approach for when page-list are not present.
This is yet to be decided. But I heard the feedback and will get back once we are closer |
ePub3 page numbers are mostly useless. They do not work with RMSDK on a Kobo Reader. Most programs that read ePub won't work with them either. ADE/RMSDK is the number 1 program used for reading ePub and ADE page numbers should be implemented first. It's OK to add other page numbers as an option.