Bug: Text Comparison version order is all over the shop

Jonathan Sheehy
Jonathan Sheehy Member Posts: 34
edited November 21 in English Forum

As of a few weeks ago, when using a custom Collection (such as "All English Bibles"—a collection I created using a rule in Logos for desktop) in the Text Comparison tool on Android mobile (v 32 and now v33 beta), the Bible versions are all over the shop with regard to version ordering. To explain:

How it should be (and used to be until a few weeks ago): The top prioritised Bible (which is LEB, for me) should be the first translation, followed by all other translations in the collection in alphabetical order.

How it is now: In any collection I use that includes it, the CJB is the top translation, against which all other translations will be compared (for percentage difference). I have no idea why that translation has been selected, as it is nowhere in my prioritised resources. It is followed by a selection of translations, in alphabetical order. For me, this is GB, GW, KJV 1900, NASB 2020, NASB 95, NCV, NIRV, NLT, NRSV, RSV, TNIV. I have not idea how those specific translations were picked out of all my translations to go next in alphabetical order. Then, out of nowhere comes DARBY (i.e. it's not in alphabetical order). And then follow the rest of my English translations in alphabetical order: ASV, AV 1973, CSB, D-R, ESV, GNB, HCSB, KJV, LEB (this is supposed to be my top bible, but it's waaay down the list!), MSG, NET, NIV, NKJV, RSVCE, YLT.

As you can see:

  1. That's not how it should be; I don't want all translations compared against the CJB!
  2. It makes skimming down to a particular translation nearly impossible, because the alphabetical order is all over the shop (basically dividing my translations into two apparently arbitrary groups, and then arranging each of those alphabetically)

Given that I only finally succeeded in getting the Text Comparison tool working to my satisfaction about a month ago (I describe a problem many mobile users will be experiencing, along with a fairly simple workaround, in this thread), a totally different bug then showed up within a week or two. That was a bit disappointing, since comparing translations is one of the first things I do when I hone in on a verse for further study. I really would like this tool to work correctly.

Whatever is causing this behaviour is present in v 32 and, now that I am beta testing it, in v33 too.

Is anybody else experiencing this or able to replicate it?

Thanks

Tagged:

Comments

  • MJ. Smith
    MJ. Smith Member, MVP Posts: 53,036 ✭✭✭✭✭

    My weekly bump of posts that have received no response.

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

Categories