Re: [Tyndale STEP - Programming] Scripts uploaded, Expository Bible

Hi David

I've kind of lost track of all the material that is ready to be integrated into the Tyndale STEP stuff, and all the other stuff... What I think would work best for our mailing lists, is if we

1- used mainly the sword-devel or jsword-devel mailing lists from crosswire going forward... (assuming that's alright with everyone else)

2- built up feature specifications. So all our conversations ideally would stem from a feature we want to include. At which point, it would be good to have the feature raised in JIRA, and then as the discussion progresses, someone fills in the details of the feature, so that we get a clearer understanding

3- use those mailing lists to clarify features already available

I think the blog is good in the sense that it's searchable, but it's not very categorised. Are you signed up to the mailing lists? I must say I haven't used the blogs much, but the mailing list feature of it I have, and it's good to know there's a store somewhere else!

Chris

On 26 January 2010 13:10, Tyndale STEP Project <tyndalestep@googlemail.com> wrote:

Troy, would Colin's OCR'ed Expository Bible be a valuable addition to the PD commentaries in OSIS format?

Colin, The Expository Bible is a very good resource - yes, please produce a copy for STEP.
The language is rather old (eg "our own grossness ... the sin that besets us),
and the theology is simplistic ("Only two classes of men deny [the New Testament's] supremacy.
They are those who do not know what real greatness is, and those who disparage it as a literature that they may be the better able to seduce foolish and shallow youths"). However, these are common failing we have to live with, and they are valued by some.

I haven't got round to putting the articles together into files for the Editor, Sarah.
What I was thinking of was putting them into a table format in Word
because this will protect the data structure and the Unicode.
I was going to put articles from the different sources into a single doc,
sort them alphabetically, then cut them down into more manageable size.
This means that articles on the same topic should be next to each other,
even if the spelling is slightly different.

Is there one set of articles which all have the 'correct' (ie ESV) spelling?
I could mark that spelling as the one she should retain.

The Greek & Hebrew headword articles sound like a good idea, but I'm not sure how valuable it will be.
It won't ever be exhaustive in any sense, and it the articles won't be satisfying to those who are comfortable with Greek & Hebrew. It is probably better to make sure that Greek & Hebrew are searchable in the body of articles.

Thanks for your valuable scripts.

David IB




At 19:48 25/01/2010, Tyndale STEP Project wrote:

I've now sorted out the Perl scripts I've been working and uploaded
them. Some will be of more use than others of course, but they include
code for parsing the dictionary as it stands (in a plain text format,
which is going to be easier for automated tools - DOC and RTF are both
pretty badly-specified...) and assembling things.

I haven't put the dictionaries under SVN on the grounds the files may
change quite radically in the near future (as advised by Troy). The Perl
scripts could well go in though. I'm not sure how the editting workflow
is going to work out.

In terms of dictionary content, we now have plenty to be getting on
with, and the issue is more linking it up and editting, I think. I'm not
sure what the most useful things to do next are. Options are:

1. Make sure the things that need to be Unicode-safe are. (Fairly
trivial, and definitely needs to be done.)

2. Set up "verse ranges" in the dictionary for efficiency, and also to
disambiguate people of the same name. (Also fairly important, I think,
and not too much work.)

3. Convert Easton headwords to ESV spelling of proper names. I think
this can largely be done automatically. May be a nice-to-do rather than
a priority though.

4. Try and get Hebrew and Greek headwords into articles. This might be
possible from the Wikipedia entries, but I haven't considered what the
practicalities are - we might find it needs a lot of manual work.

5. Try and join up articles in different dictionaries. I suspect this
may be too hard to do automatically, and would be more easily done by
the editor at the point when they're compiling articles.

6. Something else?

7. (Something completely different). I have access to the original
Expositor's Bible set of commentaries (late 19th century) which are in
the process of being digitised and proofed for Project Gutenberg and
CCEL. Would they be useful for STEP? I'm already going to be producing
them in three separate formats (plain text, HTML, CCEL-flavour XML) so a
fourth for STEP would be fairly minimal work. (A working day to write
appropriate conversion scripts, perhaps.) I've put a copy of the Hebrews
volume on the Dropbox so you can see the text.

For reference, I'm now looking at full-time jobs which will cut down
what I'm able to do for STEP. However (on the assumption that they'll be
reasonably paid) that means I'll probably be able to offer what time I
do give for free. I'll keep you posted.

Colin

--
Posted By Tyndale STEP Project to Tyndale STEP - Programming on 1/25/2010 11:48:00 AM

 
Dear


David IB

Dr David Instone-Brewer
Technical Officer & Senior Research Fellow in Rabbinics and New Testament

Tyndale House, 36 Selwyn Gardens, Cambridge, CB3 9BA, www.TyndaleHouse.com, Phone 01223 566601 
 (division of UCCF, Ltd Company 387932, Registered Charity 306137. 38 De Montfort St. LE1 7GP)

 
 



--
Posted By Tyndale STEP Project to Tyndale STEP - Programming on 1/26/2010 04:05:00 AM