Chris
Sounds good. I can probably produce you those versions if they are held in JSword. If not, i guess we probably don't want to use them! since we won't be able to display them very easily.!
Although I'm away this weekend, so it will probably have to wait a little until next week during the week or at the weekend.
Chris2009/11/13 Tyndale STEP Project <TyndaleSTEP@gmail.com>
Tyndale STEP Project wrote:
> Colin, it is easy to export whole Bibles from BibleWorks, if you want them.
>
> As for the people and places refs, you have certainly found an
> interesting example!
> I hope there aren't too many like that.
>
> Should we perhaps tackle the problem in reverse?
> - ie find a source which has a more-or-less exhaustive list of refs for
> each person/place name,
> and use that for all the versions.
>
> We could use this to compile a database of names+IDs+variant forms which
> occur in every verse,
> so when people go to that verse, the list is displayed,
> and a wordmatch is performed to highlight where they occur in the verse.
> If the names are slightly different, they won't be highlighted, but
> people can use their common sense.
> So we don't have to worry about collecting every variant form - just the
> main ones.
>
> This should solve the problem of which Judas to refer to in different
> verses,
> but it won't solve the problem of two Judas' in the same verse.
> (Hopefully, a rare problem)
>
> David IBDavid and Chris,
Yes, that was a particularly bad one! I think 90+% of the entries are
probably the same over all major versions.To clarify where I am:
I've now got a copy of Easton with all the entries tagged (person, group
of people, location, theological article, etc) plus downloaded copies of
five other similar dictionaries (Hitchcock, Fausset, ISBE, Smiths,
Naves) split by entry and which I can use as backup sources, or to
confirm Easton. (I've also bought myself a (paper) copy of Hastings'
Dictionary of the Bible (£12 for five volumes... plus £15 postage!)
which will give more detail in many cases. Unfortunately there's no
OCRed version online, but CCEL at least have scans, so I could work from
those rather than scanning them myself.)My next task is turning this into our person/places/groups etc database,
primarily ensuring that what we have is complete, accurate, and the
entries point to the right points of the Bible. We also want the
headword to be the usual modern spelling rather than the KJV/RSV as
Easton and the other dictionaries have it - I'm intending to use the
NRSV as our reference translation for this unless there's a good reason
to use another one - maybe the NET Bible would be better? (but in
practice there are only going to be a handful of cases where this
differs from any other modern source).I'm intending to do this in Biblical order rather than alphabetically -
it means less flicking of pages, ensures we have things consistent and
means we can check whether we've missed anything. It also means that I
can check the Bible verse -> database links are correct en route.I don't know if a source which contains an exhaustive names -> refs list
exists but we can do the vast bulk of it since we have a list of names
already from the headwords of Easton and can just search the KJV for
them. Writing a script to do this in our format will be faster than
working out how to parse someone else's list. Anything missed we'll find
in checking.So the plan is:
1. Generate a concordance of where all the Easton headwords occur in the
KJV and/or RSV, sort it by Bible verse.2. From this, automatically produce a highlighted version of the NRSV,
marking all the entries found in step 1 - the first one in a different
colour. I'll also mark any quoted references from the text of the Easton
dictionary not corresponding to the text in case they're helpful, plus
the entries from the timeline.3. Work through this in order, checking/proofreading/editting the
articles, modifying the headword to the NRSV spelling if needed (but
retaining the KJV spelling as an alternative), and also checking the
timeline. (Major articles will be left to a separate pass, as well as
creating "survey" articles if we need them.)4. Once we have this, checking other major versions won't be difficult -
we can produce a list of verses where we expect a name to occur and
don't find it (seeing if we have a Soundex equivalent too).
I'll have a think what can be done about the Judas problem. As far as I
know, this case is unique - I don't think there are any duplicates in
the Ezra/Nehemiah/1 Chronicles lists in the same way.
So what would be useful to have are copies of the KJV, RSV and NRSV (or
whatever modern reference Bible we reckon is best) in an easy to parse
format.Something like
@GENESIS
@Chapter 1
1. In the beginning ...
2. And the world...would be ideal.
... i.e., each verse starts on a new line (need not all be on one line),
and book and chapter titles are distinguished in some way so they're not
confused with verse continuations.Thanks,
Colin
--
Posted By Tyndale STEP Project to Tyndale STEP - Programming on 11/13/2009 08:52:00 AM
--
Posted By Tyndale STEP Project to Tyndale STEP - Programming on 11/13/2009 09:19:00 AM
No comments:
Post a Comment