The requirement is not that the search is normalized to nfc but rather that it is normalized the same as the index. This should not be a front end issue.
Btw it doesn’t matter how Hebrew is stored in the module. Indexing should normalize it to a form that is internal to the engine. — DM Smith From my phone. Brief. Weird autocorrections. > On Mar 22, 2018, at 5:22 AM, David Haslam <dfh...@protonmail.com> wrote: > > Dear all, > > Not all front-ends automatically normalize the search string to Unicode NFC. > e.g. > Eloquent does > Xiphos does not > The data is incomplete for this feature in the table in our wiki page. > https://wiki.crosswire.org/Choosing_a_SWORD_program#Search_and_Dictionary > > Please would other front-end app developers supply the missing information. > Thanks. > > Further thought: > For front-ends that also have an Advanced search feature, would it not be a > useful enhancement to have a tick box option for Search string normalization? > Then if we do make any Biblical Hebrew modules with custom normalization, > search could at least still work for the "corner cases" in Hebrew, providing > the user gave the proper input in the search box. > > cf. The source text for the WLC at tanach.us is not normalized to NFC, but > our module is. > I'll refrain from going into a lot more detail here. There's an issue in our > tracker that covers this. > > Best regards, > > David > > Sent with ProtonMail Secure Email. > > _______________________________________________ > sword-devel mailing list: sword-devel@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@crosswire.org http://www.crosswire.org/mailman/listinfo/sword-devel Instructions to unsubscribe/change your settings at above page
