BUG: Emphasize Active Lemmas not working with BDAG

Kiyah
Kiyah Member Posts: 2,807 ✭✭✭✭
edited November 21 in English Forum

I have "Emphasize Active Lemmas" set for all of my bibles. I noticed yesterday that the lemmas aren't being highlighted in pink in my bibles (I tried multiple versions) when I'm using the BDAG, but they are when I'm using Louw-Nida, LSJ, or the DBL-Greek. I tried linking my bible with the BDAG and clicking on several lemmas and none of them are being highlighted when the BDAG brings up the entry.

Is anyone else having this problem? I just noticed it so I'm not sure when this started.

Tagged:

Comments

  • Graham Criddle
    Graham Criddle MVP Posts: 32,490

    I can reproduce this - running Logos 9.5 SR-1 on Mac - but I don't know why it is happening.

  • Kiyah
    Kiyah Member Posts: 2,807 ✭✭✭✭

    I can reproduce this - running Logos 9.5 SR-1 on Mac - but I don't know why it is happening.

    I'm running Logos 9.5 SR-1 on Windows 10. I'm sure it used to work because BDAG is my preferred Greek lexicon. The resource was last updated 3/29/2021, maybe that update broke it somehow.

  • Beloved Amodeo
    Beloved Amodeo Member Posts: 4,181 ✭✭✭

    I can reproduce this - running Logos 9.5 SR-1 on Mac - but I don't know why it is happening.

    I'm running Logos 9.5 SR-1 on Windows 10. I'm sure it used to work because BDAG is my preferred Greek lexicon. The resource was last updated 3/29/2021, maybe that update broke it somehow.

    FL should comment regarding time frame of a fix for this major bug involving an important Greek lexicon.

    Meanwhile, Jesus kept on growing wiser and more mature, and in favor with God and his fellow man.

    International Standard Version. (2011). (Lk 2:52). Yorba Linda, CA: ISV Foundation.

    MacBook Pro MacOS Sequoia 15.1 1TB SSD 

  • Mike Binks
    Mike Binks MVP Posts: 7,435

    FL should comment regarding time frame of a fix for this major bug involving an important Greek lexicon.

    Remembering the story of Everybody, Somebody, and Anybody.. (Hezekiah 3:16).

    Might I ask if in fact 'Anybody' has emailed Customer Service reporting the problem?

    tootle pip

    Mike

    How to get logs and post them.(now tagging post-apocalyptic fiction as current affairs) Latest Logos, MacOS, iOS and iPadOS

  • Beloved Amodeo
    Beloved Amodeo Member Posts: 4,181 ✭✭✭

    FL should comment regarding time frame of a fix for this major bug involving an important Greek lexicon.

    Remembering the story of Everybody, Somebody, and Anybody.. (Hezekiah 3:16).

    Might I ask if in fact 'Anybody' has emailed Customer Service reporting the problem?

    Good Morning, Binks

    I have not, but will gladly pick up this mantle and inform Customer Service.

    Meanwhile, Jesus kept on growing wiser and more mature, and in favor with God and his fellow man.

    International Standard Version. (2011). (Lk 2:52). Yorba Linda, CA: ISV Foundation.

    MacBook Pro MacOS Sequoia 15.1 1TB SSD 

  • Mike Binks
    Mike Binks MVP Posts: 7,435

    I have not, but will gladly pick up this mantle and inform Customer Service.

    Good man!

    'Somebody' comes up trumps again!  [;)]

    tootle pip

    Mike

    How to get logs and post them.(now tagging post-apocalyptic fiction as current affairs) Latest Logos, MacOS, iOS and iPadOS

  • Philana R. Crouch
    Philana R. Crouch Member, Logos Employee Posts: 4,597

    I have "Emphasize Active Lemmas" set for all of my bibles. I noticed yesterday that the lemmas aren't being highlighted in pink in my bibles (I tried multiple versions) when I'm using the BDAG, but they are when I'm using Louw-Nida, LSJ, or the DBL-Greek. I tried linking my bible with the BDAG and clicking on several lemmas and none of them are being highlighted when the BDAG brings up the entry.

    Is anyone else having this problem? I just noticed it so I'm not sure when this started.

    Hi Kiyah,

    This issue is being investigated. Thank you for reporting this.

  • Kiyah
    Kiyah Member Posts: 2,807 ✭✭✭✭

    Hi Kiyah,

    This issue is being investigated. Thank you for reporting this.

    This appears to have been fixed with the latest resource update. It's working now.