Can't get Psa 31.9-16 to point to the correct reference after typing in notes
If I type Psa 31 and add a space then click on it, it brings me to the top of the psalm including superscription as expected.
Type Psa 31.1 and it goes to 1
Type Psa 31.9 and it goes to 9
Type Psa 31.9-16 (as in today's reading for the daily RCL) and it goes to 32.9
I've reproduced it twice and don't understand the problem
Using windows 10, Logos 6.10 SR-2 with NLT as default Bible
Comments
-
Scott Groethe said:
If I type Psa 36 and add a space then click on it, it brings me to the top of the psalm including superscription as expected.
Type Psa 36.1 and it goes to 1
Type Psa 36.9 and it goes to 9
Type Psa 36.9-16 (as in today's reading for the daily RCL) and it goes to 32.9
I've reproduced it twice and don't understand the problem
Psa 36 only has twelve verses, it seems RCL Daily reads Psa 31.9-16 today
Have joy in the Lord!
0 -
Sorry, mistyped it in the body of the text, but the problem, yes, it's there in Psa 31
0 -
What translation are you using? It sounds like a Masoretic vs. LXX issue
Orthodox Bishop Alfeyev: "To be a theologian means to have experience of a personal encounter with God through prayer and worship."; Orthodox proverb: "We know where the Church is, we do not know where it is not."
0 -
NLT
0 -
I can't recreate your issue. Sorry
Orthodox Bishop Alfeyev: "To be a theologian means to have experience of a personal encounter with God through prayer and worship."; Orthodox proverb: "We know where the Church is, we do not know where it is not."
0 -
Logos is still booting up so I have to wait to try. I'm going to try on a Mac this time. Thanks for taking the time.
0 -
I just did it again, Logos 6 on a Mac this time, last time was on a PC
Typed Psa 31 hovering and clicking went to the top of the psalm incl superscription
Psa 31.1 to verse 1
Psa 31.9 to verse 9
Psa 31.9-16, it went to verse 9 but in Psa 32
total headscratcher
0 -
Because there is a new NLT release, I believe you ... I just wish someone would confirm they can recreate it. I'll try once more but my index is a bit of a mess ... from other issues.
Orthodox Bishop Alfeyev: "To be a theologian means to have experience of a personal encounter with God through prayer and worship."; Orthodox proverb: "We know where the Church is, we do not know where it is not."
0 -
I switched to the LEB and it worked as it should - so you're right about it being an NLT issue -thanks a lot
My NLT is 2013 6th ed.
0 -
Tyndale House Publishers. Holy Bible: New Living Translation. Carol Stream, IL: Tyndale House Publishers, 2013.
from the bottom of the information panel
LLS:1.0.171 2016-02-23T23:04:42Z NLT.logos4
RVI:NLTNT 2016-02-23T22:24:07Z NLTNT.lbsrvi
RVI:NLTOT 2016-02-23T22:24:07Z NLTOT.lbsrviI am running the beta version ...we need someone who is on the recent release to check ...
Orthodox Bishop Alfeyev: "To be a theologian means to have experience of a personal encounter with God through prayer and worship."; Orthodox proverb: "We know where the Church is, we do not know where it is not."
0 -
MJ. Smith said:
Because there is a new NLT release, I believe you ... I just wish someone would confirm they can recreate it
When I enter Psa 31:9-16 and hover my mouse over the "9" it shows a link to Ps 32:9 "via" the LXX mapping
If I hover my mouse over the "16" (recognising there are only 11 verses in Ps 32) I get a link to Ps 31
I get the same results with NIV or LEB as my highest prioritised Bible so it is not an NLT-specific issue
This is on Windows 10 running Logos 6.11 beta 2
0 -
That looks like an error in the verse mapping ... we need to make sure Faithlife sees this bug.
Orthodox Bishop Alfeyev: "To be a theologian means to have experience of a personal encounter with God through prayer and worship."; Orthodox proverb: "We know where the Church is, we do not know where it is not."
0 -
Mine is ok now, but I'm telling you it was giving me the wrong Psalm on two platforms today. Perhaps switching the default Bible to LEB then back to NLT did the trick, not a programmer so no idea.
But I try not to post problems unless I have them twice. This was not the first time that the NLT in a note pointed to the wrong target. But I hope this is all cleared up. Thanks for your input.
0 -
The problem appears to be that Notes is using the wrong Bible datatype when you use a period to separate the chapter and the verse. If you use a colon to separate the chapter and the verse, then all is well.
<edit>I mispoke. The issue is not colons and not periods. It seems erratic because second half of the link works OK, and the first half is broken. So depending on where you hover will depend on whether you see the error. See my bug report for more details.</edit>
Now that we've understood the problem, I'll type up a bug report in the beta forum. I'll link back here when I'm done.
This is my personal Faithlife account. On 1 March 2022, I started working for Faithlife, and have a new 'official' user account. Posts on this account shouldn't be taken as official Faithlife views!
0 -
Mark Barnes said:
The problem appears to be that Notes is using the wrong Bible datatype when you use a period to separate the chapter and the verse. If you use a colon to separate the chapter and the verse, then all is well.
Mark - that doesn't seem to be consistent with this
0 -
Mark, I've been doing these notes for a few years, thousands of them in a number of note files, always with a period. I use NLT every day. It works 99.9 percent of the time, but a couple of times it has pointed to the wrong location.
Switched to LEB as default Bible, then back to NLT and now no problem.0 -
Scott Groethe said:
but a couple of times it has pointed to the wrong location.
Scott
are you seeing what I am seeing (illustrated above) that you get different results depending on where you hover your cursor (irrespective of the Bible translation)?
0 -
No one here probably believes me but I had this problem a few hours ago, typed various lines then hovered or clicked, did it on Windows Logos and then Mac Logos and it was the same problem, Psa 31.9-16 pointed to Psa 32.9ff. But it is ok now. I should probably take a screenshot next time.
0 -
Bug duly reported: 6.11 beta 2: Notes uses the wrong Bible datatype with some Bible references
This is my personal Faithlife account. On 1 March 2022, I started working for Faithlife, and have a new 'official' user account. Posts on this account shouldn't be taken as official Faithlife views!
0 -
Mark isn't this an overreaction? I don't know the system for sending bugs but did you read where I said that 99.9% of the time there is no problem, I use periods every day in different notes files for thousands of notes. Not being a geek and computer head, I thought maybe it was a Psa 31-32 problem in the NLT text.
0 -
Scott Groethe said:
No one here probably believes me but I had this problem a few hours ago, typed various lines then hovered or clicked, did it on Windows Logos and then Mac Logos and it was the same problem, Psa 31.9-16 pointed to Psa 32.9ff. But it is ok now. I should probably take a screenshot next time.
I believe you. I bet it's still a problem for you. When I try and reproduce it, if I hover over the "-16" it's correct, but if I hover over the "Psa 31:9" it's wrong. That confused me at first!
I've taken screenshots in my bug post (linked above).
This is my personal Faithlife account. On 1 March 2022, I started working for Faithlife, and have a new 'official' user account. Posts on this account shouldn't be taken as official Faithlife views!
0 -
Scott Groethe said:
Mark isn't this an overreaction? I don't know the system for sending bugs but did you read where I said that 99.9% of the time there is no problem, I use periods every day in different notes files for thousands of notes. Not being a geek and computer head, I thought maybe it was a Psa 31-32 problem in the NLT text.
It's not a problem with the NLT, because I can reproduce it in any version. That probably means it's not a problem with verse mapping either, but a bug in how references are parsed with the Notes tool.
It's good for Faithlife to be aware of all bugs, even if they're very rare. But it will of course be for them to prioritise what is fixed. In other words it's never an over-reaction to report a minor bug, but it might be an over-reaction to insist that they fix it.
This is my personal Faithlife account. On 1 March 2022, I started working for Faithlife, and have a new 'official' user account. Posts on this account shouldn't be taken as official Faithlife views!
0 -
Scott Groethe said:
Mark, I've been doing these notes for a few years, thousands of them in a number of note files, always with a period.
I was wrong about the period causing the problems. And I think you're wrong about the problem having gone away now ;-). It seems erratic because second half of the link works OK, and the first half is broken. So depending on where you hover will depend on whether you see the error. See my bug report for more details.
This is my personal Faithlife account. On 1 March 2022, I started working for Faithlife, and have a new 'official' user account. Posts on this account shouldn't be taken as official Faithlife views!
0
