BUG: Mysterious highlighting in Reverse Interlinear

Harry Hahne
Harry Hahne Member Posts: 935 ✭✭

I have an odd highlighting in Genesis 1:1 if I turn on the reverse interlinear ribbon.

Note that I have clicked on "created", but both "created" (בָּרָ֣א) and "in" (ב) are highlighted. Nothing I can do will remove the highlighting around "in" at the beginning of the verse. However, if I click on a different verse, the blue highlight on "in" goes away. It also goes away if I turn off the reverse interlinear ribbon. I don't see this behavior in other verses.

I have no visual filters on and no highlights or notes on the word "in".

Does anyone have an idea about why this highlight is there only when the verse is selected?

Comments

  • DMB
    DMB Member Posts: 3,087

    Don't know, but confirm pattern. Also NASB 2020 and ESV.  So, I guess most of them.

    I never use the pane, but clicking on columns in the pane sometimes works (lines up with text), and sometimes bounces to another position entirely.  Tried same with several RIs.  I give up.

  • MJ. Smith
    MJ. Smith MVP Posts: 53,407

    DMB said:

    but clicking on columns in the pane sometimes works (lines up with text), and sometimes bounces to another position entirely.

    Any examples? This is the first I've heard of the bug and I can't recreate it.

    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."

  • Harry Hahne
    Harry Hahne Member Posts: 935 ✭✭

    MJ. Smith said:

    DMB said:

    but clicking on columns in the pane sometimes works (lines up with text), and sometimes bounces to another position entirely.

    Any examples? This is the first I've heard of the bug and I can't recreate it.

    My original experience was with NASB1995, but if happens with the NLT and NIV 2011. I have only seen it happen in Genesis 1:1. The first word ("in") is highlighted if I have the Interlinear pane displayed and click on any word in the verse. The highlight goes away of I click on another verse.If I click on any word in the first verse, the highlight on "In" comes back.

  • Dave Hooton
    Dave Hooton MVP Posts: 35,770

    The first word ("in") is highlighted if I have the Interlinear pane displayed and click on any word in the verse. The highlight goes away of I click on another verse.If I click on any word in the first verse, the highlight on "In" comes back.

    Can reproduce in ESV.

    Dave
    ===

    Windows 11 & Android 13

  • DMB
    DMB Member Posts: 3,087

    MJ. Smith said:

    Any examples? This is the first I've heard of the bug and I can't recreate it.

    It's a strange one. Mac; latest macOS and Verbum.  Since I don't use the RIs and definitely not the pane, it's my first experience, after they intro'd it years back.

    I 'wasted' time this AM again, trying to see what the principle is; I can't see it.  

    - I do notice it positions the verse text (above the pane) incorrectly, hiding the surface text and part of the mss (screen capture below).

    - Most shift-columns (in the pane) pop back to the verse start, as if it can't find the position, and defaults to verse start.  When it does that, it doesn't re-position the view to center it.

    - If I click on a pane column that shifts to another column (incorrectly), and then do it again (same column) it then works.  Which suggests there's an incorrect value that gets 'fixed'.

    - More often then not, the error-behavior is between the arrows (in example below, '19').  But I didn't click on columns in the '19' range.  Seems something mixing up on the ranges coding.

    Anyway, appreciate the query; I've given up ... hid the pane, fixed the RI rows and closed NASB (not a NASB'er).

  • Andrew Batishko
    Andrew Batishko Member, Administrator, Community Manager, Logos Employee Posts: 5,395

    I have an odd highlighting in Genesis 1:1 if I turn on the reverse interlinear ribbon.

    Thanks for the report. We're working on a fix for this bug.

    Andrew Batishko | Logos software developer