<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Yes, BPBible is a work in progress, but for version 0.2, it looks
pretty good to me in Windows.<br>
<br>
I understand where you are coming from with regular expressions. I
don't use regular expressions either, but that's because for
sophisticated searches I use Libronix because the texts are tagged
morphologically and the Libronix Greek, Hebrew, and Aramaic search
dialogs build something akin to regular expressions for me. I haven't
tried doing this kind of searching in any of the Sword front-ends, but
the potential is there, especially with the MorphGNT module, which
includes both parsing and lemma tagging. Let's say you want to find all
aorist, 3rd person, singular forms of the verb αγαπαω (agapao, to love)
that also have θεος (theos, God) in the nominative case within three
words. Try to do that with a basic search (I haven't tried building a
regex to do that search, but I imagine you could build one to get you
close to that). Regular expressions represent exegetical potential, but
the average exegete won't take time to learn them. I am concerned about
exegetes in the developing world who can't afford Logos but want to do
more sophisticated morphological analysis. For myself, if the WLC ever
gets morphological tagging, I'd start trying to do regex searches just
to save myself the step of having to fire up my virtual machine and
open Logos. I would say that until MorphGNT makes it out of beta and
the WLC gets morphological and lemma tagging, this is not a big issue.
But down the road it could make Sword quite attractive for people
working in the biblical languages. <br>
<br>
Daniel<br>
<br>
Jonathan Morgan wrote:
<blockquote
cite="mid:f6aec790804302316l4cdfecefida31e64499af2dd7@mail.gmail.com"
type="cite">
<pre wrap="">On Thu, May 1, 2008 at 4:03 PM, Daniel Owens <a class="moz-txt-link-rfc2396E" href="mailto:dhowens@pmbx.net"><dhowens@pmbx.net></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap=""> I took a look at BPBible, and it is indeed fairly feature rich and pleasing
to the eye. I especially like the way it handles looking up dictionary
entries. I would use it regularly if:
Fonts could be set by language or module,
Bibles could be viewed in parallel, either BibleTime or BibleDesktop
fashion, and
and the Linux installation were a bit easier (I got stuck when trying to
install the swig bindings). The project has made a strong start. The search
dialog is pretty sharp, though average users aren't familiar with regular
expressions. A regular expression builder dialog would be fantastic. The
method that commentaries are linked to the Bible text is great.
</pre>
</blockquote>
<pre wrap=""><!---->
Bear in mind that it is still very much a work in progress, but
thankyou for the comments. I will agree that Linux installation may
be hard, and I'm sure that that will be addressed in some way in later
releases. However, I don't agree with the regular expression
suggestion. It is true that most users aren't familiar with regular
expressions. However, regular expressions aren't a feature that most
users will need to use. I understand regular expressions well, and
search the Bible frequently, and yet I have never had cause to use
regular expressions. I suspect that only people who understand
regular expressions well will actually want to use them. Most Bible
searches are satisfied by multi word or phrase search, which is quick
and easy and anyone who has used Google can understand.
Jon
_______________________________________________
sword-devel mailing list: <a class="moz-txt-link-abbreviated" href="mailto:sword-devel@crosswire.org">sword-devel@crosswire.org</a>
<a class="moz-txt-link-freetext" href="http://www.crosswire.org/mailman/listinfo/sword-devel">http://www.crosswire.org/mailman/listinfo/sword-devel</a>
Instructions to unsubscribe/change your settings at above page
</pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
PMBX license 1502
</pre>
</body>
</html>