Jump to content


Photo

NA28-T Crossrefs

NA28

  • Please log in to reply
3 replies to this topic

#1 Douglas Fyfe

Douglas Fyfe

    Silver

  • Accordance
  • 192 posts
  • Gender:Male
  • Location:Sydney, Australia
  • Interests:Jesus, Hebrew, Aramaic, Greek, German, Cantonese, the mighty Essendon Bombers
  • Accordance Version:11.x

Posted 23 September 2013 - 09:18 PM

I don't think this one is my fault - but it could be.

 

the crossrefs for NA28-T are looking up the wrong reference.

that is, they're giving us the LXX references, which in the Psalms for example are often a chapter and verse out. 

Accordance then takes us to not the chapter and verse after but to the reference as if it were the standard versification.

 

Eg:

Looking at Hebrews 2.12.

Crossref: Ps 21.23

Hover over crossref: get shown Ps 21.13

Click the cross ref: get taken to Ps 21.11 (LXX 20.12)

 

again, happy if it's me. but guessing it's not.

(this is on the latest PR - not at home to check my mac).


iPhone 6+ :: iOS 9.x || Windows 10 :: Samsung ATIV ultrabook i5 :: 1.80GHz || my wife controls my MacBookPro :: OSX 10.6.8


#2 Julia Falling

Julia Falling

    Platinum

  • Active Members
  • PipPipPipPipPip
  • 1,866 posts
  • Gender:Female
  • Location:Tennessee
  • Interests:Numerous!
  • Accordance Version:11.x

Posted 23 September 2013 - 10:46 PM

Douglas — I gave this a try starting with the NAS95 & NA28 Cross References in parallel.  I clicked on Ps 21.23 and got Ps 21.23.
 
I closed the second zone and changed my search text to GNT28-T w/the NAS95 and NA28 Cross References in parallel.  I again clicked on Ps 21.23 and got Ps 21.23 in the NASB (77) and the NAS95.  There was also the GNT28-T open but the pane was blank.  Do you have things set up so that you see the LXX in the OT while seeing the GNT28-T in the new Combined Text feature?  That might explain some of it.  Seems like it still went the wrong place.  You should have gotten Ps 20.14 in the LXX.
 
However, if I hover over Ps 21.23, I also get Ps 21.13.  With the hovering, I can duplicate the problem.  If I just click, having never hovered, I get the correct text.  If I hover and then click, I still get the correct text.


Edited by Julie Falling, 23 September 2013 - 10:48 PM.

Julia Falling

Accordance 11
MacBook Air El Capitan
mid-2013 1.7 GHz Intel Core i7 (2 cores)
8 GB RAM; 512 G SSD

Mac mini El Capitan Acc 11
late-2012 2.3GHz Intel Core i7 (4 cores)
16 GB RAM; 1.12 TB Fusion Drive

iPad Pro iOS 9
128 GB

 

iPhone 6s iOS 9

64 GB


#3 Rick Bennett

Rick Bennett

    Mithril

  • Accordance
  • 2,334 posts
  • Gender:Male
  • Location:Tampa Bay, FL
  • Interests: gadgets, coffee, running and cycling, Rays baseball
  • Accordance Version:11.x
  • Platforms:Mac OS X, Windows, iOS

Posted 24 September 2013 - 11:53 AM

I looked into this and it is an issue in how the module was coded. It was assumed that when setting prefs to an LXX text, or selecting it from the text view drop down it would automagically go to the correct reference. It doesn't. So, an update will be released that specifically codes these to the LXX1 text, since it is an original language resource.

 

Thanks for the report.


  • Abram K-J likes this

Rick Bennett
Director of Content Development


#4 Douglas Fyfe

Douglas Fyfe

    Silver

  • Accordance
  • 192 posts
  • Gender:Male
  • Location:Sydney, Australia
  • Interests:Jesus, Hebrew, Aramaic, Greek, German, Cantonese, the mighty Essendon Bombers
  • Accordance Version:11.x

Posted 24 September 2013 - 07:28 PM

thanks Rick. glad I finally found a bug that wasn't my fault!


iPhone 6+ :: iOS 9.x || Windows 10 :: Samsung ATIV ultrabook i5 :: 1.80GHz || my wife controls my MacBookPro :: OSX 10.6.8






Also tagged with one or more of these keywords: NA28

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users