Page numbers in Kindle popup

[samuelclay]

Page X of Y. This is more of a server-side change than client, but apart from turning it on, I had to handle compatibility with regular readables.

Note that we don't show a page number when the server returns locations instead of pages, which happens on more EPUBs than I would have thought. Kindle is stricter about EPUB page numbers, so instead we could treat locations like Sol EPUB bytes and divide them by 1000 and get a ~Sol page number. WDYT?

[johnboiles]

instead we could treat locations like Sol EPUB bytes and divide them by 1000 and get a ~Sol page number. WDYT

To me it depends on whether Kindle locations are consistent. Does it seem to roughly correlate with the amount of text?

[samuelclay]

To me it depends on whether Kindle locations are consistent. Does it seem to roughly correlate with the amount of text?

It's pretty close. Here's the same epub in both our format and kindle. Note that the start/end bytes are from the .txt extraction from the .epub, which is a larger number (and to the right). We use the epub byte offset for page numbers, but since we aren't just / 1000 the byte count to get a page count, we can either show Location 953 of 13959 or Page 95 of 1395 (or whatever the devisor we decide)

And at the end, it becomes Location 13422 of 13959 vs Page 1210 of 1271:

[samuelclay]

To be clear (since there's a lot to parse above), I propose we don't show Location but instead convert to our Pages.

For the "Rich Men" article, native EPUB would show Page 1210 of 1271 and Kindle would show Page 1342 of 1395.

Or should it say Location and not convert at all? The full Location 13422 of 13959

[samuelclay]

I'm going to punt on handling location and just get pages working for books that support it.

[samuelclay]

Servers already giving these page numbers, and since we're now public, this gets merged.