Interlinear does not work in NIV1984 since updating to 5.1a Beta
Are you in the OT or NT? The NIV84 only has a NT reverse interlinear.
Bradley,
It does not work in OT
Bradley, It does not work in OT
As Bradley said, the NIV84 doesn't have an OT RI, so this behavior is expected.
Inline Interlinear display is broken in the NT and OT in the NASB 1995, the New NIV 2011,ESV
I'm not able to reproduce this problem. Can you post an annotated screenshot (or screencast) demonstrating the bug?
Also, it would be helpful to know if you were on Mac or PC.
I am using Macbook Pro 10.84. Here is a screen shoot of the ESV
Lewis, did you press the button to the right of the word display? Just Checkin.
Lynden,
I'm referring to the inline display.
Lewis is asking about the inline reverse interlinear, which is different than the reverse interlinear panel (accessed via the button).
I can confirm the issue on my iMac, running 10.8.4. So it seems like it is a Mac issue (No comments Lynden... the problem isnt Mac, its Logos [;)])
I can confirm the issue on my iMac, running 10.8.4
Since I like interlinear displays even less than George, not sure what I should see when activating Inline. However, nothing happens with either NKJV or ESV, so I suppose it is broken. This is, of course, with Mac OS 10.8.4
(No comments Lynden... the problem isnt Mac, its Logos
[:#]
I can confirm the issue on my iMac, running 10.8.4 not sure what I should see when activating Inline. However, nothing happens with either NKJV or ESV, so I suppose it is broken.
not sure what I should see when activating Inline. However, nothing happens with either NKJV or ESV, so I suppose it is broken.
When using "inline," the info chosen appears DIRECTLY below each English word, rather than in the RI pane below. I'd give a screen shot, but well, you know... (I can't. [:D])
Bump
I've got the exact same issue on my Mac. No Inline info whatsoever. The panel below works fine, but no inline, which is what I use. Or used to use... [;)]
I have created a new thread HERE. I fear that the subject line and initial post may have muddied the issue.
This will be fixed in 5.1a Beta 3.
