Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Current page number / Total number of pages #175

Closed
icher opened this issue Sep 25, 2019 · 8 comments
Closed

Current page number / Total number of pages #175

icher opened this issue Sep 25, 2019 · 8 comments
Labels
enhancement New feature or request

Comments

@icher
Copy link

icher commented Sep 25, 2019

Hi. I know it's e-book format and there're no pages, but it's really helps to estimate book size. Most of e-book readers can do that and these numbers depends on window geometry. May be optional would be a good idea.

@johnfactotum
Copy link
Owner

This issue is actually a duplicate of #122. But I guess I'll leave this open, since the other one is closed.

AFAIK, no one has figured out how to efficiently implement page numbers based on page geometry with Epub.js yet. See upstream issue: futurepress/epub.js#744 (the various solutions discussed there involves counting an arbitrary number of characters as a page, not based on window size)

Note that currently, to estimate book size in Foliate, you can hover over the reading progress slider and see a time estimate based on the number of characters in the book.

Also note that some books actually contains a pageList, which provides information on physical page numbers (from the printed editions). It might be possible to display that information as well.

@johnfactotum johnfactotum added the enhancement New feature or request label Sep 25, 2019
@icher
Copy link
Author

icher commented Sep 25, 2019

This issue is actually a duplicate of #122.

Sorry, I just forgot about search function :)

the various solutions discussed there involves counting an arbitrary number of characters as a page, not based on window size

Well, it's not bad solution in my opinion, any relevant number would be ok, I don't need precise numbers.

Note that currently, to estimate book size in Foliate, you can hover over the reading progress slider and see a time estimate based on the number of characters in the book.

Oh, it's really confusing actually, I thought these numbers calculated based on how fast I'm turning pages. I think pages (calculated by one of possible algorithms for epub.js) much better than hours.

@johnfactotum
Copy link
Owner

The master branch has a new popover that includes a "location" entry. Each "location" has 1024 characters (1024 characters per page is used by Adobe Digital Editions).

Screenshot:
image

@johnfactotum
Copy link
Owner

After b772e9c, current and total location is now shown at the bottom, along with current chapter name
image

The progress bar can be accessed by hovering over the bottom area or by clicking on the viewing area:
image

@digitalethics
Copy link

Better to link this the other way as the discussion concerning reading time and text complexity in Standard Ebooks is now closed. I think there were some meaningful ideas that could be considered for this issue.

@johnfactotum
Copy link
Owner

You mean #341 and #372? This issue is about page numbers, not reading time.

@digitalethics
Copy link

You mean #341 and #372? This issue is about page numbers, not reading time.

Ah, yes! Sorry, should have been linked to these two.

@johnfactotum
Copy link
Owner

Closing as "locations" is a serviceable substitute for page numbers. In the gtk4 branch it also supports real page numbers from Page Lists. Showing fake page numbers based on window geometry is not practicable nor planned.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants