Way to make reading statistics use reference/stable pages instead of dynamic ones?

ilikelilies · 01-15-2026, 03:56 PM

I personally really prefer reference page numbers to dynamic page numbers.

For me, dynamic ones make no sense, since if I change the font size or even just the font, I have to look at another framework to understand where in the book I am. It makes even less sense, in my opinion, for reading statistics to use dynamic page numbers. How am I supposed to have any stable notion of something I can actually study with statistical validity if the statistics constantly change with the font size etc.?

But this is not the place for my rants, and I understand that some people may prefer dynamic page numbers. I just wanted to know how to make reading statistics use reference page numbers, since that's pretty important to me.

So I looked on KOReader's github page and, apparently, this was already supposed to be tackled in 2025.10, which is the version I'm running. Looking at the changelog, if I'm interpreting it correctly then this was already supposed to be implemented in #14388 and a subsequent fix in #14416 , both of which were merged. I'm not completely sure whether those prs are actually supposed to implement that, I'm just basing this on the title of #14388 . But then apparently all that was reverted in #14435 because of some issues, if I'm keeping track of it correctly. There was also a previous #13385 , but that shouldn't matter that much as that's what #14388 was based on.

So is that it? This issue is still open, and it doesn't seem like there's been much progress. Is there any actually stable way to do this at this moment? The user of #13385 made this userpatch , but I'm dubious as to whether it will be appropriate and up to date seeing as #14435 (which is what it's based off of) was never merged.

Can anyone confirm if the patch works? Does anyone know if there's an alternative method for making this work? Or is it simply a stagnated issue that the devs just aren't interested in looking into at the moment?

Thank you for your time :)

Frenzie · 01-16-2026, 07:38 AM

I think the relevant issue and comment is https://github.com/koreader/koreader...ent-3476633521

Quote:

No plans at the moment.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Use Stable Pages Feature on Previously Opened Books?	JimmXinu	KOReader	4	11-05-2025 04:23 PM
reference pages everywhere?	solane	KOReader	0	02-28-2025 04:23 PM
Way to tell which books have reference pages in advance?	mallomar	KOReader	4	02-16-2025 12:42 AM
Reference Pages	Amon_Re	KOReader	1	04-16-2023 12:56 PM
make statistics with Calibre	sirius911	Library Management	6	01-05-2012 01:48 PM

01-15-2026, 03:56 PM	#1
ilikelilies linux user Posts: 7 Karma: 10 Join Date: Jan 2026 Device: Kobo Libra 2	Way to make reading statistics use reference/stable pages instead of dynamic ones? I personally really prefer reference page numbers to dynamic page numbers. For me, dynamic ones make no sense, since if I change the font size or even just the font, I have to look at another framework to understand where in the book I am. It makes even less sense, in my opinion, for reading statistics to use dynamic page numbers. How am I supposed to have any stable notion of something I can actually study with statistical validity if the statistics constantly change with the font size etc.? But this is not the place for my rants, and I understand that some people may prefer dynamic page numbers. I just wanted to know how to make reading statistics use reference page numbers, since that's pretty important to me. So I looked on KOReader's github page and, apparently, this was already supposed to be tackled in 2025.10, which is the version I'm running. Looking at the changelog, if I'm interpreting it correctly then this was already supposed to be implemented in #14388 and a subsequent fix in #14416 , both of which were merged. I'm not completely sure whether those prs are actually supposed to implement that, I'm just basing this on the title of #14388 . But then apparently all that was reverted in #14435 because of some issues, if I'm keeping track of it correctly. There was also a previous #13385 , but that shouldn't matter that much as that's what #14388 was based on. So is that it? This issue is still open, and it doesn't seem like there's been much progress. Is there any actually stable way to do this at this moment? The user of #13385 made this userpatch , but I'm dubious as to whether it will be appropriate and up to date seeing as #14435 (which is what it's based off of) was never merged. Can anyone confirm if the patch works? Does anyone know if there's an alternative method for making this work? Or is it simply a stagnated issue that the devs just aren't interested in looking into at the moment? Thank you for your time :)

Advert