Bug 398771 - EPub backend: changing default font size doesn't update the page number
Summary: EPub backend: changing default font size doesn't update the page number
Status: RESOLVED DUPLICATE of bug 384070
Alias: None
Product: okular
Classification: Applications
Component: EPub backend (show other bugs)
Version: 1.5.1
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: Okular developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-09-17 19:14 UTC by Neviril
Modified: 2018-10-04 17:29 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Neviril 2018-09-17 19:14:27 UTC
=Background information=
Often, I need to read EPub ebooks a few meters away from my monitor and it is helpful for this to increase the default font size and type (on my configuration by default it's "Noto Sans, 10") to make text more easily readable.

=Issue encountered=
I found that changing the font size and type in EPub backend options results in Okular not updating the page number. Practically speaking, if an EPub Ebook has a 200 page count and I increase the font size, text appears to be reflowed correctly, but the page count would still remain 200. The most immediate issue is that the book gets clipped, meaning that the end could not be read if not by decreasing font size again.

Conversely, when decreasing the font size, blank pages result at the end of the document, although this is more than an annoyance than a usage-breaking bug.

=Additional notes=
Closing/reopening Okular and/or the document does not seem to solve the issue.
I observed this issue with different EPub documents.

=Backend information=
Version 0.2.3
KDE Frameworks 5.49.0
Qt 5.11.1 (built against 5.11.1)
The xcb windowing system
Comment 1 Christoph Feck 2018-10-03 21:26:51 UTC
Document generators currently cannot inform the Okular core of a changed page count. It might be needed to reload the document.
Comment 2 Albert Astals Cid 2018-10-04 17:29:42 UTC
This is a duplicate

*** This bug has been marked as a duplicate of bug 384070 ***