|
1 | | -<!-- $PostgreSQL: pgsql/doc/src/sgml/textsearch.sgml,v 1.29 2007/10/29 01:55:11 tgl Exp $ --> |
| 1 | +<!-- $PostgreSQL: pgsql/doc/src/sgml/textsearch.sgml,v 1.30 2007/11/05 15:55:53 mha Exp $ --> |
2 | 2 |
|
3 | 3 | <chapter id="textsearch"> |
4 | 4 | <title id="textsearch-title">Full Text Search</title> |
@@ -2060,7 +2060,7 @@ SELECT to_tsvector('english','in the list of stop words'); |
2060 | 2060 | 'list':3 'stop':5 'word':6 |
2061 | 2061 | </programlisting> |
2062 | 2062 |
|
2063 | | - Themising positions 1,2,4 are because of stop words. Ranks |
| 2063 | + Themissing positions 1,2,4 are because of stop words. Ranks |
2064 | 2064 | calculated for documents with and without stop words are quite different: |
2065 | 2065 |
|
2066 | 2066 | <programlisting> |
@@ -2542,7 +2542,7 @@ CREATE TEXT SEARCH DICTIONARY english_stem ( |
2542 | 2542 | <para> |
2543 | 2543 | A <application>Snowball</> dictionary recognizes everything, whether |
2544 | 2544 | or not it is able to simplify the word, so it should be placed |
2545 | | - at the end of the dictionary list. Itit useless to have it |
| 2545 | + at the end of the dictionary list. Itis useless to have it |
2546 | 2546 | before any other dictionary because a token will never pass through it to |
2547 | 2547 | the next dictionary. |
2548 | 2548 | </para> |
|