Tagging problem in Hebrew of Psalm 122.1?
I've been looking at Psalm 122, and it seems there's a problem with verse 1 in Logos.
Clicking on any word should bring up a list of English translations under 'Translated' in the Information window, but all it has is the LXX (and only the Logos LXX). The rest of the Psalm brings up the usual multiple English translations as well as the Swete LXX.
I've tried BHW, BHS and LHB and all have the same result.
Do others have the same problem?
Comments
-
Do others have the same problem?
I see the same thing - but I can't explain why!
Hopefully someone more knowledgeable than I will be able to.
0 -
I can reproduce this problem and have filed a bug report.
0 -
A quick reminder here. Verse 1 may mean either the heading (otherwise known as verse 0) or the first portion of the psalm itself.
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 -
Given the Bibles mentioned in the OP, I was assuming Hebrew versification.
0 -
I've been looking at Psalm 122, and it seems there's a problem with verse 1 in Logos.
Clicking on any word should bring up a list of English translations under 'Translated' in the Information window, but all it has is the LXX (and only the Logos LXX). The rest of the Psalm brings up the usual multiple English translations as well as the Swete LXX.
I've tried BHW, BHS and LHB and all have the same result.
Do others have the same problem?
I see that Bradley has answered you, but I don't understand. When I click on any word it brings up HALOT.
george
gfsomselיְמֵי־שְׁנוֹתֵינוּ בָהֶם שִׁבְעִים שָׁנָה וְאִם בִּגְבוּרֹת שְׁמוֹנִים שָׁנָה וְרָהְבָּם עָמָל וָאָוֶן
0 -
This will be fixed in 5.2a.
0 -
Thanks Bradley! Yes, Hebrew versification.
George, I think the default setting is for it to appear on mouse-over rather than click - either way, look at what comes up in the information pane.
0 -
This will be fixed in 5.2a.
This will be fixed in 5.2a Beta 4.
0