Bug 501154

Summary: Confusion with Page Numbers
Product: [Applications] okular Reporter: Peter <p.wibberley>
Component: generalAssignee: Okular developers <okular-devel>
Status: RESOLVED WORKSFORME    
Severity: minor CC: john.kizer, oliver.sander
Priority: NOR    
Version First Reported In: 24.12.2   
Target Milestone: ---   
Platform: Neon   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:
Attachments: Screenshot of Okular Page Numbering Confusion

Description Peter 2025-03-06 18:25:44 UTC
Created attachment 179187 [details]
Screenshot of Okular Page Numbering Confusion

SUMMARY

The numbering of pages in Okular is ambiguous and confusing.  This seems to arise when a document's pages are not numbered contiguously. i.e. in simple numerical order (beginning with "A", "B", etc.).  This creates confusion, for example, as to what numbers should be used to print specific pages.    

STEPS TO REPRODUCE
1. Open document with non-contiguous page numbering  
2. 
3. 

OBSERVED RESULT
See attached screenshot.  Page number is shown as both "74" and "76 of 152".

EXPECTED RESULT
Not clear why it's necessary to have "74" and "76" or why these are different.  Or could it be made clear what the distinction is between the meaning of the two numbers.   


SOFTWARE/OS VERSIONS
Windows: 
macOS: 
(available in the Info Center app, or by running `kinfo` in a terminal window)
Linux/KDE Plasma: 
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION
Comment 1 Oliver Sander 2025-03-07 07:59:49 UTC
The pdf format does distinguish between physical and logical page numbers, are you sure you are not seeing that being used?

Otherwise, please attach a test document.
Comment 2 John Kizer 2025-03-21 18:37:48 UTC
Updating the status here as this one is pending confirmation and/or a test document from the reporter. Thanks!
Comment 3 Bug Janitor Service 2025-04-05 03:46:43 UTC
๐Ÿ›๐Ÿงน โš ๏ธ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME.

For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging.

Thank you for helping us make KDE software even better for everyone!
Comment 4 Bug Janitor Service 2025-04-20 03:47:22 UTC
๐Ÿ›๐Ÿงน This bug has been in NEEDSINFO status with no change for at least 30 days. Closing as RESOLVED WORKSFORME.