4.5 Beta 10 Text Comparison Puzzle for 1 Verse

Puzzled by text comparison of Revelation 13:1

image

Personal Book docx file is posted in thread => http://community.logos.com/forums/p/12407/315126.aspx#315126 that builds with 0 errors and 0 warnings along with having milestone [[@Bible:Re13:1]] with {{field-on:Bible}} and {{field-off:Bible}}

In Text Comparison, can hover over Re 13:1 for pop-up in Logos 1901 ASV and my ASV1901.

Keep Smiling [:)]

Comments

  • Dave Hooton
    Dave Hooton MVP Posts: 36,195

    " rel="nofollow">Keep Smiling 4 Jesus :) said:

    Puzzled by text comparison of Revelation 13:1

    It happens with other Logos bibles

    image

    It's the way the text is split between 12.17 and 13.1

    Dave
    ===

    Windows 11 & Android 13

  • It's the way the text is split between 12.17 and 13.1

    Fascinating split; appears Logos ASV resource has bit different tagging.

    image

    Thanks for idea of comparing with other Bibles.

    Keep Smiling [:)]

  • Dave Hooton
    Dave Hooton MVP Posts: 36,195

    " rel="nofollow">Keep Smiling 4 Jesus :) said:

    Fascinating split; appears Logos ASV resource has bit different tagging.

    If you perform a Compare for 12:17 only v.13:1 also appears!

    I've sent an email to  logos4feedback@logos.com

    Dave
    ===

    Windows 11 & Android 13

  • " rel="nofollow">Keep Smiling 4 Jesus :) said:

    Fascinating split; appears Logos ASV resource has bit different tagging.

    If you perform a Compare for 12:17 only v.13:1 also appears!

    I've sent an email to  logos4feedback@logos.com

    Thanks [8-|]

    Keep Smiling [:)]

  • MJ. Smith
    MJ. Smith MVP Posts: 55,093

    Early on I reported a number of these anomalies that occur if you play games with the base text. I believe they are in the wiki error logs.

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

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

    Can you please send me the resource information for ASV1901?  We don't have that resource available, it appears to have been deprecated by 1901 ASV.

  • Dave Hooton
    Dave Hooton MVP Posts: 36,195

    Mine is called 1901 ASV

    LLS:1.0.60
    2011-06-22T22:37:46Z
    ASV.logos4

    To my Comparison (12.17-13.1) add NKJV and KJV1900 for more weirdness.

    Dave
    ===

    Windows 11 & Android 13

  • Can you please send me the resource information for ASV1901?  We don't have that resource available, it appears to have been deprecated by 1901 ASV.

    The "ASV1901" is my Personal Book Bible project; docx file (with OT prefaces and NT text) is posted in thread => http://community.logos.com/forums/p/12407/315126.aspx#315126 that builds with 0 errors and 0 warnings along with having milestone [[@Bible:Re13:1]] with {{field-on:Bible}} and {{field-off:Bible}}

    The "1901 ASV" is the current Logos American Standard Version resource, which has not been deprecated.  Note: the Logos "1901 ASV" resource lacks preface text for OT and NT.

    image

    The public domain text has several typographical errors, which are easy to find using Text Comparison in Logos 4, then fix in docx file.  Sent separate report about John 21:17 having more words in a text file, which are also in a printed ASV with 1901 and 1929 copyrights.

    Note: my Personal Book Bible project is a work in progress; have compared ASV text in New Testament that has 0 % differences, except for two verses: John 21:17 and Revelation 13:1, which is the basis for this thread.  Currently adding New Testament Red Letter tagging (synoptic gospels yet to do) plus have Old Testament books to copy, then convert text verse markings to Logos @Bible milestones with bible-on and bible-off tagging.

    Keep Smiling [:)]

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

    " rel="nofollow">Keep Smiling 4 Jesus :) said:

    It's the way the text is split between 12.17 and 13.1

    Fascinating split; appears Logos ASV resource has bit different tagging.

    image

    Thanks for idea of comparing with other Bibles.

    Keep Smiling Smile

    Thanks - I've written up a case and sent it to our Development department.

     

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

    " rel="nofollow">Keep Smiling 4 Jesus :) said:

    It's the way the text is split between 12.17 and 13.1

    Fascinating split; appears Logos ASV resource has bit different tagging.

    image

    Thanks for idea of comparing with other Bibles.

    Keep Smiling Smile

    Thanks - I've written up a case and sent it to our Development department.

     

     

    This appears to be working as designed.  From our Development department:

    "Revelation 12:17-13:1 is a common difference in versification in English Bibles. (The text that is in 12:18 in NET is part of 12:17 in many Bibles, and part of 13:1 in others. Most Bibles don't have v18.)

    A Bible "Grid" search will graphically show how the versions align.

    The Text Comparison output could perhaps be arranged better, but it's producing a reasonable output given the difference in the underlying translations. Determining how to show verse-by-verse differences when there aren't one-to-one correspondences between verses in the display translations could be very difficult."

  • This appears to be working as designed.  From our Development department:

    "Revelation 12:17-13:1 is a common difference in versification in English Bibles. (The text that is in 12:18 in NET is part of 12:17 in many Bibles, and part of 13:1 in others. Most Bibles don't have v18.)

    A Bible "Grid" search will graphically show how the versions align.

    The Text Comparison output could perhaps be arranged better, but it's producing a reasonable output given the difference in the underlying translations. Determining how to show verse-by-verse differences when there aren't one-to-one correspondences between verses in the display translations could be very difficult."

    My desire is to create a Personal Book (PB) edition of the American Standard Version (ASV). whose Text comparison can match Logos ASV.  My PB docx file includes::

    @{{bible-on}}[[@Re13:1]]and he stood upon the sand of the sea. And I saw a beast coming up out of the sea, having ten horns, and seven heads, and on his horns ten diadems, and upon his heads names of blasphemy. [[@Re13:2]]And . . . .{{bible-off}}

    How should this verse be tagged so Text Comparison shows 0 % differences between my PB of ASV and Logos ASV ?

    Oddity: right click on first word, "and", in both ASV's shows reference Revelation 13:1, yet Text Comparison for the same words in this verse has 100 % difference:

    image

    Keep Smiling [:)]

  • Bradley Grainger (Logos)
    Bradley Grainger (Logos) Administrator, Logos Employee Posts: 12,138

    " rel="nofollow">Keep Smiling 4 Jesus :) said:

    My desire is to create a Personal Book (PB) edition of the American Standard Version (ASV). whose Text comparison can match Logos ASV.  My PB docx file includes::

    Re13:1Re13:2]]And . . . .{{bible-off}}

    How should this verse be tagged so Text Comparison shows 0 % differences between my PB of ASV and Logos ASV ?

    I believe the 1901 ASV uses the KJV's versification scheme, so you should tag all milestones in your document explicitly using that versemap, for example: [[@BibleKJV:Rev 13:1]]

  • " rel="nofollow">Keep Smiling 4 Jesus :) said:

    How should this verse be tagged so Text Comparison shows 0 % differences between my PB of ASV and Logos ASV ?

    I believe the 1901 ASV uses the KJV's versification scheme, so you should tag all milestones in your document explicitly using that versemap, for example: [[@BibleKJV:Rev 13:1]]

    Changing Bible milestones to KJV versification had some intriguing results until added chapter milestone:

    [[@BibleKJV:Re 13]] {{bible-on}}[[@BibleKJV:Re13:1]]and he stood upon the sand of the sea. And I saw a beast coming up out of the sea, having ten horns, and seven heads, and on his horns ten diadems, and upon his heads names of blasphemy. [[@BibleKJV:Re13:2]]And . . . .{{bible-off}}

    Thanks [8-|] Text Comparison now shows 0 % differences for verse and chapters.

    Now wondering how to tag Bible Chapter # for Table of Contents entry without using a separate paragraph; have tried fields heading and headtitle

    @{{field-on:heading}}[[@BibleKJV:Re13]]13
    @{{field-off:heading}}{{bible-on}}[[@BibleKJV:Re13:1]]and he stood upon the sand
    of the sea. And I saw a beast coming up out of the sea, having ten horns, and
    seven heads, and on his horns ten diadems, and upon his heads names of
    blasphemy. [[@BibleKJV:Re13:2]]And

    By the way, also tried a separate paragraph for chapter # using a heading style with small font and white font color, which does work.  If font size is less than 5 pt, then warning appears in PBB log about extreme size. 

    Keep Smiling [:)]

  • Dave Hooton
    Dave Hooton MVP Posts: 36,195

    " rel="nofollow">Keep Smiling 4 Jesus :) said:

    Changing Bible milestones to KJV versification had some intriguing results until added chapter milestone:

    [[@BibleKJV:Re 13]] {{bible-on}}[[@BibleKJV:Re13:1]]and he stood upon the sand of the sea. And I saw a beast coming up out of the sea, having ten horns, and seven heads, and on his horns ten diadems, and upon his heads names of blasphemy. [[@BibleKJV:Re13:2]]And . . . .{{bible-off}}

    Thanks Geeked Text Comparison now shows 0 % differences for verse and chapters.

    Yes, but that method has created issues for other comparisons

    image

    The NKJV has a different versification scheme but the same verse split as ASV and KJV1900.

    Dave
    ===

    Windows 11 & Android 13

  • The NKJV has a different versification scheme but the same verse split as ASV and KJV1900.

    Text Comparison for single verse of Revelation 13:1 appears bit different than comparing a range that includes Revelation 13:1

    image

    Keep Smiling [:)]

This discussion has been closed.