<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">You're not missing anything. These kind of problems are handled best by normalization.<div><br></div><div>In my earlier post I was suggesting that we normalize an hyphenated word, say "God-ward", to its parts and the whole: "God", "ward" and "Godward".</div><div><br></div><div>Solving backward compatibliity is fairly simple. Have a version number for the built index. If it doesn't match the expected value from the normalizer, the index is invalid and can't be used. JSword has the code for such a mechanism, but it hasn't been woven in. One could go deeper than a single coarse grain version number and have version numbers for each feature that is part of an index.</div><div><br></div><div>In Him,</div><div><span class="Apple-tab-span" style="white-space:pre"> </span>DM<br><div><div>On Mar 3, 2013, at 8:36 AM, Chris Burrell <<a href="mailto:chris@burrell.me.uk">chris@burrell.me.uk</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div dir="ltr">I still think normalisation of what is searched for would be good, in that it basically means the user sees the results that he is looking for.<div><br></div><div>I understand the concern for backwards compatibility and perhaps that means frontends should be able to turn this normalisation off. But looking ahead, for new front-ends, front-ends that can make rebuilding indexes part of the upgrade to a new version and for all new downloads of frontends, this has to be a benefit.</div>
<div><br></div><div>Not normalising, seems to me like perpetuating an existing problem into all new downloads from this day forth. Or am I missing something?</div><div>Chris</div><div><br></div></div><div class="gmail_extra">
<br><br><div class="gmail_quote">On 3 March 2013 12:53, Jonathan Morgan <span dir="ltr"><<a href="mailto:jonmmorgan@gmail.com" target="_blank">jonmmorgan@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Another possibly related normalisation problem which BPBible at least has an open issue about is Caesar vs. Cæsar. Theoretically I guess you want either search to match both forms. I don't know how Lucene etc. deals with this (if at all).<br>
<br>Jon<div class="HOEnZb"><div class="h5"><br><br><div class="gmail_quote">On Mon, Feb 25, 2013 at 2:48 AM, David Haslam <span dir="ltr"><<a href="mailto:dfhmch@googlemail.com" target="_blank">dfhmch@googlemail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
In the KJV module, if you want to search for [say] the hyphenated name<br>
"Maher–shalal–hash–baz", you first have to be aware that this module uses<br>
the ndash in place of the hyphen.<br>
<br>
btw. It's not so easy to enter the ndash from a keyboard, and probably even<br>
harder in an Android tablet or mobile.<br>
<br>
If you use ordinary hyphen/minus for the search key hyphen for this module,<br>
you don't find anything with "Exact phrase".<br>
If you use "Multi-word", you do find "Maher" highlighted in the found verse.<br>
(e.g. using Xiphos).<br>
<br>
For modules in general, however, the user cannot usually know in advance<br>
whether hyphenated words use the ndash, the hyphen or something else.<br>
<br>
Has anyone else looked into this aspect of the search feature?<br>
<br>
David<br>
<br>
<br>
<br>
<br>
<br>
--<br>
View this message in context: <a href="http://sword-dev.350566.n4.nabble.com/Searching-for-hyphenated-words-tp4652016.html" target="_blank">http://sword-dev.350566.n4.nabble.com/Searching-for-hyphenated-words-tp4652016.html</a><br>
Sent from the SWORD Dev mailing list archive at <a href="http://Nabble.com">Nabble.com</a>.<br>
<br>
_______________________________________________<br>
sword-devel mailing list: <a href="mailto:sword-devel@crosswire.org" target="_blank">sword-devel@crosswire.org</a><br>
<a href="http://www.crosswire.org/mailman/listinfo/sword-devel" target="_blank">http://www.crosswire.org/mailman/listinfo/sword-devel</a><br>
Instructions to unsubscribe/change your settings at above page</blockquote></div><br>
</div></div><br>_______________________________________________<br>
sword-devel mailing list: <a href="mailto:sword-devel@crosswire.org">sword-devel@crosswire.org</a><br>
<a href="http://www.crosswire.org/mailman/listinfo/sword-devel" target="_blank">http://www.crosswire.org/mailman/listinfo/sword-devel</a><br>
Instructions to unsubscribe/change your settings at above page<br></blockquote></div><br></div>
_______________________________________________<br>sword-devel mailing list: <a href="mailto:sword-devel@crosswire.org">sword-devel@crosswire.org</a><br><a href="http://www.crosswire.org/mailman/listinfo/sword-devel">http://www.crosswire.org/mailman/listinfo/sword-devel</a><br>Instructions to unsubscribe/change your settings at above page</blockquote></div><br></div></body></html>