Updated reverse interlinears published

We've updated the reverse interlinears and published them for Logos 5.

. . .

It also enables "Alternate translations in Information"; however over a word in a reverse interlinear and get a quick snapshot (in the Information Panel) of how it's translated in other Bibles.

Something is off here. I first noticed it shortly after a huge download and thought I just needed to wait for indexing to finish. But now that indexing is done, I'm seeing the same thing. Note that I'm clicking on the word "faith" in Hebrews 11:1 in the NIV(84). (I have the information pane set to update on "Click" rather than "Hover" though results are the same either way.)

Results for other words sometimes seem worse. This is from clicking on "commend" in Heb.11:2 (NIV84)

Is there something I'm not understanding about how this is supposed to work?

https://community.logos.com/discussion/comment/404970#Comment_404970

Is there something I'm not understanding about how this is supposed to work?

No, this looks broken. (And I suppose it's possible that search results highlighting is also broken.)

It was working internally with the previous build of the resources, so I'm not sure what's wrong. We'll investigate.

https://community.logos.com/discussion/comment/404980#Comment_404980

I get the same results as Richard, so the problem's not isolated to him.

https://community.logos.com/discussion/comment/404980#Comment_404980

Is there something I'm not understanding about how this is supposed to work?

No, this looks broken. (And I suppose it's possible that search results highlighting is also broken.)

It was working internally with the previous build of the resources, so I'm not sure what's wrong. We'll investigate.

I'm also finding that searching lemmas in the NIV84 is broken.

Steps: Open NIV84 to Hebrews 11:1

Right-click on "faith"

From the right column choose: Lemma πίστις

From the left column choose: Search this resource

Results: 0 results (0.06 sec)

This seems isolated to the NIV84 as doing the same and choosing "Search all open resources" returns results for the LEB, NLT, NIV11, ESV, LGNTI, and Lex LXX Int.

If others are getting results doing a lemma search with the NIV84, maybe my NIV84 has a corrupt rev.int. index. If others aren't, maybe the problem is a bad NIV84 rev.int. file was put on the servers.

https://community.logos.com/discussion/comment/404990#Comment_404990

If others are getting results doing a lemma search with the NIV84, maybe my NIV84 has a corrupt rev.int. index.

I get results for that lemma search, but I still have the other problems you posted about.

https://community.logos.com/discussion/comment/404991#Comment_404991

I get results for that lemma search, but I still have the other problems you posted about.

Okay, I'll rebuild my Bible index and report back.

EDIT: That didn't work. Still 0 results when searching any (Greek) lemma in the NIV84. I'll have to try to hide, restart, unhide, restart and see if that works.

EDIT 2: That didn't work either. It appears that no searches that rely on the NIV84 rev.int. are working. They do work on the NIV11 rev.int. Searching the surface text from the right click menu works. Seems to me that the rev.int. or the index for this rev.int. is corrupt. Any other ideas?

JT (alabama24)

https://community.logos.com/discussion/comment/404994#Comment_404994

Bradley -

I noticed THIS USER has an issue that looks similar to the screen shots posted here… is it possible that he downloaded the bad RI info into L4?

EDIT: After looking at it more closely, I think it is unrelated. I have recommended that the user rebuilt his Bible index.

https://community.logos.com/discussion/comment/405042#Comment_405042

I noticed THIS USER has an issue that looks similar to the screen shots posted here… is it possible that he downloaded the bad RI info into L4?

EDIT: After looking at it more closely, I think it is unrelated. I have recommended that the user rebuilt his Bible index.

No, those are the classic symptoms of the search index being out-of-sync with the resource. Your advice to rebuild the Bible Index is spot on.

https://community.logos.com/discussion/comment/404990#Comment_404990

I'm also finding that searching lemmas in the NIV84 is broken.

This is still happening for me in L5b1. Any suggestions that I haven't tried yet?

(Note: I was gone all day in a denominational regional meeting and just got back to playing with this.)

https://community.logos.com/discussion/comment/405432#Comment_405432

I'm also finding that searching lemmas in the NIV84 is broken.

This is still happening for me in L5b1. Any suggestions that I haven't tried yet?

We're rebuilding all the reverse interlinears and will ship an update when they're complete (or as they're completed).

Graham Criddle

https://community.logos.com/discussion/comment/405435#Comment_405435

I'm also finding that searching lemmas in the NIV84 is broken.

This is still happening for me in L5b1. Any suggestions that I haven't tried yet?

We're rebuilding all the reverse interlinears and will ship an update when they're complete (or as they're completed).

Don't know if this will help or if you already have this covered but another example below:

This is the result of a syntax search for four consecutive verbs.

The search works fine but the highlighting in the NRSV is off and there are some extra words / letters being introduced in the NRSV text.

Graham

https://community.logos.com/discussion/comment/405435#Comment_405435

We're rebuilding all the reverse interlinears and will ship an update when they're complete (or as they're completed).

I have an outstanding download of 544 MB which would appear to be all the buggy RI's (which I refused) + something else. I would like only to receive useful downloads!

https://community.logos.com/discussion/comment/405435#Comment_405435

We're rebuilding all the reverse interlinears and will ship an update when they're complete (or as they're completed).

I just sent a typo report on the rev.int. for Heb.11:1 in both the NIV84 and NIV11. As long as you're rebuilding, you might as well get those changes in too.

[The typo report states that the word "confidence" and the phrase "what we hope for" have the underlying Greek text inverted. "Confidence" goes with ὑπόστασις, and "what is hoped for" goes with ἐλπιζομένων (not the other way around).]

Lawrence Rafferty

https://community.logos.com/discussion/comment/405747#Comment_405747

I just sent a typo report on the rev.int. for Heb.11:1 in both the NIV84 and NIV11. As long as you're rebuilding, you might as well get those changes in too.

Unfortunately the new builds were already well on their way. I passed on your typo report, so hopefully it will be fixed in the next release.

The good news is the updated reverse interlinears are available now.

https://community.logos.com/discussion/comment/405755#Comment_405755

The good news is the updated reverse interlinears are available now.

That just doubled my problem - see previous post - as the download is now 1.18 GB. How much of that is useful?

https://community.logos.com/discussion/comment/405756#Comment_405756

That just doubled my problem - see previous post - as the download is now 1.18 GB. How much of that is useful?

The Update Manager should have recognised that the previous RI downloads are now superseded, but it appears it may not have.

You could try "update resources" to force a full check, or you could shut down the app and delete your UpdateManager\Updates.db database to ensure that it "forgets" the previous downloads.

https://community.logos.com/discussion/comment/405755#Comment_405755

The good news is the updated reverse interlinears are available now.

The ESV still has problems:

JT (alabama24)

https://community.logos.com/discussion/comment/405800#Comment_405800

Todd - which passages are you using? I have not seen this since the update and index tonight.

https://community.logos.com/discussion/comment/405811#Comment_405811

Todd - which passages are you using? I have not seen this since the update and index tonight.

I think those examples were from clicking around in the first few chapters of 1Thess. But I see the problem everywhere.

Rebuilding my bible index now to see if it makes a difference.

JT (alabama24)

https://community.logos.com/discussion/comment/405814#Comment_405814

Rebuilding my bible index now to see if it makes a difference.

That would be my suggestion. Here are my results:

https://community.logos.com/discussion/comment/404990#Comment_404990

I'm also finding that searching lemmas in the NIV84 is broken.

Steps: Open NIV84 to Hebrews 11:1

Right-click on "faith"

From the right column choose: Lemma πίστις

From the left column choose: Search this resource

Results: 0 results (0.06 sec)

This seems isolated to the NIV84 as doing the same and choosing "Search all open resources" returns results for the LEB, NLT, NIV11, ESV, LGNTI, and Lex LXX Int.

If others are getting results doing a lemma search with the NIV84, maybe my NIV84 has a corrupt rev.int. index. If others aren't, maybe the problem is a bad NIV84 rev.int. file was put on the servers.

I'm still getting this. There is something broken, probably with just my system, but I'm not sure what to do next. I did find something very interesting and confusing that I'm posting here. The rev.int. lines up properly in the bottom panel, but not in the main panel.

Any suggestions on what's going on and how to fix it?

EDIT: Not sure why the text in the image looks blurry here, it looks crystal clear on my monitor.

https://community.logos.com/discussion/comment/405814#Comment_405814

Rebuilding my bible index now to see if it makes a difference.

Rebuilding the index didn't help--ESV's translated words are still messed up:

(from Eph 1:14)

https://community.logos.com/discussion/comment/405821#Comment_405821

EDIT: Not sure why the text in the image looks blurry here, it looks crystal clear on my monitor.

Don't have any suggestions on your problem, but the image is blurry because it gets resized by the forum software. If you click on it, it will show the original, which looks sharp to me.

Mark Smith

https://community.logos.com/discussion/comment/405821#Comment_405821

Rich, I am not getting the mess-up you have in the NIV84:

No idea what is causing your strange behavior.

You could try hiding the NIV84, close and reopen L5, then unhide it, close and reopen, and force a re-download of the resource. If that clears things up the resource was corrupted in some way. Doesn't explain how or why, however

Lawrence Rafferty

https://community.logos.com/discussion/comment/405800#Comment_405800

The ESV still has problems:

This is symptomatic of having a version of the reverse interlinear resource (*.lbsrvi) that does not correspond to the version of the Bible resource. Rebuilding the Bible index will not change this data, it is stored in the reverse interlinear resource. Updating your resources should resolve the problem. If the problem persists, we'll need to check which versions you do have downloaded. You should have

2012-10-12T16:52:28Z for ESV.logos4,
2012-10-11T20:40:31Z for ESVNT.lbsrvi
2012-10-12T01:08:38Z for ESVOT.lbsrvi

Lawrence Rafferty

https://community.logos.com/discussion/comment/405821#Comment_405821

I'm also finding that searching lemmas in the NIV84 is broken.

Steps: Open NIV84 to Hebrews 11:1

Right-click on "faith"

From the right column choose: Lemma πίστις

From the left column choose: Search this resource

Results: 0 results (0.06 sec)

This seems isolated to the NIV84 as doing the same and choosing "Search all open resources" returns results for the LEB, NLT, NIV11, ESV, LGNTI, and Lex LXX Int.

If others are getting results doing a lemma search with the NIV84, maybe my NIV84 has a corrupt rev.int. index. If others aren't, maybe the problem is a bad NIV84 rev.int. file was put on the servers.

I'm still getting this. There is something broken, probably with just my system, but I'm not sure what to do next. I did find something very interesting and confusing that I'm posting here. The rev.int. lines up properly in the bottom panel, but not in the main panel.

Any suggestions on what's going on and how to fix it?

EDIT: Not sure why the text in the image looks blurry here, it looks crystal clear on my monitor.

Richard, your NIV 84 problems also appear to be from having a version of the reverse interlinear that does not correspond to your version of the NIV 84. The indexer will not index a reverse interlinear with a Bible unless the version exactly matches what it is expecting, so that explains why you aren't getting lemma search results in NIV 84. Unfortunately only indexing has this protection—all of these other features are capable of trying to use an incompatible version. Updating your resources should fix the problem. You will need to rebuild your Bible index for searching reverse interlinear data in NIV 84. The versions you should have are

2012-10-12T17:14:23Z for NIV.logos4
2012-10-11T22:04:01Z for NIVNT.lbsrvi

Graham Criddle

https://community.logos.com/discussion/comment/405590#Comment_405590

This is the result of a syntax search for four consecutive verbs.

The search works fine but the highlighting in the NRSV is off and there are some extra words / letters being introduced in the NRSV text.

This works fine now after upgrading to B2 and the updated RIs (which didn't seem to involve a large download this time unless I missed it!)

Thanks, Graham

https://community.logos.com/discussion/comment/405763#Comment_405763

You could try "update resources" to force a full check,

Thanks, that reduced the download to 587.6 MB - now let's see if my holiday (mobile) broadband will cope with it.

https://community.logos.com/discussion/comment/405848#Comment_405848

You should have

2012-10-12T16:52:28Z for ESV.logos4,

I had 2012-08-08T21:30:18Z for ESV.logos4.

Update Resources caused a download, but the ESV wasn't changed when Logos restarted.

Checking the indexer log shows this:

2012-10-13 09:29:04.9583 7 Info ResourceManager Moving resource from 'C:\Users\Todd\AppData\Local\Logos4\Data\4asxrlsf.kyr\ResourceManager\Downloaded\LLS_1.0.710\ESV.logos4' to 'C:\Users\Todd\AppData\Local\Logos4\Data\4asxrlsf.kyr\ResourceManager\ScannedResources\ESV.logos4'.
2012-10-13 09:29:04.9583 7 Warn ResourceManager Failed to move file ESV.logos4 to C:\Users\Todd\AppData\Local\Logos4\Data\4asxrlsf.kyr\ResourceManager\Resources\ESV.logos4

What would cause this?

So I cleaned out the Downloaded directory and tried running Update Resources again, but the same thing happened again. (1641.LogosIndexer.log)

So I tried hiding/unhiding the ESV, and that didn't fix it. I think the resource file wasn't removed when it was hidden.

Finally, I manually deleted the ESV.logos file from the Resources directory, restarted Logos which told me that the resource was hidden, clicked the "Unhide" button, and restarted. THEN it was fixed.

I now have the current version and the translated words section is working correctly.

https://community.logos.com/discussion/comment/405854#Comment_405854

Richard, your NIV 84 problems also appear to be from having a version of the reverse interlinear that does not correspond to your version of the NIV 84. The indexer will not index a reverse interlinear with a Bible unless the version exactly matches what it is expecting, so that explains why you aren't getting lemma search results in NIV 84. Unfortunately only indexing has this protection—all of these other features are capable of trying to use an incompatible version. Updating your resources should fix the problem. You will need to rebuild your Bible index for searching reverse interlinear data in NIV 84. The versions you should have are

2012-10-12T17:14:23Z for NIV.logos4

2012-10-11T22:04:01Z for NIVNT.lbsrvi

Following Todd's procedure I was able to get the correct NIV84 to download.

Is there any idea about how such an update would not happen automatically? I'm curious in case there are other updating issues I have but am not aware of.

EDIT: Forgot to mention that the NIV84 inline rev.int. lines up properly now and once indexing finished "search this resource" also works again.

Fred Chapman

https://community.logos.com/discussion/comment/406039#Comment_406039

Thanks Todd. Deleting the esv from the resources directory and restarting, downloading and indexing fixed my problem as well.

https://community.logos.com/discussion/comment/406141#Comment_406141

So, is this resource update problem a bug? At least three of us had similar problems, and I haven't experienced anything like it until now.

https://community.logos.com/discussion/comment/405963#Comment_405963

2012-10-13 09:29:04.9583 7 Info ResourceManager Moving resource from 'C:\Users\Todd\AppData\Local\Logos4\Data\4asxrlsf.kyr\ResourceManager\Downloaded\LLS_1.0.710\ESV.logos4' to 'C:\Users\Todd\AppData\Local\Logos4\Data\4asxrlsf.kyr\ResourceManager\ScannedResources\ESV.logos4'.

2012-10-13 09:29:04.9583 7 Warn ResourceManager Failed to move file ESV.logos4 to C:\Users\Todd\AppData\Local\Logos4\Data\4asxrlsf.kyr\ResourceManager\Resources\ESV.logos4

What would cause this?

It could fail to move the file if the existing one was in use. Is it possible that you had Logos 5 open when this happened? (I think this is unlikely, because this line was logged during the "Preparing your library" phase; at this stage, Logos 5 shouldn't have any files open but should just be waiting for the indexer to finish.)

https://community.logos.com/discussion/comment/406439#Comment_406439

It could fail to move the file if the existing one was in use. Is it possible that you had Logos 5 open when this happened?

I don't think so---especially since I tried multiple times to update the resource. Plus, I had the problem of the file not being deleted when it was hidden (but I don't have logs from that instance). It is like some process was holding on to the file. I did verify that it wasn't marked read-only before I deleted it.

https://community.logos.com/discussion/comment/406440#Comment_406440

I don't think so---especially since I tried multiple times to update the resource. Plus, I had the problem of the file not being deleted when it was hidden (but I don't have logs from that instance).

Same thing happened with me: Closed all instances of NIV in L5. Hid the resource, closed L5, restarted, then checked and it was still there. Deleted manually. Closed, & opened L5 again, then unhid and closed & opened again & L5 upgraded to the new file version.

My problem was with the NIV (my preferred Bible). I wonder if that's what caused the problem? (I didn't change my default Bible before/after moving to hidden. After hiding/restoring it is still my preferred Bible.)

https://community.logos.com/discussion/comment/406507#Comment_406507

My problem was with the NIV (my preferred Bible).

And mine was with my preferred bible, ESV.

https://community.logos.com/discussion/comment/405763#Comment_405763

That just doubled my problem - see previous post - as the download is now 1.18 GB. How much of that is useful?

The Update Manager should have recognised that the previous RI downloads are now superseded, but it appears it may not have.

You could try "update resources" to force a full check, or you could shut down the app and delete your UpdateManager\Updates.db database to ensure that it "forgets" the previous downloads.

Don't forget that the initial release of RI's was not removed from my download when the updated ones were issued.

Fred Chapman

https://community.logos.com/discussion/comment/406523#Comment_406523

My problem was with the NIV (my preferred Bible).

And mine was with my preferred bible, ESV.

Mine was the ESV as well which is my preferred bible in Logos. The preferred bible selection may be the source of the problem

https://community.logos.com/discussion/comment/405755#Comment_405755

I just sent a typo report on the rev.int. for Heb.11:1 in both the NIV84 and NIV11. As long as you're rebuilding, you might as well get those changes in too.

Unfortunately the new builds were already well on their way. I passed on your typo report, so hopefully it will be fixed in the next release.

The good news is the updated reverse interlinears are available now.

NIV reverse interlinears were updated today, and the typo I reported was corrected. Thanks!

(Wow, that was fast!)