Page Numbering (Bug?)
In Logos, I study theology books by taking notes in a different application, marking down the page number and pasting quotes of interest. That way I don't always have to open the resource again if I want to quote & cite it in something.
This month, I read the preview book, Sproul's Everyone's a Theologian, almost exclusively through the web app. Going back to my desktop and checking my quotes today, I notice that the page number I have recorded, which I took from the "Go" field in the web app while reading, is always +1 page numbers ahead of what the resource is showing in Logos desktop.
For example, this passage is shown as being on p. 30 in the web app:
Versus the orange page marker in the desktop app, showing page 29.
I have noticed this problem in other resource as well. Is this a bug or is there something I'm just not perceiving correctly? For casual reading this is not a problem, but for citation in formal writing it is a major issue.
I need this clarified so I can know how to proceed with occasional use of the web app. If all resources are consistently numbered +1 page, I can work around that BUT notify us if you ever fix it. If it's not consistent I'll have to double check every single citation I make from the web version against my desktop version, which somewhat defeats the purpose of having the former.
Someone from Logos, please advise.
[For the record, while I never used biblia.com that much, I had previously noticed this problem there too but didn't think much of it at the time.]
Comments
-
I had a similar experience recently with Learning to Study the Bible, between the iOS and desktop apps. I didn't think much of it until I saw your post.
0 -
I had a similar experience recently with Learning to Study the Bible, between the iOS and desktop apps. I didn't think much of it until I saw your post.
Ugh. I also use the Android app but have never thought to check it for this issue. Thankfully, at least for the example I have included above, it shows the same page number (29) as the desktop program. I wonder why this is?
0 -
For example, this passage is shown as being on p. 30 in the web app:
In fact, it's not:
however, If I read forward on the page and hit e.g. the down arrow of the scrollbar, the page will move one or two lines - I can still see the text from page 29 but the position of the text where I am at (at the bottom of the page) is actually on page 30:
If I hit the upward button of the scrollbar, again moving the display by two lines, but indicating to the app that I read on the top of the page, it shows page 29 again.
Have joy in the Lord!
0 -
In fact, it's not:
I see that if you type in p. 30, it takes you to the correct page (the beginning of the next chapter). However, that's not something someone normally does while reading through a resource.
Also, at least as I've been using it, the URL bar does not update as I scroll through pages while reading. (I might even be in a reading mode that doesn't show the address bar). I have to go with what is shown in the Go bar, which does update. I've checked about a dozen quotes I noted while reading, and consistently for every one, the page number I got from the Go bar is +1 to what the desktop program shows.
ETA: I see the address bar tracks the URL of the resource open in the left pane. I usually have a Bible open there and read other resources in the right. In any event, I shouldn't have to be looking at URL's to attempt to figure out page numbers while reading.
0 -
Sean,
forget about the URL and read my post again. I did not type the location, but left the resource in the desktop at p.29, opened it in the app and and it was at the same place in p.29
The point I think is that Logos displays one page, even if the information you have on screen is from two pages from the physical book. When you read it scrolling down, the location shown is the one from the bottom of the page, not the one from the top of the page.
Have joy in the Lord!
0 -
When you read it scrolling down, the location shown is the one from the bottom of the page, not the one from the top of the page.
Thanks, I see that now.
Bumping this in hope someone from FL will respond: given how the desktop and apps work, this is a rather unintuitive and awkward setup. What would be best would be if there could be some page number marker like that which can be turned on or off in the desktop version. Are there any plans for something like this? (Eventually--I know better than to ask "when".)
0 -
I'm going to have to return to my original position that the page numbering in the web app is too imprecise to rely on for formal citation.
1. Here is the pagination of the dedication (p. 5) and table of contents (p. 7) for The Unseen Realm on desktop:
.png)
-Here's the same pages in the web app. It all shows as page 5; if it were going by the line at the bottom of the screen, it should be displaying 7.
.png)
-I have to scroll down one more line before it does so:
.png)
2. This shot from the desktop shows where p. 8 begins, at Part 5 in the ToC:
.png)
-But the web app is showing that I'm already on p. 8 even before Part 5 shows at the bottom of the screen:
.png)
I'm not sure why it is so unreliable--perhaps it has something to do with the font size & how it calculates which page is at the bottom of the screen? I really don't have any more time to give over to trying to figure it out.
So, FaithLife, can you give any guidance on this? I understand the very important word for the web app--**BETA**--so I'm not expecting perfection here. Yet, this is still a fairly major issue--like a massive typo--that I would think should be fairly easy to fix. Are there any chances we might get a little orange rectangle thingy like we have on the desktop, seeing that the page # info is surely already in the files the web site renders? If not, is there any more reliable way that I can get page number info out of a book I'm reading on the web?
Thanks in advance for your response.
0 -
One more example:
Desktop, pages 9 & 11:
.png)
Web app shows it all as p. 9:
.png)
Until I scroll down one more line:
.png)
0 -
the page numbering in the web app is too imprecise to rely on for formal citation.
until someone from Faithlife answers, my personal view is that it simply wasn't designed with your use case in mind (and maybe there are much better ways existing or planned in the app to derive quotes than looking at this locator box - displaying the page info in the resource text would be one I could think of)
Have joy in the Lord!
0 -
When you read it scrolling down, the location shown is the one from the bottom of the page, not the one from the top of the page.
Thanks, I see that now.
Bumping this in hope someone from FL will respond: given how the desktop and apps work, this is a rather unintuitive and awkward setup. What would be best would be if there could be some page number marker like that which can be turned on or off in the desktop version. Are there any plans for something like this? (Eventually--I know better than to ask "when".)
We're working on bringing resource display in the web app up to full parity with the desktop, including more precise location tracking and visual filters, including page number markers. Some of these things may be available sooner than you'd think.
Although they're not available on the web app, have you considered using a Clipping document for collecting your interesting quotations?
David Mitchell
Development Lead
Faithlife0 -
When you read it scrolling down, the location shown is the one from the bottom of the page, not the one from the top of the page.
Thanks, I see that now.
Bumping this in hope someone from FL will respond: given how the desktop and apps work, this is a rather unintuitive and awkward setup. What would be best would be if there could be some page number marker like that which can be turned on or off in the desktop version. Are there any plans for something like this? (Eventually--I know better than to ask "when".)
We're working on bringing resource display in the web app up to full parity with the desktop, including more precise location tracking and visual filters, including page number markers. Some of these things may be available sooner than you'd think.
Although they're not available on the web app, have you considered using a Clipping document for collecting your interesting quotations?
Thanks, David. "Eventually" is good enough more me; I can work around it until then.
I have started using Clippings for some readings; it's a nice feature. For most of my notes I use Nota Bene's Orbis note-retrieval system. It's got all my notes since my post-grad days back when I was using Libronix, from dead-tree books as well as ebooks, so I doubt I'll migrate from it anytime soon.
0
