<html>
<body>
Dear Daniel<br><br>
I was hoping to look at the possibility of adding a "Root"
field to the Strongs modules, so that people could do a search for
similar words. <br>
As a starting point I was going to find a programming way of identifying
clusters from Strong's own internal links to similar words, <br>
and then look through for obvious errors (that's the tricky bit!). <br>
It would be nice to make a distinction between "root" and
"lemma", but this would take more sophistication. <br><br>
Initially I just need a copy of the project at present (in XML or
similar) to see if the plan is feasible. <br>
If I get some sensible results, it looks like the best thing to do is to
send them to you for incorporation into the official module. <br>
Is that right? <br><br>
BTW the Strongs Greek v.1.4 still lists 5054 (teknwn) as derived from
5098. <br>
This should be derived from "5088". This is in error in all
online versions of Strongs<br>
This error led someone to publish a book last year saying that Jesus was
actually the son of a judge, and was a respected member of the
establishment, because 5098 is <i><u>timoria</u></i> from 5097;
vindication, i.e. (by implication) a penalty:--punishment. <br>
Its frightening what can happen as a result of bad OCR. <br><br>
David IB<br><br>
At 22:25 13/12/2010, Daniel Owens wrote:<br>
<blockquote type=cite class=cite cite="">On 12/13/2010 04:06 PM, Peter
von Kaehne wrote:<br>
<blockquote type=cite class=cite cite="">On 13/12/10 16:13, David Haslam
wrote:<br><br>
<blockquote type=cite class=cite cite="">If you wish to obtain the OSIS
source text for a module, then you'd need to<br>
contact the relevant CrossWire volunteer.</blockquote>The Strong modules
are created using TEI not OSIS.<br><br>
I am not sure (though Chris Little will know) if this :<br><br>
<a href="http://files.morphgnt.org/strongs-dictionary/" eudora="autourl">
http://files.morphgnt.org/strongs-dictionary/</a><br><br>
and our source is the same, but I would think nevertheless this is a<br>
quality source for TEI encoded Strongs.<br><br>
Another, interesting (though I think, quite sleepy) project is
here:<br><br>
<a href="http://www.textonline.org/wiki/Textonline.org:Current_events" eudora="autourl">
http://www.textonline.org/wiki/Textonline.org:Current_events</a><br><br>
Unfortunate the site appears to be in difficulties. The site uses a<br>
variant of SFM to encode which should be easily translatable into TEI
on<br>
completion.<br><br>
Peter<br>
</blockquote>Sleepy is a great way to describe our project at
textonline.org! I get to it after semesters close (which is right now for
us in America), and I need to chase down our provider to fix the site's
database! Hopefully when my dissertation is done I will make lots of
progress.<br><br>
Currently the effort in regard to Greek is essentially dormant. For
Hebrew, I am working on checking the glosses that you, David IB, obtained
from the OLB lexicon to make sure they conform to BDB and Strongs, thus
moving the source way from the OLB source and toward public domain
material. I am using WeSay, a program written by SIL to enable
collaboration in developing lexicons. The files are in LIFT XML and
housed at LanguageDepot.org. If you or someone you know would like to
contribute to the ongoing work, register there and let me know so I can
get you (or another) set up to contribute. WeSay uses Mercurial for
version control, but all the user does is click Send/Receive button in
WeSay. It is really user-friendly once it is set up. Once I get the
textonline.org site back up and running I will make sure the instructions
there are clear.<br><br>
But for Strongs, another source is at OpenScriptures.org. I think they
are working on perfecting a Strong's source in OSIS.<br><br>
Daniel<br><br>
_______________________________________________<br>
sword-devel mailing list: sword-devel@crosswire.org<br>
<a href="http://www.crosswire.org/mailman/listinfo/sword-devel" eudora="autourl">
http://www.crosswire.org/mailman/listinfo/sword-devel</a><br>
Instructions to unsubscribe/change your settings at above
page</blockquote></body>
</html>