PBB Verse maps revisited

There have been a number of threads recently of people trying to work out which verse mapping they should use for creating their own Personal Bibles. The problem is that there's no published list from Logos as to which versions support which verses. It looks unlikely that Logos will publish their verse mapping file, as presumably they invested heavily in creating it, and don't want it to be made public.

However, I have thought of a way in which I think it may be possible for me to create a list of which Bibles include which verses. This list would not describe how the verses related to one another, merely that a particular bible datatype included particular verses (and therefore I'm sure wouldn't be publishing Logos' intellectual property). I could only do this for Bibles that I owned, but it would be relatively easy for other people to send me a small file with the required information if they owned a Bible that I did not.

Like I said, I'm not sure that this will actually work in practice, but I'd be interested to know whether people think it's worthwhile to have a go.

Find more posts tagged with

Comments

DominicM

Mark, sounds like a plan, however, what would you do about the "disputed" verses, would you map them or leave them out.. is my only concern..

RE: Project
I think its a mamoth undertaking, and would hate it to impact on your ministry.

Mark Barnes

https://community.logos.com/discussion/comment/286752#Comment_286752

what would you do about the "disputed" verses

The purpose is simply to find out which verses a particular version supports so we can use them in personal books. By definition disputed verses are supported by a datatype. It's only rejected verses that are unsupported.

I think its a mamoth undertaking, and would hate it to impact on your ministry.

I'm intending to extract the data programmatically from the .mstidx (index) files. I already have written a script to convert the information in .mstidx files into an SQL database, and I understand the file and data format there. It's therefore 'just' a question of writing the script that compares one Bible to another, and displays the results in a readable format - probably one or two evening's work.

David Ames

Some time back I started a thread that touches this subject
http://community.logos.com/forums/p/25051/185812.aspx#185812

Pick a known verse mapping. If a verse is “”missing”” in the text then add the words “no corresponding text” as a place holder. If there are “extra” words just add them. Somewhere in the Preface add your own comments on what you did to “shoe horn ¹” the text into Logos PB format so that it was usable with the standard tool.

[Using the words ‘missing’ or ‘added’ raises the other Bible to the level of Standard of Excellence when what we want is a Standard of Reference so we can compare] [The new one we are adding is the “ONE AND ONLY TRUE BIBLE” so we do not want to raise that other one to the level of perfect]

[¹ ‘shoe horn' as in force it to fit]