Jump to content

Bug with Changing English Translations


Recommended Posts

Posted (edited)
I'm having a bizarre problem when flipping through versions in a one pane window. I enter Mark 10:1, in the search bar. Then I use cntrl-shift-number to flip through and compare various translations. Instead of keeping me on Mark 10:1, the software starts jumping around wildly to various random places in the Bible. ESV takes me to Mark 9:44. AMP to Mark 9:49. NIV Mark 9:45. NRSV to Rev 6:3!!
Looks like a bug to me?
I never recall having this problem prior to 2.0, back when search and display were independent. I hope you are giving serious consideration to a preferences option to bring back those old features for your advanced users! They were critical to my use of Accordance.
Thanks!
Randy

 

 

 

 

 

 

 

Edited by Randy Steffens Jr
Posted

Can anyone else replicate this? Is it a unique problem I'm having or a bug?

 

Thanks!

 

Randy

Posted

Sorry, but I could not replicate this. The correct verse(s) displayed (unless they were not present in that text module). NB: my ctrl-shift-n, where n=0, 1, 2, ..., 9) are all original language Greek texts.

Posted

I haven't studied this but I started out in ESVS and started from Mark 10:1 and the various ctrl-shirt-N started to go to some rather unexpected places including Ephesians at one point. Playing will be required to sort out a repro. case. I suspect where you end up is related to what's where in the first and the second texts between which the switch is occurring but that's a guess. My texts are mix of languages including texts missing Mark entirely like the KJVA.

 

BTW, I've never before used this feature so I don't have any comparison to previous function.

 

Thx

D

Posted

Even starting with an English text, using the keyboard command yields the original selected text, such as Mark 10:1

Posted

Randy, you got your wish in 10.2.2 :)

Posted

I am so glad to hear that Joel! This will be a tremendous blessing. I really appreciate all you and the team do to provide stellar customer satisfaction.

 

Randy

  • 2 weeks later...
Posted

Thank you SO much for fixing this in 10.2.3! I am thrilled to see the old features restored! It works so much better for my needs now. I really appreciate the responsiveness of the Accordance team. You have a dedicated customer for life.

 

Randy

  • 2 weeks later...
Posted (edited)
I'm still having a problem being kept in the same location in the Bible when changing translations.
When I enter a verse from the search bar (Say Hebrews 11:30), and then change the version displayed, The software doesn't always keep me reading in the same spot. If I start from KJV (my default) and switch to AMP, I am taken to Heb 11:28. If I switch from KJV to ASV or NIV, I'm taken to Hebrews 11:14. And KJV to NRSV Rev 22:21!
This also only occurs for the 1st text searched for, immediately after opening a new KJV module. And one must switch from KJV directly to the translation in question. If one goes from say, KJV to NKJV to NIV, the issue does not occur.
Can anyone else duplicate this behavior?
Randy

 

Edited by Randy Steffens Jr
Posted

Hi Randy, I have tried a few different ways to duplicate this without success.

 

I know you have done this reasonably well already, but could you delineate the exact steps (press by press/click by click) that you do to make this happen?


Thanks

Posted

OK, Here's the procedure.

 

Set Default Bible to KJVS in Preferences. Close all workspaces. Then quit Accordance.

 

Open Accordance. Open a new workspace (default KJVS). Type Hebrews 11:30 into the search bar. Hit enter. Click on the Display Text drop down menu, and select NIV. You will be immediately taken to Hebrews 11:14.

 

Now close the workspace.

 

Open a new workspace. Type Hebrews 11:30 into the search bar. Hit enter. Click on the Display Text drop down menu, and select AMP. You will be immediately taken to Hebrews 11:28.

 

Now close the workspace.

 

Open a new workspace. Type Hebrews 11:30 into the search bar. Hit enter. Click on the Display Text drop down menu, and select NRSVS. You will be immediately taken to Revelation 22:21.

 

Repeat this process for each of the affected translations.

 

Thanks!

Randy

Posted

That's very peculiar Randy. I have followed your instructions exactly and cannot reproduce the issue.

 

Can anyone else?

Posted

Its possible to see variations like this using either Ctrl-shift-# or the displayed text pull down.

So I started with the original Mark 10:1 search or the newer test case with Heb 11:30 and its easy to go astray as you cycle through the texts.

 

KJVS Heb 11:30 Do search. That works. You're at Heb 11:30

Ctrl Shft 1 (ESVS). Lands up at Heb 11:13.

Ctrl Shft 4 (BBE). Lands up at Heb 10:34.

 

I omitted Ctrl Shft 2 and 3 as 2 is KJVS and 3 is KJVA.

 

Curiously if I start at KJVS Heb 11:30 and go directly to BBE it locates correctly.

 

Or try starting at KJVS Heb 11:30 and then use the display text menu.

BBE -> Heb 10:34

WEB -> Heb 10:34

NAS95S -> Heb 10:38

NET -> Heb 10:21

NAS95S -> Heb 10:38

DOUAY -> Rev 22 somewhere - basically the end of the text.

 

