On Friday, May 10, 2024 10:21:19 AM EDT Troy A. Griffitts wrote: > Yes, we could add in some logic to call strongsPad during the search loop so > a Strongs entry in every Bible gets normalized before compare.
That would be amazing, and would, based on my understanding of the OSHB thread, help Xiphos as well. I haven't verified Xiphos behavior myself, but it sounds similar to the issues I'm having. > I haven't run into this so often because my front ends usually add this > feature as an interface by clicking on an existing word in a Bible with an > option "find other occurrences of this Greek word" and I search for the > Strongs number as it is formatted in that Bible. My strongs command does two things, 1) If given an arbitrary word, it checks if the module is a Greek or Hebrew lexicon, and, if so, searches it for the word. (If effect this is the same as using the search command with a lexicon selected) 2) If given a token starting with G or H, checks the module to see if it has Strong's Numbers, and, if so, searches the entity attributes for the given token. I'm sure I could add some logic to check the given module and adapt the token to fit, but that doesn't help the other issue I've found. When searching for, say, G11 in a module that isn't 0 padded, all occurrences of G11 are found, but so are all occurrences of G110, G1105, etc. Assuming that normalization of padding on the entity attributes adds padding to them so it's in the form of G0XXXX, that should cut down on the false matches significantly. _______________________________________________ sword-devel mailing list: sword-devel@crosswire.org http://crosswire.org/mailman/listinfo/sword-devel Instructions to unsubscribe/change your settings at above page
