<html>
<body>
Great, Daniel!<br>
(To be honest I don't know your acronyms, but I guess you know what
you're doing). <br><br>
Do we need extra permission for this? <br>
The work done by the guys at openscriptures
<<a href="http://github.com/openscriptures" eudora="autourl">
http://github.com/openscriptures</a>> is based on my work, and I
certainly give permission, <br>
but they didn't reply to my email asking if they were offering it to PD.
<br>
They also have another very interesting project called
"morphhb" <br>
which appears to be the Leningrad OT tagged with Strongs, in Unicode with
many corrections. <br>
- ie all the PD stuff, but with extra corrections and all in tidy
XML.<br><br>
I think David Troidl <DavidTroidl@aol.com> is the contact but, as I
said, he declined to reply to me. <br>
Perhaps I didn't phrase the question properly. Sounds like a
job for David Haslam's expertise. <br><br>
David IB<br><br>
<br>
On 23 April 2010 20:33, Daniel Owens <dhowens@pmbx.net>
wrote:<br><br>
I may be able to work at it in a few weeks. It will need to be
transformed into TEI for SWORD. I am not so strong on XSLT, so if anyone
with better skills there would take this on it would go more
quickly.<br><br>
Daniel<br><br>
<blockquote type=cite class=cite cite="">
<dl>
<dd>On 4/23/2010 2:03 PM, David Instone-Brewer wrote:<br>
<dl>
<dd>Sword have a good Hebrew lexicon based on Strongs (corrected by me),
but I don't know where such things are stored.<br>
<dd>The guys at openscriptures
<<a href="http://github.com/openscriptures">
http://github.com/openscriptures</a>> have added several more
corrections to my corrections, and produced a tidy XML package,<br><br>
<dd>downloadable at
<a href="http://github.com/openscriptures/strongs/downloads">
http://github.com/openscriptures/strongs/downloads</a><br>
<dd>Could this be converted into a replacement Sword module by
someone?<br><br>
<dd>David IB<br><br>
<dd>At 19:45 23/04/2010, Chris Burrell wrote:<br>
<dl>
<dd>Hi Daniel<br><br>
<dd>I think to start with we really need a Strong-tagged hebrew sword
module and if possible with the morphology in it. That would help with
the classic interlinears and in particular in their accuracy. Perhaps
that already exists, but I haven't been able to find it.<br><br>
<dd>And then as you say, a good Hebrew lexicon would be a great addition.
Hopefully David IB will be able to comment on the best way forward here.
We'll need both at some point, so either would be good!<br>
<dd>Chris<br><br>
<br>
<dd>On 22 April 2010 00:07, Chris Burrell
<<a href="mailto:chris@burrell.me.uk">chris@burrell.me.uk</a>
<<a href="mailto:chris@burrell.me.uk" eudora="autourl">
mailto:chris@burrell.me.uk</a>>> wrote:<br><br>
<dd> Hi Daniel<br><br>
<dd> I'm copying David IB from Tyndale House who is part of
Tyndale<br>
<dd> House and leading the data side of the project.<br><br>
<dd> A couple of emails have circulated on this previously on
our<br>
<dd> blogs, which I've tried to capture (in part) on<br>
<dd>
<a href="http://crosswire.org/bugs/browse/TYNSTEP-44">
http://crosswire.org/bugs/browse/TYNSTEP-44</a><br>
<dd>
<a href="http://crosswire.org/bugs/browse/TYNSTEP-45" eudora="autourl">
http://crosswire.org/bugs/browse/TYNSTEP-45</a><br><br>
<dd> I'm sure David IB will have more to input on this...
I've copied<br>
<dd> his original email below<br>
<dd> Chris<br><br>
<dd> ==========================================<br>
<dd> THis is the best lookup lexicon to use for Hebrew
interlinear -<br>
<dd> it is tagged to Strongs, includes the pointed Hebrew and
has an<br>
<dd> abbreviated BDB entry. And the version downloadable
from<br>
<dd>
<a href="http://github.com/openscriptures">
http://github.com/openscriptures</a> has even more corrections than<br>
<dd> mine. For all I know, it might finally be letter
perfect! THis<br>
<dd> version is also packaged in nice XML which can easily
be<br>
<dd> converted to any other DB format.<br><br>
<dd> The equivalent lexicon at Crosswire for Greek is, I
think, in a<br>
<dd> much better state, and didn't need all the work the
Hebrew did.<br><br>
<dd> The version of the tagged OT text at<br>
<dd>
<a href="http://github.com/openscriptures">
http://github.com/openscriptures</a> is also in very good condition<br>
<dd> (prob better than the one at Crosswire). It appears to
only<br>
<dd> contain PD data - ie it doesn't include the more
complete<br>
<dd> morphology data which is copyrighted.<br><br>
<dd> David IB<br><br>
<br><br>
<dd> On 21 April 2010 23:22, Daniel Owens
<<a href="mailto:dhowens@pmbx.net">dhowens@pmbx.net</a><br>
<dd>
<<a href="mailto:dhowens@pmbx.net" eudora="autourl">
mailto:dhowens@pmbx.net</a>>> wrote:<br><br>
<dd> Chris,<br><br>
<dd> I am not qualified to contribute
code (though I lurk on<br>
<dd> sword-devel because of my
module-creating disposition), but I<br>
<dd> am involved in producing content
for the very purpose you<br>
<dd> mention. By the way, if you are
at Tyndale House now, you may<br>
<dd> know Daniel Block. He is my PhD
mentor at Wheaton College.<br><br>
<dd> There are two content areas with
which I am involved and<br>
<dd> would be happy to collaborate
on. One is Greek and Hebrew<br>
<dd> lexica. Currently at
<a href="http://www.textonline.org">www.textonline.org</a><br>
<dd>
<<a href="http://www.textonline.org/" eudora="autourl">
http://www.textonline.org</a>> we are involved in<br><br>
<dd> collaboratively producing a
modern replacement for Strongs.<br>
<dd> We're starting with a Strongs
base but hope to provide a<br>
<dd> basic and up-to-date modern
equivalent to Holladay for Hebrew<br>
<dd> or Newman for Greek, except that
they will be released under<br>
<dd> a creative commons license. The
challenge is finding people<br>
<dd> to contribute quality entries
with little or no possibility<br>
<dd> of accolades in the guild of
biblical studies (and certainly<br>
<dd> no money!). The other project is
a collaboratively produced<br>
<dd> morphologically tagged Hebrew
text (see<br>
<dd>
<a href="http://www.OpenScriptures.org">www.OpenScriptures.org</a>
<<a href="http://www.openscriptures.org/" eudora="autourl">
http://www.OpenScriptures.org</a>>). For<br><br>
<dd> that we are looking at Django
and Pinax as the applications<br>
<dd> for collaborating on putting
together the data. For me, the<br>
<dd> purpose of this is to fill a
void of content for SWORD in<br>
<dd> order to serve the global
church.<br><br>
<dd> I notice that full-text lexicons
are part of the second phase<br>
<dd> of your plan. Is there any way
we can begin to collaborate on<br>
<dd> that? I am open to your
suggestions.<br><br>
<dd> Daniel<br><br>
<dd> On 4/21/2010 2:07 PM, Chris
Burrell wrote:<br><br>
<dd> *What is
Tyndale STEP?*<br><br>
<dd> Tyndale
STEP is an offline and online Java web<br>
<dd>
application which aims to make ancient texts and maps as<br>
<dd> well as
timeline data, genealogies, ... accessible to<br>
<dd>
everyone, scholar and non-scholar alike, so that the<br>
<dd> Bible is
illuminated by its full ancient context. [see<br>
<dd> roadmap
below]. Tyndale House will also distribute the<br>
<dd> online
version to pastors in the third world, who often<br>
<dd> cant
afford commercial Bible software.<br><br>
<dd> A wiki
page has been set up here:<br>
<dd>
<a href="http://crosswire.org/wiki/Frontends:TyndaleStep">
http://crosswire.org/wiki/Frontends:TyndaleStep</a> which has<br>
<dd> a lot
more information!<br><br>
<dd> *Who are
we looking for?*<br>
<dd> We need
lots of help!<br>
<dd> *Java
developers*: this code base is mainly in Java so<br>
<dd> we can
do with all the help we can get!<br>
<dd> *User
Interface designers*: there is currently a sketch<br>
<dd> of the
user interface, created more to prove a point. We<br>
<dd> need
proper guidance to make the software as user<br>
<dd> friendly
and rich as possible<br>
<dd> *Data
harvesters*: Tyndale House could do with a few<br>
<dd> extra
pairs of hands to helpcollate the data and make it<br>
<dd>
available to the wider CrossWire community<br><br>
<dd> *How do
I start?*<br>
<dd> Get in
touch!<br>
<dd> Read
through the wiki page:<br>
<dd>
<a href="http://crosswire.org/wiki/Frontends:TyndaleStep">
http://crosswire.org/wiki/Frontends:TyndaleStep</a><br>
<dd> Build
the code from:<br>
<dd>
<a href="http://crosswire.org/wiki/Frontends:TyndaleStep_Build_Environment">
http://crosswire.org/wiki/Frontends:TyndaleStep_Build_Environment</a><br>
<dd> Check
out our feature/bug repository:<br>
<dd>
<a href="http://crosswire.org/bugs/browse/TYNSTEP">
http://crosswire.org/bugs/browse/TYNSTEP</a><br>
<dd> Have a
look at the proof of concept sketches at<br>
<dd>
<a href="http://crosswire.org:8080/~chrisburrell/">
http://crosswire.org:8080/~chrisburrell/</a><br>
<dd>
<<a href="http://crosswire.org:8080/~chrisburrell/" eudora="autourl">
http://crosswire.org:8080/%7Echrisburrell/</a>> <<br>
<dd>
<a href="http://crosswire.org:8080/%7Echrisburrell/">
http://crosswire.org:8080/%7Echrisburrell/</a>> (including<br>
<dd>
timelines and interlinears on strong-tagged Bibles)<br><br>
<dd> Peruse
the blogs mentioned on the wiki to get a feel<br>
<dd> for the
data and programming<br><br>
<dd> As you
can see, theres plenty to do!<br><br>
<dd> *What
does the roadmap look like?*<br><br>
<dd> */1st
phase: build a multi-platform structure for<br>
<dd> standard
Bible-study tools:/*<br>
<dd> Bible
texts, including original languages, translations<br>
<dd> and
interlinears<br>
<dd>
Language aids, including lookup-dictionaries<br>
<dd>
concordance searches<br>
<dd>
History tools, including an expandable timeline with<br>
<dd>
scripture links<br>
<dd>
Dictionary articles, culled from various sources and edited<br>
<dd> */<br>
<dd> /*<br>
<dd> */2nd
phase: add detailed geographic, historic &<br>
<dd>
linguistic data/*<br>
<dd>
Gazetteer of all named places, with short articles and<br>
<dd> links to
pictures<br>
<dd>
Co-ordinates of identifiable places to GoogleEarth<br>
<dd> Map
overlays of high-ref 1:20,000 maps of pre-urbanised<br>
<dd>
Palestine<br>
<dd>
Flexible timelines which can be altered at key points<br>
<dd> of
uncertainty<br>
<dd>
Full-text lexicons linked to the lookup dictionaries in<br>
<dd> tagged
texts<br><br>
<dd> */3rd
phase: add translation aids and links to modern<br>
<dd>
publications/*<br>
<dd>
different possible translations for words and passages<br>
<dd>
differences in manuscripts, with evidence for each variant<br>
<dd>
expositions in modern and older commentaries, articles<br>
<dd> and
books<br><br>
<dd> */4th
phase: adds link to extra-biblical literature with<br>
<dd>
searching:/*<br>
<dd> search
other ancient literature for similar passages in<br>
<dd> a
similar context<br>
<dd> look
up Greek and Hebrew words in other ancient literature<br>
<dd> view
ancient texts with translations where possible<br><br>
<dd> These
tools will put centuries of research into the hands<br>
<dd> of
non-scholars. When the information is laid open like<br>
<dd> this, it
is easy to see that the Bible is well preserved<br>
<dd> and
translated, reflecting historical events in real<br>
<dd> places,
and dealing with issues current in the ancient<br>
<dd> and
modern work alike.<br><br>
<dd> If you
have any more questions or want to get involved,<br>
<dd> please
do let me know!<br>
<dd>
Chris<br><br>
<br>
<dd>
_______________________________________________<br>
<dd>
sword-devel mailing list:
<a href="mailto:sword-devel@crosswire.org">sword-devel@crosswire.org</a>
<br>
<dd>
<<a href="mailto:sword-devel@crosswire.org" eudora="autourl">
mailto:sword-devel@crosswire.org</a>><br><br>
<dd>
<a href="http://www.crosswire.org/mailman/listinfo/sword-devel">
http://www.crosswire.org/mailman/listinfo/sword-devel</a><br>
<dd>
Instructions to unsubscribe/change your settings at above<br>
<dd>
page<br><br>
<br><br>
<dd>_______________________________________________<br>
<dd>jsword-devel mailing list<br>
<dd><a href="mailto:jsword-devel@crosswire.org">
jsword-devel@crosswire.org</a><br>
<dd>
<a href="http://www.crosswire.org/mailman/listinfo/jsword-devel" eudora="autourl">
http://www.crosswire.org/mailman/listinfo/jsword-devel</a><br><br>
</dl>
</dl>
</dl></blockquote></body>
</html>