Thx

D

Posted

I just downloaded 10.2.4, which unfortunately does not fix this issue. I'm still having the exact same problem. Any updates on when a solution to this bug might get implemented?

 

Thanks!

Randy

Posted

Hi Randy and Daniel, it doesn't happen for me at all. I have tried multiple texts, various starting points, changing texts using the drop down and control shift x. I just can't get Accordance to mess up.

 

Must be because I am using Accordance upside-down here in Australia. But it sounds like we have one of those pesky "with this setup" issues, so I am not sure how our developers will troubleshoot this if we can't reproduce it...Any more ideas about what might need to be done to cause this? Maybe a shot of your Search tab preferences?

Posted

Thought I'd experiment with this, I get similar results as Randy and Daniel. (Latest Acc 10.2.4)

 

Start: KJVS - Heb 11:30

 

C/S #1= EVS - Heb 11:13

 

C/S #2= HCSB - Heb 10:28

 

C/S #3= NRSV - Rev 22:21

 

C/S #4= NASB - Heb 11:30

 

C/S #5 NIV - Heb 10:14

 

(C/S = control + shift)

 

interesting that 3 are seeing this, and yet the version reference results are not identical. Results are not what one would expect; calling this a bug.

 

 

Second test:

Start: ESV - Heb 11.30

 

Cmd N - C/S # type Heb 11.30 in search bar = Heb 11:30

following this procedure Accordance works as expected with the various bible texts

 

Third test:

open Acc - close workspace (Cmd w) - open workspace (Cmd N) - type Heb 11:30 search bar - close (Cmd w) - open (Cmd N) - C/S # - type Heb 11:30 search bar - etc.

 

works as expected.

 

Hope this may be helpful.

Posted

OK - I tried again. No luck sadly. I have included a few screenshots. Have a look and tell me if there is something I am missing/that is different. Context slider, etc etc. All my text changes were done using CTRL-SHFT-x except the RV (my last one) which was done from the displayed text drop down.

 

post-29509-0-62958900-1378075766_thumb.png post-29509-0-78301000-1378075769_thumb.png post-29509-0-51222600-1378075756_thumb.png post-29509-0-22872300-1378075763_thumb.png post-29509-0-43492300-1378075759_thumb.png

Posted

Ken, I can confirm your results as working with the context slider to 0 (as your screenshots); however, do you get the same results with the context slider set to "all". Set to "all" brings about the unexpected behavior - at least for me.

Posted (edited)

I was playing with this a little more, and I noticed the differing text references at the bottom right corner - for example: the Rev 22:21 display shows the text reference as Rev 22:5266; the Mounce NT and CNT show a reference to the OT; etc.

 

Perhaps this additional info will be of help.

 

Also, I find that using the book choice (bottom right corner) and the arrow keys (bottom left corner) and not using the search bar gives the desired and expected results whether using the text drop down or cycling thru using control/shift. It is when one uses the search bar with context set to "all" that things go wrong.

Edited by accord
Posted

I can confirm that when I go to Preferences>Search Tabs and uncheck "Add Automatic Context", this issue disappears. So try checking "Add Automatic Contact" under preferences Ken, and see if you can duplicate this issue that way.

 

Thanks!

Randy

Posted

I tried my test above again and it appears that setting the slider to 0 after the initial search, or doing it that way initially, will give you correct behaviour. But interestingly if you leave the slider at A and go to the next text and land in the wrong place, moving the slider to 0 leaves you with the correct verse in the display. So it seems it knows where it should be but is displaying at an unexpected point.

 

Thx

D

Posted

OK! I have reproduced. Not quite as wildly as all you guys seem to have - the most off the wall was Mounce Reverse which jumped to no text at all. The rest all jumped to around Heb 11:13-16 or thereabouts.

 

Nonetheless, having reproduced it, I can't do anything about it directly but say to our developers, it's confirmed as an "undocumented feature" ^_^ . Automatic context must be on, and it works with the KJVS as the startup text, and HCSBS, ESVS, NIV-G/K and probably more.

 

So over to the developers....

Posted

I'm having the same issue, and it's driving me crazy!

 

However, I'm not sure automatic context must be selected in preferences for the bug to occur. I have attached a screen shot of my Search Tabs preference to show my setup.

 

-Phil

 

post-30144-0-75403800-1378126960_thumb.jpg

Posted

I agree the key issue is where the context slider is set. The impact of the pref setting appears to be in new workspaces initial setting of the slider. Thus the pref seems an indirect driver of the problem. The key issue is to ensure that the context slider is set to 0 however that is achieved, as far as I can tell. After I first unchecked the pref it didn't initially do anything helpful for me. I had to create a new workspace and in fact I think I restarted Acc just to be sure. But it didn't really matter which way I had the pref set if I set the context slider manually.

 

One thing I have not tried is to set the context slider to an intermediate value between 0 and A.

 

Thx

D

Posted

We have identified the issue, and fixed it for the next release.

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
×
×
  • Create New...