BUG: Large Text search misses entry in Tozer Topical Reader
This thread was in the Suggestions forum so it was probably missed, and I just checked and it still fails:
A search of Large Text in Tozer Topical Reader for Forgiveness fails to find #1028, while for example Regret is found.
See thread for discussion, but it's pretty easy to duplicate. There may be other problems with the Search fields in this resource.
Comments
-
I am finding that this is also true with Vyrso titles
Dell, studio XPS 7100, Ram 8GB, 64 - bit Operating System, AMD Phenom(mt) IIX6 1055T Processor 2.80 GHZ
0 -
Ted Hans said:
I am finding that this is also true with Vyrso titles
I didn't think Vyrso titles had search fields like Large Text, do they?
0 -
Ted Hans said:
I am finding that this is also true with Vyrso titles
Logos have no control over Vyrso ePub's, which are primarily intended for reading!.See http://community.logos.com/forums/p/35348/266888.aspx#266888
Dave
===Windows 11 & Android 13
0 -
Dominick Sela said:
I didn't think Vyrso titles had search fields like Large Text, do they?
Large Text is created by the Indexer, based on font size, so it may be created for Vyrso books. You would have to check the Information page.
Dave
===Windows 11 & Android 13
0 -
It appears that it's failing to find the hits that are at the end of the headings in that book. In addition to the one Dominick cited, a Search of 'unsaved' fails to find the instance at the end of the #1029 heading, but does find it in the middle of the #1030 heading (and others). I will report this bug. Thanks.
Edit: I should add that the problem didn't occur when I checked several other topical resources.
0 -
Dave Hooton said:Dominick Sela said:
I didn't think Vyrso titles had search fields like Large Text, do they?
Large Text is created by the Indexer, based on font size, so it may be created for Vyrso books. You would have to check the Information page.
Okay this is confusing. The search field has Large Text but are you suggesting that it is there for nothing? Pardon my ignorance but what would be the point of that?
Dell, studio XPS 7100, Ram 8GB, 64 - bit Operating System, AMD Phenom(mt) IIX6 1055T Processor 2.80 GHZ
0 -
Ted Hans said:
Okay this is confusing. The search field has Large Text but are you suggesting that it is there for nothing?
It means that there is Large Text, but the eye cannot detect instances that fail the criteria for Large Text; the source is not uniform in its application of font size to what appears to be "headings".
Dave
===Windows 11 & Android 13
0 -
Dave Hooton said:
It means that there is Large Text, but the eye cannot detect instances that fail the criteria for Large Text; the source is not uniform in its application of font size to what appears to be "headings".
Thanks Dave for the response. I will pretend that i have understood what you have written, what you mean[:$].
Dell, studio XPS 7100, Ram 8GB, 64 - bit Operating System, AMD Phenom(mt) IIX6 1055T Processor 2.80 GHZ
0 -
Ted Hans said:Dave Hooton said:
It means that there is Large Text, but the eye cannot detect instances that fail the criteria for Large Text; the source is not uniform in its application of font size to what appears to be "headings".
Thanks Dave for the response. I will pretend that i have understood what you have written, what you mean.
If it helps to make it a bit more clear, I was able to get a Large Text search hit for 'Apologetic' in the Section I heading "The Apologetic Task" but not in what appears to be large text below it, "The Task of Apologetics" (with "Match all word forms" selected). This is most likely due to the format of the source document, but I am getting clarification on that.
0 -
Melissa Snyder said:
If it helps to make it a bit more clear, I was able to get a Large Text search hit for 'Apologetic' in the Section I heading "The Apologetic Task" but not in what appears to be large text below it, "The Task of Apologetics" (with "Match all word forms" selected). This is most likely due to the format of the source document, but I am getting clarification on that.
Thanks Melissa, i get it now. What is strange is that on a few Vyrso books i am getting both result for Large Text.
Melissa Snyder said:This is most likely due to the format of the source document, but I am getting clarification on that.
Please do get some clarification on this. It will be helpful not only to me but to others.
Blessings
Dell, studio XPS 7100, Ram 8GB, 64 - bit Operating System, AMD Phenom(mt) IIX6 1055T Processor 2.80 GHZ
0 -
This has been fixed, in Beta 8 I believe, and will be added to the final compiled list of 4.5 release notes.
0 -
Tonya J Ross said:
This has been fixed, in Beta 8 I believe
Tonya is referring to 4.5 Beta 8 which has yet to be released. I cannot test this in Beta 10 (latest beta) as I don't have any Vyrso books (nor Tozer).
Dave
===Windows 11 & Android 13
0 -
Dave Hooton said:
I cannot test this in Beta 10 (latest beta) as I don't have any Vyrso books
But you could have such - even for free (and not all Vyrso books are Amish romances or self-help).
Have joy in the Lord!
0 -
Dave
===Windows 11 & Android 13
0 -
Dave Hooton said:
I took it hook, line & sinker - guess that makes me a Vyrso fan-boy? But then again it maybe just shows my careless posting, while others bit their tongues (or fingers) for ten minutes after your steilvorlage (deep forward pass in soccer)...
[:)]
Have joy in the Lord!
0 -
-
Tonya J Ross said:
This has been fixed, in Beta 8 I believe, and will be added to the final compiled list of 4.5 release notes.
Many thanks Tonya
Dell, studio XPS 7100, Ram 8GB, 64 - bit Operating System, AMD Phenom(mt) IIX6 1055T Processor 2.80 GHZ
0 -
Ted said:Tonya J Ross said:
This has been fixed, in Beta 8 I believe, and will be added to the final compiled list of 4.5 release notes.
Did you note the veiled hint?
Dave
===Windows 11 & Android 13
0 -
NewbieMick said:
while others bit their tongues (or fingers) for ten minutes after your steilvorlage (deep forward pass in soccer)...
I hope it didn't catch you offside[:)]
Dave
===Windows 11 & Android 13
0 -
Dell, studio XPS 7100, Ram 8GB, 64 - bit Operating System, AMD Phenom(mt) IIX6 1055T Processor 2.80 GHZ
0 -
Thank you, I've written up a case for the Large Text search and sent it to our Development department.
0 -
Kevin Byford said:
Thank you, I've written up a case for the Large Text search and sent it to our Development department.
Turns out this is working fine - if you click on the Blue link it will take you to the top of the Chapter; if you click on the highlighted search terms in the results (Forgive, Worship, Morality) it should take you to the exact spot in the resource where that term exists. Is that working properly for you?
0 -
Kevin Byford said:
Turns out this is working fine - if you click on the Blue link it will take you to the top of the Chapter; if you click on the highlighted search terms in the results (Forgive, Worship, Morality) it should take you to the exact spot in the resource where that term exists. Is that working properly for you?
Thanks, verified using Logos 4.5 Beta 11.
Also learned to look carefully since one Large Text search result is a Book Title in a footnote.
Keep Smiling [:)]
0 -
Melissa Snyder said:
It appears that it's failing to find the hits that are at the end of the headings in that book. In addition to the one Dominick cited, a Search of 'unsaved' fails to find the instance at the end of the #1029 heading, but does find it in the middle of the #1030 heading (and others). I will report this bug. Thanks.
Edit: I should add that the problem didn't occur when I checked several other topical resources.
Melissa and Tonya, this still appears to fail in 4.5 Was this fixed, it appears someone said it would be? (the origianl post where in Large Text for Tozer Topical Reader #1028 is not found)
0 -
Dominick Sela said:
Melissa and Tonya, this still appears to fail in 4.5 Was this fixed, it appears someone said it would be? (the origianl post where in Large Text for Tozer Topical Reader #1028 is not found)
Unfortunately, the fix doesn't take effect until affected resources are reindexed. I don't think the Tozer resource has been updated recently, so it probably hasn't been reindexed automatically. You will need to "rebuild index" to fix the Large Text searching. (I thought we had posted this limitation in the thread, but I can't find it now. I will update the release notes; sorry for the incomplete documentation on this fix.)
0 -
That's fine and no problem, thanks Bradley for the update and I am glad you were able to get this fix in!
0 -
Bradley Grainger said:
Unfortunately, the fix doesn't take effect until affected resources are reindexed. I don't think the Tozer resource has been updated recently, so it probably hasn't been reindexed automatically. You will need to "rebuild index" to fix the Large Text searching. (I thought we had posted this limitation in the thread, but I can't find it now. I will update the release notes; sorry for the incomplete documentation on this fix.)
I am hoping this also goes for Vyrso titles as well?
Dell, studio XPS 7100, Ram 8GB, 64 - bit Operating System, AMD Phenom(mt) IIX6 1055T Processor 2.80 GHZ
0