BUG: Cmd-F doesn't work very well in the Catholic Lectionary

fgh

I hit Cmd-F, type a word and, if necessary, hit Enter. I get to

Only the word isn't there. It's an inch or two above:

Find more posts tagged with

Comments

fgh

Unfortunately, it's even worse than above:

2) The search result only shows up at all if I'm already under the right date. Otherwise the 'Find' feature behaves as if there's nothing to find. I noticed this yesterday as well, but I had such a large swap file at the time that I wanted to make sure before reporting it that it was a real issue, and not just caused by it taking so long that I gave up too early.

I presume this is another one of those issues that occur because the lectionary isn't a 'real' resource, but a kind of 'reading plan' fetching the actual text from somewhere else? What makes this one so tricky, though, is that you believe you've done a search and found nothing, but in reality you haven't actually done the search at all. And there's no way of knowing that.

3) I don't yet know if this is a repeatable bug or just a one time thing, but this morning when I opened my lectionary layout, the lectionary tab opened to where I last was (i e the passage in the OP), instead of to this mornings reading, where it was when I saved the layout. And, no, I can't possibly have forgotten to save, as the other tabs were in the right place.

Haven't managed to repeat it so far, though.

fgh

OK, now I've tested this in the Daf Yomi as well and found that it is a resource type issue, not a resource issue, and a very weird one at that, so let me rephrase things:

1) If the wanted word is found, the lectionary opens to the empty space below the text it's in -- which in the case of the Daf Yomi can be a very long way from where it actually is.

I chose an unusual word that occurs in the Gospel for both the Thursday of the 19th Week and St Stephen (same date, same Gospel) and typed it into the find box.
I scrolled to and put the focus in the first OT reading for St Stephen, and started the search. Except for issue 1) it found the word in the NT reading for the same day.
I then moved back to the OT reading for the Thursday, started the search again, and it found the word in the NT reading for that day.
I went on to the Assumption, did the same thing, and again it found the word in the Thursday reading.
I did the same thing for the Assumption Vigil and St M M Kolbe. Same result.
Then I jumped a few days back to St Clare -- and suddenly Logos can't find the word anymore.
Same thing if I change direction and try to go forward again. Suddenly it can't find the word from a position it easily found it from minutes earlier.

As long as I move backwards one step at the time Logos keeps finding the word, but as soon as I move direction or jump a day it's as if the word doesn't exist in the resource. I really hate the kind of bugs that makes you think you've performed a full and accurate search when you haven't!

But at least the fact that it can find things across text and date boundaries under some conditions ought to mean that it's a 'real' bug, and not something that can't possibly be fixed until the whole lectionary 'feature' is revamped.

Dylan Rondeau

1) If the wanted word is found, the lectionary opens to the empty space below the text it's in -- which in the case of the Daf Yomi can be a very long way from where it actually is.

I was able to reproduce this and have created a case for development.

As long as I move backwards one step at the time Logos keeps finding the word, but as soon as I move direction or jump a day it's as if the word doesn't exist in the resource.

I am unable to follow the steps on this. If this is still an issue, could you provide a specific search word and location for me to reproduce? I understand you're not finding words that are clearly there - but I'm having trouble following the mechanics of it.