>> If by backward compatibility, you mean that old indexes will still >> work as they always have, then backwards compatibility is being >> preserved (this is how I would interpret it). > > This is what I meant. The analyzer is used to tokenize both the text going > into the index and the search request. If both are not tokenized the same > there will be mismatches. > > Some examples: old index w/o stopwords and engine that preserves them. In > the following example IN is a stopword. > > Search a phrase w/ a stop word. "in Christ" will look for all soca > containing both "in" and "Christ" with the first immediatily preceding the > second. > > Search for the same but not as a phrase. The default action is to find all > verses that contain either word. This will find all verses with Christ and > none with In. This is the same as searching for IN OR CHRIST > > If the default is overridden to mean AND or the search is IN AND CHRIST then > no verses will be found.
You are correct. I wasn't thinking of the AND scenario (which is actually default in Xiphos simple search). In these cases, searching the old index would certainly not return the expected results. Matthew _______________________________________________ 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
