[sword-devel] Strong tagging and Septuagint

Troy A. Griffitts scribe at crosswire.org
Tue Feb 12 13:17:37 MST 2013


I understand the possible need for general facility, to indicate 
features and this is why we have the Feature=StrongsNumbers tag.

I also understand why this isn't straight forward the LXX.

But, I would say that this is an exception and one that doesn't warrant 
adding a new feature like:


The logic we all implement for this, if we need to know BEFORE look at 
the data, is something like,
if Feature=StrongsGreek then we expect have Greek Numbers in the NT, if 
an NT exists in the module and Hebrew Numbers in the OT, unless we're 
the LXX, then we have Greek Numbers in the OT.

There really are no other exceptions that I can think of that would 
warrant us all changing our code to look for two different Feature tags 
instead of the single instance.

Why again do you need to know before a user clicks on a Strong's 
number?  We are beginning to have modules with other lemma tags than 
simply Strongs, so you will need to look at the lemma type attribute 
when the user clicks to see what's available for lookup.  Granted, we 
probably want to standarize and add other Feature= option values for 
these new lemma types as well, so I'm not saying we shouldn't expand the 
list, but for this instance, to support Greek lookups in the OT for the 
LXX, I don't think the change is worth this single exception.

As an example, you can see the LXX doing greek lookups in the OT here:

(click on an LXX word)

I'm certainly open to hear and reconsider if you have a case you can't 
work around.


On 02/12/2013 04:08 PM, Chris Burrell wrote:
> Yes, but in this case, these are existing modules used with a new 
> front-end (with I'm guessing functionality that isn't yet available in 
> existing front-ends), hence the issue.
> Chris
> On 12 February 2013 14:52, David Haslam <dfhmch at googlemail.com 
> <mailto:dfhmch at googlemail.com>> wrote:
>     Regarding proposed new module configuration properties....
>     xulsword <http://code.google.com/p/xulsword/>   already makes use
>     of a few
>     extra properties in the conf files for modules made for that
>     front-end.
>     See note 2 in
>     http://crosswire.org/wiki/Module_Repositories#Institute_for_Bible_Translation
>     Even so, and also with some OSIS subtype attributes documented
>     elsewhere,
>     xulsword modules are wholly compatible with the SWORD API.
>     Other front-ends simply ignore these things.
>     David
>     --
>     View this message in context:
>     http://sword-dev.350566.n4.nabble.com/Strong-tagging-and-Septuagint-tp4651344p4651946.html
>     Sent from the SWORD Dev mailing list archive at Nabble.com.
>     _______________________________________________
>     sword-devel mailing list: sword-devel at crosswire.org
>     <mailto:sword-devel at crosswire.org>
>     http://www.crosswire.org/mailman/listinfo/sword-devel
>     Instructions to unsubscribe/change your settings at above page
> _______________________________________________
> sword-devel mailing list: sword-devel at crosswire.org
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.crosswire.org/pipermail/sword-devel/attachments/20130212/215d9ff0/attachment.html>

More information about the sword-devel mailing list