Bug: Morph Query is case sensitive

Page 1 of 1 (5 items)
This post has 4 Replies | 2 Followers

Posts 25114
Forum MVP
Dave Hooton | Forum Activity | Posted: Tue, Oct 11 2016 3:06 PM

For example a Surface search for κυρίου omits Κυρίου (James 5:4)

It would have been easier to track if Save as Passage List worked (it crashed on one occasion). Perhaps the "Save as xxx" options should be greyed out if they will be non-functional.

Dave
===

Windows 10 & Android 8

Posts 2736
LogosEmployee
Philana R. Crouch | Forum Activity | Replied: Tue, Oct 11 2016 3:49 PM

Dave,

Can you post a screenshot of your Morph Query?

Thanks,

Philana

Posts 25114
Forum MVP
Dave Hooton | Forum Activity | Replied: Tue, Oct 11 2016 4:38 PM

SBLGNT returns the same 238 results, but they omit Jas 5:4 which is returned by a text search. The suggestions in Surface indicate sensitivity as both cases are displayed.

Dave
===

Windows 10 & Android 8

Posts 86
Scott Fleischman | Forum Activity | Replied: Wed, Oct 12 2016 1:59 PM

Right now surface matches are exact. It is on our list to add options for case insensitivity and different match levels for marks such as the text search has. See https://wiki.logos.com/Search_Matching_Commands

For now you can indicate all of the exact forms with separate tags.

Posts 25114
Forum MVP
Dave Hooton | Forum Activity | Replied: Fri, Oct 14 2016 5:03 AM

Scott Fleischman:
Right now surface matches are exact

As with Proximity previously, why give the Query different defaults/rules to the text search? My reason for the comparison was to validate the Morph Query result. Users will be confused with different results.

Dave
===

Windows 10 & Android 8

Page 1 of 1 (5 items) | RSS