[sword-devel] Strong's Numbers Standards

[Daniel Owens]

As a module creator, this has been a source of untold hours of 
frustration and experimentation in order to discover what works.

 From memory, the most widely supported format in practice is to have G 
or H followed by a padded number.

It would be ideal if all the front-ends supported the same format so 
modules would work the same way everywhere.

Daniel

On 9/28/17 7:11 AM, DM Smith wrote:
> I’m curious whether your question is as a module creator or otherwise. 
> Are you creating a Strong’s module or a module having Strong’s numbers?
>
> The KJV module uses Strong’s numbers of the form G975, that is, a G or 
> H followed by an unpadded number. That’s the current standard.
>
> There’s a new setting for dictionary modules having keys that 
> beginning with numbers: StrongsPadding=true|false
> When it is true, it will pad a key beginning with numbers with the 
> assumption that it follows the old logic of padded numbers.
>
> The reason for padded numbers is that keys are sorted by a strict 
> ascii text collation and the desire is for keys to be in numerical order.
>
> You can use ld2imp to dump a dictionary and examine its keys.
>
> A front end needs to normalize a search request the same as the module 
> it is searching against.
>
> I don’t know how SWORD does it but JSword examines an arbitrary key 
> from the Strong’s module and establishes a pattern based upon that. It 
> allows for keys to start with a G or H and be 0 padded or not. Then it 
> normalizes the search request according to that pattern.
>
> Hope this helps a bit,
> DM Smith
>
>> On Sep 27, 2017, at 2:12 PM, Gary Holmlund <gary.holmlund at gmail.com 
>> <mailto:gary.holmlund at gmail.com>> wrote:
>>
>> I don't see anywhere the document suggest not having the zeros. I do 
>> see several examples with zeros between the letter and the digits.
>>
>> H0776
>> H01961
>> H08414
>> H0922
>>
>> Even if the document had suggested no zeros, we have documents 
>> (MLStrong, Dodson) that do have these zeros. If I have "G32" how do I 
>> know to change it to "G0032" to lookup in these documents?
>>
>> Gary
>>
>>
>> On 09/27/2017 12:12 AM, Michael H wrote:
>>> STEP suggests that leading zeros do not belong in between the letter 
>>> and the digits.
>>>
>>> https://stepweb.atlassian.net/wiki/spaces/TYNSTEP/pages/36569098/OSIS+samples#OSISsamples-OSISofaBiblewithstrongnumbers(ESV) 
>>> <https://stepweb.atlassian.net/wiki/spaces/TYNSTEP/pages/36569098/OSIS+samples#OSISsamples-OSISofaBiblewithstrongnumbers%28ESV%29>
>>>
>>>
>>>
>>> On Tue, Sep 26, 2017 at 10:38 PM, Gary Holmlund <gary at holmlund.org 
>>> <mailto:gary at holmlund.org>> wrote:
>>>
>>>     I am trying to understand the various forms that Strong's
>>>     references can have. Let me explain with an example from
>>>     BibleTime when we hover over a word and automatically display
>>>     the Strong's reference text.
>>>
>>>     In the new testament (KJV and ESV2011) the Strong's reference
>>>     for "angel" is  "G32". In BibleTime the "G" is removed leaving
>>>     "32" as the reference to lookup. This works for StrongsGreek,
>>>     StringsRealGreek, and AbbottSmithStrongs. It does not work for
>>>     MLStrong and Dodson.
>>>
>>>     In the books StrongsGreek, StringsRealGreek, and
>>>     AbbottSmithStrongs the reference is "00032". In MLStrong and
>>>     Dodson the reference is "G0032". So, I find that "32" will work
>>>     as a key when the book reference is "00032",  but "32" or "G32"
>>>     won't work if the book reference is "G0032"
>>>
>>>     If I knew that Strong's references were either "Gnnnn" or
>>>     "nnnnn" I could pad zeros in the right place when a shorter
>>>     Strong's reference needs to be looked up. Or is there some other
>>>     method we can use?
>>>
>>>     PS. I am told that Xiphos has the same problem.
>>>
>>>     Gary Holmlund
>>>
>>>
>>>
>>>     _______________________________________________
>>>     sword-devel mailing list: sword-devel at crosswire.org
>>>     <mailto:sword-devel at crosswire.org>
>>>     http://www.crosswire.org/mailman/listinfo/sword-devel
>>>     <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
>>
>> _______________________________________________
>> 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