Bug v22.0: Logos 9 Search cannot be converted
1. This query works in Logos 9 but cannot be converted in Verbum 22.0:-
(purpose,reason,goal) WITHIN 5 WORDS (cross,death,crucifixion) WITHIN 5 WORDS (Jesus,Christ,Lord)
- there is an error associated with the first term.
(purpose,reason,goal) WITHIN 5 WORDS (cross,death,crucifixion) was accepted but produced no results.
.
2. This Morph Search in Favorites works in Logos 9: [match dagesh, accents] hebrew:מֶֽלֶךְ but it comes across as an "Untitled Morph Query" in Verbum 22.0
When manually input the query is converted!
Dave
===
Windows 11 & Android 13
Comments
-
The first query was also accepted for me in the Books tab but produced no results. I didn't get an error, but I didn't get any results either.
0 -
>1. This query works in Logos 9 but cannot be converted in Verbum 22.0:-
When you say cannot be converted. Can you elaborate on that? Our assumption is you are creating a shortcut that works in L9 but doesn't convert to L10 syntax? If so, that is a bug, but just want to confirm our understanding is correct.#2 is also an issue we can bring up and investigate. I'll work on a repro and get a case going.
0 -
>1. This query works in Logos 9 but cannot be converted in Verbum 22.0:-
When you say cannot be converted. Can you elaborate on that?I just realised that I had an extraneous character after the last closing ).
If I paste (purpose,reason,goal) WITHIN 5 WORDS (cross,death,crucifixion) WITHIN 5 WORDS (Jesus,Christ,Lord) into a Books Search it produces no results. But if I insert a space after any comma, I get an error.
The weird thing is that a history entry from yesterday (when I first tried it) converts it and runs it immediately:-
term:(purpose OR reason OR goal) WITHIN 5 WORDS term:(cross OR death OR crucifixion) WITHIN 5 WORDS term:(Jesus OR Christ OR Lord)
But the most recent history entry (today) does not convert it.
Dave
===Windows 11 & Android 13
0 -
If I paste (purpose,reason,goal) WITHIN 5 WORDS (cross,death,crucifixion) WITHIN 5 WORDS (Jesus,Christ,Lord) into a Books Search it produces no results. But if I insert a space after any comma, I get an error.
The weird thing is that a history entry from yesterday (when I first tried it) converts it and runs it immediately:-
term:(purpose OR reason OR goal) WITHIN 5 WORDS term:(cross OR death OR crucifixion) WITHIN 5 WORDS term:(Jesus OR Christ OR Lord)
But the most recent history entry (today) does not convert it.
I suspect that the problem is that the lack of L9 specific syntax means the query is not recognized as being from L9 and that's why it's not converted. I'm not sure there's much we can do about that, but I'll ask.
Does the history entry originate from L9? If so, that would explain why it works from there.
0 -
the problem is that the lack of L9 specific syntax
Aren't the commas L9 specific?
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 suspect that the problem is that the lack of L9 specific syntax means the query is not recognized as being from L9
The original query was converted in Mac OS. See https://community.logos.com/forums/t/213201.aspx
(purpose,reason,goal) is L9 specific, also (Jesus,death,purpose) both of which produce no results in Verbum 22.0. But (Jesus,death, purpose) will produce an error.
Does the history entry originate from L9? If so, that would explain why it works from there.
I can't know for sure, but it still begs the question as to why my paste of the query fails.
Dave
===Windows 11 & Android 13
0 -
I can't know for sure, but it still begs the question as to why my paste of the query fails.
In L10, we only attempt to convert from L9 syntax if either (a) we know it's L9 because it synced from there, or (b) the search doesn't parse correctly.
In this case, the search query does parse correctly in L10, so it doesn't get converted.
0 -
In this case, the search query does parse correctly in L10
OK, I proved that (lord,jesus, christ) will parse correctly after the search is saved to Favorites in L9. But pasting it in L10 produces an error that is not obviously corrected by deleting the space when comma is treated as AND. The same applies to (lord,jesus$ christ).
Dave
===Windows 11 & Android 13
0
