<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Hi Daniel,<br>
<br>
this is AWESOME! I'm interested in buying this when it becomes
available.<br>
<br>
Is there an official Sword release available that includes the
patch?<br>
<br>
Only the Windows and MacOS builds of BibleTime include Sword in
binary form. We don't have influence on the packaged version of
Sword in the various distributions. :(<br>
<br>
Best regards, mg<br>
<br>
Am 16.04.12 14:55, schrieb Daniel Owens:<br>
<span style="white-space: pre;">> I am preparing a module that
includes the Westminster Hebrew Morphology, the premier
morphological database for the Hebrew Bible. The Groves Center
will sell it at a reasonable price. This is a GIANT step forward
for SWORD in becoming a mature tool for study of the ancient
language texts.<br>
><br>
> By far the best offline front-end for this module is
BibleTime. However, the morphology codes are case-sensitive, and
Troy has worked out a fix in the engine (November 2011) to handle
case-sensitive lexicon keys. It works with BibleTool but not
BibleTime. It would be fantastic if the next BT release were built
to handle this and packaged with a more recent build of SWORD
because otherwise you get erroneous results in the mag window.<br>
><br>
> I can probably get the Groves Center to allow me to pass
along a partial module if there is a developer willing to try to
work on this.<br>
><br>
> Maybe this isn't something for 2.9.2, but I hope you will
work on it soon. I at least wanted to let you know about it.<br>
><br>
> Daniel<br>
><br>
> On 04/15/2012 02:04 PM, Jaak Ristioja wrote:</span><br>
<blockquote type="cite">Hi!<br>
<br>
BibleTime 2.9.1 was released on December 22 last year right before<br>
Christmas. Time to release 2.9.2 soon. Is there anything critical
left<br>
to fix for 2.9.2?<br>
<br>
Blessings!<br>
Jaak<br>
<br>
PS: Please also check for open bugs in the old "Bugs" tracker on
our<br>
SourceForge project page. It were ideal if that list of open bugs
became<br>
a list of closed bugs one fine day so we could archieve that
tracker<br>
for good.<br>
</blockquote>
<span style="white-space: pre;">>><br>
>> _______________________________________________<br>
>> bt-devel mailing list<br>
>> <a class="moz-txt-link-abbreviated" href="mailto:bt-devel@crosswire.org">bt-devel@crosswire.org</a><br>
>> <a class="moz-txt-link-freetext" href="http://www.crosswire.org/mailman/listinfo/bt-devel">http://www.crosswire.org/mailman/listinfo/bt-devel</a><br>
>><br>
><br>
> _______________________________________________<br>
> bt-devel mailing list<br>
> <a class="moz-txt-link-abbreviated" href="mailto:bt-devel@crosswire.org">bt-devel@crosswire.org</a><br>
> <a class="moz-txt-link-freetext" href="http://www.crosswire.org/mailman/listinfo/bt-devel">http://www.crosswire.org/mailman/listinfo/bt-devel</a><br>
></span><br>
<br>
</body>
</html>