Lexham Hebrew word duplication in Text flow diagram

Scott Jacobsen
Scott Jacobsen Member Posts: 209 ✭✭
edited November 2024 in English Forum

I've stumbled across this problem. I am setting up a Text Flow Diagram of Exodus 2:23-25. As you can see from the screenshot, I end up with two of the first word, three of the second, then two of the third, fourth, and fifth. This continues throughout the text.  This is using the Lexham Hebrew text. My 4.2 & WIVU don't do this, but do other strange things with prefixes which doesn't seem to be a problem in Lexham.

 

Anyone else have this issue, and is there a fix?

Scott

Comments

  • Anyone else have this issue, and is there a fix?

    Using Logos 4.5 RC 1, able to replicate text flow diagram issue for LHI (funky stuff starts in first line) and BHS/WIVU (duplication starts happening in middle of 2nd line):

    image

    Currently appears AFAT and BHS/WHM 4.2 are usable for text flow diagrams.

    By the way, LHI word duplication issue happens with and without an alternate line.

    Keep Smiling [:)]

  • Kevin Byford (Faithlife)
    Kevin Byford (Faithlife) Member, Logos Employee Posts: 4,309

    I've stumbled across this problem. I am setting up a Text Flow Diagram of Exodus 2:23-25. As you can see from the screenshot, I end up with two of the first word, three of the second, then two of the third, fourth, and fifth. This continues throughout the text.  This is using the Lexham Hebrew text. My 4.2 & WIVU don't do this, but do other strange things with prefixes which doesn't seem to be a problem in Lexham.

     

    Anyone else have this issue, and is there a fix?

    Scott

    Hi Scott, I've reproduce this issue and will write up a case for our Development department.

  • Scott Jacobsen
    Scott Jacobsen Member Posts: 209 ✭✭

    Thanks for getting back to me on this. In a related matter, I noticed that the 4.2 and WIVU separate prefixes from the words to which they should be attached. In October 2010 there was a discussion thread about this, but I don't see any resolution. Has that been fixed/resolved? Thanks again.