The Ispell dictionary template supports morphological dictionaries, which can normalize many different linguistic forms of a word into the same lexeme. For example, an English Ispell dictionary can match all declensions and conjugations of the search term bank, e.g., banking, banked, banks, banks', and bank's.
The standard PostgreSQL distribution does not include any Ispell configuration files. Dictionaries for a large number of languages are available from Ispell. Also, some more modern dictionary file formats are supported \u2014 MySpell (OO < 2.0.1) and Hunspell (OO >= 2.0.2). A large list of dictionaries is available on the OpenOffice Wiki.
\nTo create an Ispell dictionary perform these steps:
\ndownload dictionary configuration files. OpenOffice extension files have the .oxt extension. It is necessary to extract .aff and .dic files, change extensions to .affix and .dict. For some dictionary files it is also needed to convert characters to the UTF-8 encoding with commands (for example, for a Norwegian language dictionary):
iconv -f ISO_8859-1 -t UTF-8 -o nn_no.affix nn_NO.aff\niconv -f ISO_8859-1 -t UTF-8 -o nn_no.dict nn_NO.dic\n
copy files to the $SHAREDIR/tsearch_data directory
load files into PostgreSQL with the following command:
\nCREATE TEXT SEARCH DICTIONARY english_hunspell (\n TEMPLATE = ispell,\n DictFile = en_us,\n AffFile = en_us,\n Stopwords = english);\n
Here, DictFile, AffFile, and StopWords specify the base names of the dictionary, affixes, and stop-words files. The stop-words file has the same format explained above for the simple dictionary type. The format of the other files is not specified here but is available from the above-mentioned web sites.
Ispell dictionaries usually recognize a limited set of words, so they should be followed by another broader dictionary; for example, a Snowball dictionary, which recognizes everything.
\nThe .affix file of Ispell has the following structure:
prefixes\nflag *A:\n . > RE # As in enter > reenter\nsuffixes\nflag T:\n E > ST # As in late > latest\n [^AEIOU]Y > -Y,IEST # As in dirty > dirtiest\n [AEIOU]Y > EST # As in gray > grayest\n [^EY] > EST # As in small > smallest\n\n
And the .dict file has the following structure:
lapse/ADGRS\nlard/DGRS\nlarge/PRTY\nlark/MRS\n\n
Format of the .dict file is:
basic_form/affix_class_name\n\n
In the .affix file every affix flag is described in the following format:
condition > [-stripping_letters,] adding_affix\n\n
Here, condition has a format similar to the format of regular expressions. It can use groupings [...] and [^...]. For example, [AEIOU]Y means that the last letter of the word is \"y\" and the penultimate letter is \"a\", \"e\", \"i\", \"o\" or \"u\". [^EY] means that the last letter is neither \"e\" nor \"y\".
Ispell dictionaries support splitting compound words; a useful feature. Notice that the affix file should specify a special flag using the compoundwords controlled statement that marks dictionary words that can participate in compound formation:
compoundwords controlled z\n\n
Here are some examples for the Norwegian language:
\nSELECT ts_lexize('norwegian_ispell', 'overbuljongterningpakkmesterassistent');\n {over,buljong,terning,pakk,mester,assistent}\nSELECT ts_lexize('norwegian_ispell', 'sjokoladefabrikk');\n {sjokoladefabrikk,sjokolade,fabrikk}\n\nMySpell format is a subset of Hunspell. The .affix file of Hunspell has the following structure:
PFX A Y 1\nPFX A 0 re .\nSFX T N 4\nSFX T 0 st e\nSFX T y iest [^aeiou]y\nSFX T 0 est [aeiou]y\nSFX T 0 est [^ey]\n\n
The first line of an affix class is the header. Fields of an affix rules are listed after the header:
\nparameter name (PFX or SFX)
\nflag (name of the affix class)
\nstripping characters from beginning (at prefix) or end (at suffix) of the word
\nadding affix
\ncondition that has a format similar to the format of regular expressions.
\nThe .dict file looks like the .dict file of Ispell:
larder/M\nlardy/RT\nlarge/RSPMYT\nlargehearted\n\n
MySpell does not support compound words. Hunspell has sophisticated support for compound words. At present, PostgreSQL implements only the basic compound word operations of Hunspell.
\nThe Ispell dictionary template supports morphological dictionaries, which can normalize many different linguistic forms of a word into the same lexeme. For example, an English Ispell dictionary can match all declensions and conjugations of the search term bank, e.g., banking, banked, banks, banks', and bank's.
The standard PostgreSQL distribution does not include any Ispell configuration files. Dictionaries for a large number of languages are available from Ispell. Also, some more modern dictionary file formats are supported \u2014 MySpell (OO < 2.0.1) and Hunspell (OO >= 2.0.2). A large list of dictionaries is available on the OpenOffice Wiki.
\nTo create an Ispell dictionary perform these steps:
\ndownload dictionary configuration files. OpenOffice extension files have the .oxt extension. It is necessary to extract .aff and .dic files, change extensions to .affix and .dict. For some dictionary files it is also needed to convert characters to the UTF-8 encoding with commands (for example, for a Norwegian language dictionary):
iconv -f ISO_8859-1 -t UTF-8 -o nn_no.affix nn_NO.aff\niconv -f ISO_8859-1 -t UTF-8 -o nn_no.dict nn_NO.dic\n\n
copy files to the $SHAREDIR/tsearch_data directory
load files into PostgreSQL with the following command:
\nCREATE TEXT SEARCH DICTIONARY english_hunspell (\n TEMPLATE = ispell,\n DictFile = en_us,\n AffFile = en_us,\n Stopwords = english);\n\n
Here, DictFile, AffFile, and StopWords specify the base names of the dictionary, affixes, and stop-words files. The stop-words file has the same format explained above for the simple dictionary type. The format of the other files is not specified here but is available from the above-mentioned web sites.
Ispell dictionaries usually recognize a limited set of words, so they should be followed by another broader dictionary; for example, a Snowball dictionary, which recognizes everything.
\nThe .affix file of Ispell has the following structure:
prefixes\nflag *A:\n . > RE # As in enter > reenter\nsuffixes\nflag T:\n E > ST # As in late > latest\n [^AEIOU]Y > -Y,IEST # As in dirty > dirtiest\n [AEIOU]Y > EST # As in gray > grayest\n [^EY] > EST # As in small > smallest\n\n
And the .dict file has the following structure:
lapse/ADGRS\nlard/DGRS\nlarge/PRTY\nlark/MRS\n\n
Format of the .dict file is:
basic_form/affix_class_name\n\n
In the .affix file every affix flag is described in the following format:
condition > [-stripping_letters,] adding_affix\n\n
Here, condition has a format similar to the format of regular expressions. It can use groupings [...] and [^...]. For example, [AEIOU]Y means that the last letter of the word is \"y\" and the penultimate letter is \"a\", \"e\", \"i\", \"o\" or \"u\". [^EY] means that the last letter is neither \"e\" nor \"y\".
Ispell dictionaries support splitting compound words; a useful feature. Notice that the affix file should specify a special flag using the compoundwords controlled statement that marks dictionary words that can participate in compound formation:
compoundwords controlled z\n\n
Here are some examples for the Norwegian language:
\nSELECT ts_lexize('norwegian_ispell', 'overbuljongterningpakkmesterassistent');\n {over,buljong,terning,pakk,mester,assistent}\nSELECT ts_lexize('norwegian_ispell', 'sjokoladefabrikk');\n {sjokoladefabrikk,sjokolade,fabrikk}\n\nMySpell format is a subset of Hunspell. The .affix file of Hunspell has the following structure:
PFX A Y 1\nPFX A 0 re .\nSFX T N 4\nSFX T 0 st e\nSFX T y iest [^aeiou]y\nSFX T 0 est [aeiou]y\nSFX T 0 est [^ey]\n\n
The first line of an affix class is the header. Fields of an affix rules are listed after the header:
\nparameter name (PFX or SFX)
\nflag (name of the affix class)
\nstripping characters from beginning (at prefix) or end (at suffix) of the word
\nadding affix
\ncondition that has a format similar to the format of regular expressions.
\nThe .dict file looks like the .dict file of Ispell:
larder/M\nlardy/RT\nlarge/RSPMYT\nlargehearted\n\n
MySpell does not support compound words. Hunspell has sophisticated support for compound words. At present, PostgreSQL implements only the basic compound word operations of Hunspell.
\nThe Ispell dictionary template supports morphological dictionaries, which can normalize many different linguistic forms of a word into the same lexeme. For example, an English Ispell dictionary can match all declensions and conjugations of the search term bank, e.g., banking, banked, banks, banks', and bank's.
The standard PostgreSQL distribution does not include any Ispell configuration files. Dictionaries for a large number of languages are available from Ispell. Also, some more modern dictionary file formats are supported \u2014 MySpell (OO < 2.0.1) and Hunspell (OO >= 2.0.2). A large list of dictionaries is available on the OpenOffice Wiki.
\nTo create an Ispell dictionary perform these steps:
\ndownload dictionary configuration files. OpenOffice extension files have the .oxt extension. It is necessary to extract .aff and .dic files, change extensions to .affix and .dict. For some dictionary files it is also needed to convert characters to the UTF-8 encoding with commands (for example, for a Norwegian language dictionary):
iconv -f ISO_8859-1 -t UTF-8 -o nn_no.affix nn_NO.aff\niconv -f ISO_8859-1 -t UTF-8 -o nn_no.dict nn_NO.dic\n\n
copy files to the $SHAREDIR/tsearch_data directory
load files into PostgreSQL with the following command:
\nCREATE TEXT SEARCH DICTIONARY english_hunspell (\n TEMPLATE = ispell,\n DictFile = en_us,\n AffFile = en_us,\n Stopwords = english);\n\n
Here, DictFile, AffFile, and StopWords specify the base names of the dictionary, affixes, and stop-words files. The stop-words file has the same format explained above for the simple dictionary type. The format of the other files is not specified here but is available from the above-mentioned web sites.
Ispell dictionaries usually recognize a limited set of words, so they should be followed by another broader dictionary; for example, a Snowball dictionary, which recognizes everything.
\nThe .affix file of Ispell has the following structure:
prefixes\nflag *A:\n . > RE # As in enter > reenter\nsuffixes\nflag T:\n E > ST # As in late > latest\n [^AEIOU]Y > -Y,IEST # As in dirty > dirtiest\n [AEIOU]Y > EST # As in gray > grayest\n [^EY] > EST # As in small > smallest\n\n
And the .dict file has the following structure:
lapse/ADGRS\nlard/DGRS\nlarge/PRTY\nlark/MRS\n\n
Format of the .dict file is:
basic_form/affix_class_name\n\n
In the .affix file every affix flag is described in the following format:
condition > [-stripping_letters,] adding_affix\n\n
Here, condition has a format similar to the format of regular expressions. It can use groupings [...] and [^...]. For example, [AEIOU]Y means that the last letter of the word is \"y\" and the penultimate letter is \"a\", \"e\", \"i\", \"o\" or \"u\". [^EY] means that the last letter is neither \"e\" nor \"y\".
Ispell dictionaries support splitting compound words; a useful feature. Notice that the affix file should specify a special flag using the compoundwords controlled statement that marks dictionary words that can participate in compound formation:
compoundwords controlled z\n\n
Here are some examples for the Norwegian language:
\nSELECT ts_lexize('norwegian_ispell', 'overbuljongterningpakkmesterassistent');\n {over,buljong,terning,pakk,mester,assistent}\nSELECT ts_lexize('norwegian_ispell', 'sjokoladefabrikk');\n {sjokoladefabrikk,sjokolade,fabrikk}\n\nMySpell format is a subset of Hunspell. The .affix file of Hunspell has the following structure:
PFX A Y 1\nPFX A 0 re .\nSFX T N 4\nSFX T 0 st e\nSFX T y iest [^aeiou]y\nSFX T 0 est [aeiou]y\nSFX T 0 est [^ey]\n\n
The first line of an affix class is the header. Fields of an affix rules are listed after the header:
\nparameter name (PFX or SFX)
\nflag (name of the affix class)
\nstripping characters from beginning (at prefix) or end (at suffix) of the word
\nadding affix
\ncondition that has a format similar to the format of regular expressions.
\nThe .dict file looks like the .dict file of Ispell:
larder/M\nlardy/RT\nlarge/RSPMYT\nlargehearted\n\n
MySpell does not support compound words. Hunspell has sophisticated support for compound words. At present, PostgreSQL implements only the basic compound word operations of Hunspell.
\nThe Ispell dictionary template supports morphological dictionaries, which can normalize many different linguistic forms of a word into the same lexeme. For example, an English Ispell dictionary can match all declensions and conjugations of the search term bank, e.g., banking, banked, banks, banks', and bank's.
The standard PostgreSQL distribution does not include any Ispell configuration files. Dictionaries for a large number of languages are available from Ispell. Also, some more modern dictionary file formats are supported \u2014 MySpell (OO < 2.0.1) and Hunspell (OO >= 2.0.2). A large list of dictionaries is available on the OpenOffice Wiki.
\nTo create an Ispell dictionary perform these steps:
\ndownload dictionary configuration files. OpenOffice extension files have the .oxt extension. It is necessary to extract .aff and .dic files, change extensions to .affix and .dict. For some dictionary files it is also needed to convert characters to the UTF-8 encoding with commands (for example, for a Norwegian language dictionary):
iconv -f ISO_8859-1 -t UTF-8 -o nn_no.affix nn_NO.aff\niconv -f ISO_8859-1 -t UTF-8 -o nn_no.dict nn_NO.dic\n\n
copy files to the $SHAREDIR/tsearch_data directory
load files into PostgreSQL with the following command:
\nCREATE TEXT SEARCH DICTIONARY english_hunspell (\n TEMPLATE = ispell,\n DictFile = en_us,\n AffFile = en_us,\n Stopwords = english);\n\n
Here, DictFile, AffFile, and StopWords specify the base names of the dictionary, affixes, and stop-words files. The stop-words file has the same format explained above for the simple dictionary type. The format of the other files is not specified here but is available from the above-mentioned web sites.
Ispell dictionaries usually recognize a limited set of words, so they should be followed by another broader dictionary; for example, a Snowball dictionary, which recognizes everything.
\nThe .affix file of Ispell has the following structure:
prefixes\nflag *A:\n . > RE # As in enter > reenter\nsuffixes\nflag T:\n E > ST # As in late > latest\n [^AEIOU]Y > -Y,IEST # As in dirty > dirtiest\n [AEIOU]Y > EST # As in gray > grayest\n [^EY] > EST # As in small > smallest\n\n
And the .dict file has the following structure:
lapse/ADGRS\nlard/DGRS\nlarge/PRTY\nlark/MRS\n\n
Format of the .dict file is:
basic_form/affix_class_name\n\n
In the .affix file every affix flag is described in the following format:
condition > [-stripping_letters,] adding_affix\n\n
Here, condition has a format similar to the format of regular expressions. It can use groupings [...] and [^...]. For example, [AEIOU]Y means that the last letter of the word is \"y\" and the penultimate letter is \"a\", \"e\", \"i\", \"o\" or \"u\". [^EY] means that the last letter is neither \"e\" nor \"y\".
Ispell dictionaries support splitting compound words; a useful feature. Notice that the affix file should specify a special flag using the compoundwords controlled statement that marks dictionary words that can participate in compound formation:
compoundwords controlled z\n\n
Here are some examples for the Norwegian language:
\nSELECT ts_lexize('norwegian_ispell', 'overbuljongterningpakkmesterassistent');\n {over,buljong,terning,pakk,mester,assistent}\nSELECT ts_lexize('norwegian_ispell', 'sjokoladefabrikk');\n {sjokoladefabrikk,sjokolade,fabrikk}\n\nMySpell format is a subset of Hunspell. The .affix file of Hunspell has the following structure:
PFX A Y 1\nPFX A 0 re .\nSFX T N 4\nSFX T 0 st e\nSFX T y iest [^aeiou]y\nSFX T 0 est [aeiou]y\nSFX T 0 est [^ey]\n\n
The first line of an affix class is the header. Fields of an affix rules are listed after the header:
\nparameter name (PFX or SFX)
\nflag (name of the affix class)
\nstripping characters from beginning (at prefix) or end (at suffix) of the word
\nadding affix
\ncondition that has a format similar to the format of regular expressions.
\nThe .dict file looks like the .dict file of Ispell:
larder/M\nlardy/RT\nlarge/RSPMYT\nlargehearted\n\n
MySpell does not support compound words. Hunspell has sophisticated support for compound words. At present, PostgreSQL implements only the basic compound word operations of Hunspell.
\nThe Ispell dictionary template supports morphological dictionaries, which can normalize many different linguistic forms of a word into the same lexeme. For example, an English Ispell dictionary can match all declensions and conjugations of the search term bank, e.g., banking, banked, banks, banks', and bank's.
The standard PostgreSQL distribution does not include any Ispell configuration files. Dictionaries for a large number of languages are available from Ispell. Also, some more modern dictionary file formats are supported \u2014 MySpell (OO < 2.0.1) and Hunspell (OO >= 2.0.2). A large list of dictionaries is available on the OpenOffice Wiki.
\nTo create an Ispell dictionary perform these steps:
\ndownload dictionary configuration files. OpenOffice extension files have the .oxt extension. It is necessary to extract .aff and .dic files, change extensions to .affix and .dict. For some dictionary files it is also needed to convert characters to the UTF-8 encoding with commands (for example, for a Norwegian language dictionary):
iconv -f ISO_8859-1 -t UTF-8 -o nn_no.affix nn_NO.aff\niconv -f ISO_8859-1 -t UTF-8 -o nn_no.dict nn_NO.dic\n\n
copy files to the $SHAREDIR/tsearch_data directory
load files into PostgreSQL with the following command:
\nCREATE TEXT SEARCH DICTIONARY english_hunspell (\n TEMPLATE = ispell,\n DictFile = en_us,\n AffFile = en_us,\n Stopwords = english);\n\n
Here, DictFile, AffFile, and StopWords specify the base names of the dictionary, affixes, and stop-words files. The stop-words file has the same format explained above for the simple dictionary type. The format of the other files is not specified here but is available from the above-mentioned web sites.
Ispell dictionaries usually recognize a limited set of words, so they should be followed by another broader dictionary; for example, a Snowball dictionary, which recognizes everything.
\nThe .affix file of Ispell has the following structure:
prefixes\nflag *A:\n . > RE # As in enter > reenter\nsuffixes\nflag T:\n E > ST # As in late > latest\n [^AEIOU]Y > -Y,IEST # As in dirty > dirtiest\n [AEIOU]Y > EST # As in gray > grayest\n [^EY] > EST # As in small > smallest\n\n
And the .dict file has the following structure:
lapse/ADGRS\nlard/DGRS\nlarge/PRTY\nlark/MRS\n\n
Format of the .dict file is:
basic_form/affix_class_name\n\n
In the .affix file every affix flag is described in the following format:
condition > [-stripping_letters,] adding_affix\n\n
Here, condition has a format similar to the format of regular expressions. It can use groupings [...] and [^...]. For example, [AEIOU]Y means that the last letter of the word is \"y\" and the penultimate letter is \"a\", \"e\", \"i\", \"o\" or \"u\". [^EY] means that the last letter is neither \"e\" nor \"y\".
Ispell dictionaries support splitting compound words; a useful feature. Notice that the affix file should specify a special flag using the compoundwords controlled statement that marks dictionary words that can participate in compound formation:
compoundwords controlled z\n\n
Here are some examples for the Norwegian language:
\nSELECT ts_lexize('norwegian_ispell', 'overbuljongterningpakkmesterassistent');\n {over,buljong,terning,pakk,mester,assistent}\nSELECT ts_lexize('norwegian_ispell', 'sjokoladefabrikk');\n {sjokoladefabrikk,sjokolade,fabrikk}\n\nMySpell format is a subset of Hunspell. The .affix file of Hunspell has the following structure:
PFX A Y 1\nPFX A 0 re .\nSFX T N 4\nSFX T 0 st e\nSFX T y iest [^aeiou]y\nSFX T 0 est [aeiou]y\nSFX T 0 est [^ey]\n\n
The first line of an affix class is the header. Fields of an affix rules are listed after the header:
\nparameter name (PFX or SFX)
\nflag (name of the affix class)
\nstripping characters from beginning (at prefix) or end (at suffix) of the word
\nadding affix
\ncondition that has a format similar to the format of regular expressions.
\nThe .dict file looks like the .dict file of Ispell:
larder/M\nlardy/RT\nlarge/RSPMYT\nlargehearted\n\n
MySpell does not support compound words. Hunspell has sophisticated support for compound words. At present, PostgreSQL implements only the basic compound word operations of Hunspell.
\nThe Ispell dictionary template supports morphological dictionaries, which can normalize many different linguistic forms of a word into the same lexeme. For example, an English Ispell dictionary can match all declensions and conjugations of the search term bank, e.g., banking, banked, banks, banks', and bank's.
The standard PostgreSQL distribution does not include any Ispell configuration files. Dictionaries for a large number of languages are available from Ispell. Also, some more modern dictionary file formats are supported \u2014 MySpell (OO < 2.0.1) and Hunspell (OO >= 2.0.2). A large list of dictionaries is available on the OpenOffice Wiki.
\nTo create an Ispell dictionary perform these steps:
\ndownload dictionary configuration files. OpenOffice extension files have the .oxt extension. It is necessary to extract .aff and .dic files, change extensions to .affix and .dict. For some dictionary files it is also needed to convert characters to the UTF-8 encoding with commands (for example, for a Norwegian language dictionary):
iconv -f ISO_8859-1 -t UTF-8 -o nn_no.affix nn_NO.aff\niconv -f ISO_8859-1 -t UTF-8 -o nn_no.dict nn_NO.dic\n\n
copy files to the $SHAREDIR/tsearch_data directory
load files into PostgreSQL with the following command:
\nCREATE TEXT SEARCH DICTIONARY english_hunspell (\n TEMPLATE = ispell,\n DictFile = en_us,\n AffFile = en_us,\n Stopwords = english);\n\n
Here, DictFile, AffFile, and StopWords specify the base names of the dictionary, affixes, and stop-words files. The stop-words file has the same format explained above for the simple dictionary type. The format of the other files is not specified here but is available from the above-mentioned web sites.
Ispell dictionaries usually recognize a limited set of words, so they should be followed by another broader dictionary; for example, a Snowball dictionary, which recognizes everything.
\nThe .affix file of Ispell has the following structure:
prefixes\nflag *A:\n . > RE # As in enter > reenter\nsuffixes\nflag T:\n E > ST # As in late > latest\n [^AEIOU]Y > -Y,IEST # As in dirty > dirtiest\n [AEIOU]Y > EST # As in gray > grayest\n [^EY] > EST # As in small > smallest\n\n
And the .dict file has the following structure:
lapse/ADGRS\nlard/DGRS\nlarge/PRTY\nlark/MRS\n\n
Format of the .dict file is:
basic_form/affix_class_name\n\n
In the .affix file every affix flag is described in the following format:
condition > [-stripping_letters,] adding_affix\n\n
Here, condition has a format similar to the format of regular expressions. It can use groupings [...] and [^...]. For example, [AEIOU]Y means that the last letter of the word is \"y\" and the penultimate letter is \"a\", \"e\", \"i\", \"o\" or \"u\". [^EY] means that the last letter is neither \"e\" nor \"y\".
Ispell dictionaries support splitting compound words; a useful feature. Notice that the affix file should specify a special flag using the compoundwords controlled statement that marks dictionary words that can participate in compound formation:
compoundwords controlled z\n\n
Here are some examples for the Norwegian language:
\nSELECT ts_lexize('norwegian_ispell', 'overbuljongterningpakkmesterassistent');\n {over,buljong,terning,pakk,mester,assistent}\nSELECT ts_lexize('norwegian_ispell', 'sjokoladefabrikk');\n {sjokoladefabrikk,sjokolade,fabrikk}\n\nMySpell format is a subset of Hunspell. The .affix file of Hunspell has the following structure:
PFX A Y 1\nPFX A 0 re .\nSFX T N 4\nSFX T 0 st e\nSFX T y iest [^aeiou]y\nSFX T 0 est [aeiou]y\nSFX T 0 est [^ey]\n\n
The first line of an affix class is the header. Fields of an affix rules are listed after the header:
\nparameter name (PFX or SFX)
\nflag (name of the affix class)
\nstripping characters from beginning (at prefix) or end (at suffix) of the word
\nadding affix
\ncondition that has a format similar to the format of regular expressions.
\nThe .dict file looks like the .dict file of Ispell:
larder/M\nlardy/RT\nlarge/RSPMYT\nlargehearted\n\n
MySpell does not support compound words. Hunspell has sophisticated support for compound words. At present, PostgreSQL implements only the basic compound word operations of Hunspell.
\nThe Ispell dictionary template supports morphological dictionaries, which can normalize many different linguistic forms of a word into the same lexeme. For example, an English Ispell dictionary can match all declensions and conjugations of the search term bank, e.g., banking, banked, banks, banks', and bank's.
The standard PostgreSQL distribution does not include any Ispell configuration files. Dictionaries for a large number of languages are available from Ispell. Also, some more modern dictionary file formats are supported \u2014 MySpell (OO < 2.0.1) and Hunspell (OO >= 2.0.2). A large list of dictionaries is available on the OpenOffice Wiki.
\nTo create an Ispell dictionary perform these steps:
\ndownload dictionary configuration files. OpenOffice extension files have the .oxt extension. It is necessary to extract .aff and .dic files, change extensions to .affix and .dict. For some dictionary files it is also needed to convert characters to the UTF-8 encoding with commands (for example, for a Norwegian language dictionary):
iconv -f ISO_8859-1 -t UTF-8 -o nn_no.affix nn_NO.aff\niconv -f ISO_8859-1 -t UTF-8 -o nn_no.dict nn_NO.dic\n\n
copy files to the $SHAREDIR/tsearch_data directory
load files into PostgreSQL with the following command:
\nCREATE TEXT SEARCH DICTIONARY english_hunspell (\n TEMPLATE = ispell,\n DictFile = en_us,\n AffFile = en_us,\n Stopwords = english);\n\n
Here, DictFile, AffFile, and StopWords specify the base names of the dictionary, affixes, and stop-words files. The stop-words file has the same format explained above for the simple dictionary type. The format of the other files is not specified here but is available from the above-mentioned web sites.
Ispell dictionaries usually recognize a limited set of words, so they should be followed by another broader dictionary; for example, a Snowball dictionary, which recognizes everything.
\nThe .affix file of Ispell has the following structure:
prefixes\nflag *A:\n . > RE # As in enter > reenter\nsuffixes\nflag T:\n E > ST # As in late > latest\n [^AEIOU]Y > -Y,IEST # As in dirty > dirtiest\n [AEIOU]Y > EST # As in gray > grayest\n [^EY] > EST # As in small > smallest\n\n
And the .dict file has the following structure:
lapse/ADGRS\nlard/DGRS\nlarge/PRTY\nlark/MRS\n\n
Format of the .dict file is:
basic_form/affix_class_name\n\n
In the .affix file every affix flag is described in the following format:
condition > [-stripping_letters,] adding_affix\n\n
Here, condition has a format similar to the format of regular expressions. It can use groupings [...] and [^...]. For example, [AEIOU]Y means that the last letter of the word is \"y\" and the penultimate letter is \"a\", \"e\", \"i\", \"o\" or \"u\". [^EY] means that the last letter is neither \"e\" nor \"y\".
Ispell dictionaries support splitting compound words; a useful feature. Notice that the affix file should specify a special flag using the compoundwords controlled statement that marks dictionary words that can participate in compound formation:
compoundwords controlled z\n\n
Here are some examples for the Norwegian language:
\nSELECT ts_lexize('norwegian_ispell', 'overbuljongterningpakkmesterassistent');\n {over,buljong,terning,pakk,mester,assistent}\nSELECT ts_lexize('norwegian_ispell', 'sjokoladefabrikk');\n {sjokoladefabrikk,sjokolade,fabrikk}\n\nMySpell format is a subset of Hunspell. The .affix file of Hunspell has the following structure:
PFX A Y 1\nPFX A 0 re .\nSFX T N 4\nSFX T 0 st e\nSFX T y iest [^aeiou]y\nSFX T 0 est [aeiou]y\nSFX T 0 est [^ey]\n\n
The first line of an affix class is the header. Fields of an affix rules are listed after the header:
\nparameter name (PFX or SFX)
\nflag (name of the affix class)
\nstripping characters from beginning (at prefix) or end (at suffix) of the word
\nadding affix
\ncondition that has a format similar to the format of regular expressions.
\nThe .dict file looks like the .dict file of Ispell:
larder/M\nlardy/RT\nlarge/RSPMYT\nlargehearted\n\n
MySpell does not support compound words. Hunspell has sophisticated support for compound words. At present, PostgreSQL implements only the basic compound word operations of Hunspell.
\nThe Ispell dictionary template supports morphological dictionaries, which can normalize many different linguistic forms of a word into the same lexeme. For example, an English Ispell dictionary can match all declensions and conjugations of the search term bank, e.g., banking, banked, banks, banks', and bank's.
The standard PostgreSQL distribution does not include any Ispell configuration files. Dictionaries for a large number of languages are available from Ispell. Also, some more modern dictionary file formats are supported \u2014 MySpell (OO < 2.0.1) and Hunspell (OO >= 2.0.2). A large list of dictionaries is available on the OpenOffice Wiki.
\nTo create an Ispell dictionary perform these steps:
\ndownload dictionary configuration files. OpenOffice extension files have the .oxt extension. It is necessary to extract .aff and .dic files, change extensions to .affix and .dict. For some dictionary files it is also needed to convert characters to the UTF-8 encoding with commands (for example, for a Norwegian language dictionary):
iconv -f ISO_8859-1 -t UTF-8 -o nn_no.affix nn_NO.aff\niconv -f ISO_8859-1 -t UTF-8 -o nn_no.dict nn_NO.dic\n\n
copy files to the $SHAREDIR/tsearch_data directory
load files into PostgreSQL with the following command:
\nCREATE TEXT SEARCH DICTIONARY english_hunspell (\n TEMPLATE = ispell,\n DictFile = en_us,\n AffFile = en_us,\n Stopwords = english);\n\n
Here, DictFile, AffFile, and StopWords specify the base names of the dictionary, affixes, and stop-words files. The stop-words file has the same format explained above for the simple dictionary type. The format of the other files is not specified here but is available from the above-mentioned web sites.
Ispell dictionaries usually recognize a limited set of words, so they should be followed by another broader dictionary; for example, a Snowball dictionary, which recognizes everything.
\nThe .affix file of Ispell has the following structure:
prefixes\nflag *A:\n . > RE # As in enter > reenter\nsuffixes\nflag T:\n E > ST # As in late > latest\n [^AEIOU]Y > -Y,IEST # As in dirty > dirtiest\n [AEIOU]Y > EST # As in gray > grayest\n [^EY] > EST # As in small > smallest\n\n
And the .dict file has the following structure:
lapse/ADGRS\nlard/DGRS\nlarge/PRTY\nlark/MRS\n\n
Format of the .dict file is:
basic_form/affix_class_name\n\n
In the .affix file every affix flag is described in the following format:
condition > [-stripping_letters,] adding_affix\n\n
Here, condition has a format similar to the format of regular expressions. It can use groupings [...] and [^...]. For example, [AEIOU]Y means that the last letter of the word is \"y\" and the penultimate letter is \"a\", \"e\", \"i\", \"o\" or \"u\". [^EY] means that the last letter is neither \"e\" nor \"y\".
Ispell dictionaries support splitting compound words; a useful feature. Notice that the affix file should specify a special flag using the compoundwords controlled statement that marks dictionary words that can participate in compound formation:
compoundwords controlled z\n\n
Here are some examples for the Norwegian language:
\nSELECT ts_lexize('norwegian_ispell', 'overbuljongterningpakkmesterassistent');\n {over,buljong,terning,pakk,mester,assistent}\nSELECT ts_lexize('norwegian_ispell', 'sjokoladefabrikk');\n {sjokoladefabrikk,sjokolade,fabrikk}\n\nMySpell format is a subset of Hunspell. The .affix file of Hunspell has the following structure:
PFX A Y 1\nPFX A 0 re .\nSFX T N 4\nSFX T 0 st e\nSFX T y iest [^aeiou]y\nSFX T 0 est [aeiou]y\nSFX T 0 est [^ey]\n\n
The first line of an affix class is the header. Fields of an affix rules are listed after the header:
\nparameter name (PFX or SFX)
\nflag (name of the affix class)
\nstripping characters from beginning (at prefix) or end (at suffix) of the word
\nadding affix
\ncondition that has a format similar to the format of regular expressions.
\nThe .dict file looks like the .dict file of Ispell:
larder/M\nlardy/RT\nlarge/RSPMYT\nlargehearted\n\n
MySpell does not support compound words. Hunspell has sophisticated support for compound words. At present, PostgreSQL implements only the basic compound word operations of Hunspell.
\nThe Ispell dictionary template supports morphological dictionaries, which can normalize many different linguistic forms of a word into the same lexeme. For example, an English Ispell dictionary can match all declensions and conjugations of the search term bank, e.g., banking, banked, banks, banks', and bank's.
The standard PostgreSQL distribution does not include any Ispell configuration files. Dictionaries for a large number of languages are available from Ispell. Also, some more modern dictionary file formats are supported \u2014 MySpell (OO < 2.0.1) and Hunspell (OO >= 2.0.2). A large list of dictionaries is available on the OpenOffice Wiki.
\nTo create an Ispell dictionary perform these steps:
\ndownload dictionary configuration files. OpenOffice extension files have the .oxt extension. It is necessary to extract .aff and .dic files, change extensions to .affix and .dict. For some dictionary files it is also needed to convert characters to the UTF-8 encoding with commands (for example, for a Norwegian language dictionary):
iconv -f ISO_8859-1 -t UTF-8 -o nn_no.affix nn_NO.aff\niconv -f ISO_8859-1 -t UTF-8 -o nn_no.dict nn_NO.dic\n\n
copy files to the $SHAREDIR/tsearch_data directory
load files into PostgreSQL with the following command:
\nCREATE TEXT SEARCH DICTIONARY english_hunspell (\n TEMPLATE = ispell,\n DictFile = en_us,\n AffFile = en_us,\n Stopwords = english);\n\n
Here, DictFile, AffFile, and StopWords specify the base names of the dictionary, affixes, and stop-words files. The stop-words file has the same format explained above for the simple dictionary type. The format of the other files is not specified here but is available from the above-mentioned web sites.
Ispell dictionaries usually recognize a limited set of words, so they should be followed by another broader dictionary; for example, a Snowball dictionary, which recognizes everything.
\nThe .affix file of Ispell has the following structure:
prefixes\nflag *A:\n . > RE # As in enter > reenter\nsuffixes\nflag T:\n E > ST # As in late > latest\n [^AEIOU]Y > -Y,IEST # As in dirty > dirtiest\n [AEIOU]Y > EST # As in gray > grayest\n [^EY] > EST # As in small > smallest\n\n
And the .dict file has the following structure:
lapse/ADGRS\nlard/DGRS\nlarge/PRTY\nlark/MRS\n\n
Format of the .dict file is:
basic_form/affix_class_name\n\n
In the .affix file every affix flag is described in the following format:
condition > [-stripping_letters,] adding_affix\n\n
Here, condition has a format similar to the format of regular expressions. It can use groupings [...] and [^...]. For example, [AEIOU]Y means that the last letter of the word is \"y\" and the penultimate letter is \"a\", \"e\", \"i\", \"o\" or \"u\". [^EY] means that the last letter is neither \"e\" nor \"y\".
Ispell dictionaries support splitting compound words; a useful feature. Notice that the affix file should specify a special flag using the compoundwords controlled statement that marks dictionary words that can participate in compound formation:
compoundwords controlled z\n\n
Here are some examples for the Norwegian language:
\nSELECT ts_lexize('norwegian_ispell', 'overbuljongterningpakkmesterassistent');\n {over,buljong,terning,pakk,mester,assistent}\nSELECT ts_lexize('norwegian_ispell', 'sjokoladefabrikk');\n {sjokoladefabrikk,sjokolade,fabrikk}\n\nMySpell format is a subset of Hunspell. The .affix file of Hunspell has the following structure:
PFX A Y 1\nPFX A 0 re .\nSFX T N 4\nSFX T 0 st e\nSFX T y iest [^aeiou]y\nSFX T 0 est [aeiou]y\nSFX T 0 est [^ey]\n\n
The first line of an affix class is the header. Fields of an affix rules are listed after the header:
\nparameter name (PFX or SFX)
\nflag (name of the affix class)
\nstripping characters from beginning (at prefix) or end (at suffix) of the word
\nadding affix
\ncondition that has a format similar to the format of regular expressions.
\nThe .dict file looks like the .dict file of Ispell:
larder/M\nlardy/RT\nlarge/RSPMYT\nlargehearted\n\n
MySpell does not support compound words. Hunspell has sophisticated support for compound words. At present, PostgreSQL implements only the basic compound word operations of Hunspell.
\nThe Ispell dictionary template supports morphological dictionaries, which can normalize many different linguistic forms of a word into the same lexeme. For example, an English Ispell dictionary can match all declensions and conjugations of the search term bank, e.g., banking, banked, banks, banks', and bank's.
The standard PostgreSQL distribution does not include any Ispell configuration files. Dictionaries for a large number of languages are available from Ispell. Also, some more modern dictionary file formats are supported \u2014 MySpell (OO < 2.0.1) and Hunspell (OO >= 2.0.2). A large list of dictionaries is available on the OpenOffice Wiki.
\nTo create an Ispell dictionary perform these steps:
\ndownload dictionary configuration files. OpenOffice extension files have the .oxt extension. It is necessary to extract .aff and .dic files, change extensions to .affix and .dict. For some dictionary files it is also needed to convert characters to the UTF-8 encoding with commands (for example, for a Norwegian language dictionary):
iconv -f ISO_8859-1 -t UTF-8 -o nn_no.affix nn_NO.aff\niconv -f ISO_8859-1 -t UTF-8 -o nn_no.dict nn_NO.dic\n\n
copy files to the $SHAREDIR/tsearch_data directory
load files into PostgreSQL with the following command:
\nCREATE TEXT SEARCH DICTIONARY english_hunspell (\n TEMPLATE = ispell,\n DictFile = en_us,\n AffFile = en_us,\n Stopwords = english);\n\n
Here, DictFile, AffFile, and StopWords specify the base names of the dictionary, affixes, and stop-words files. The stop-words file has the same format explained above for the simple dictionary type. The format of the other files is not specified here but is available from the above-mentioned web sites.
Ispell dictionaries usually recognize a limited set of words, so they should be followed by another broader dictionary; for example, a Snowball dictionary, which recognizes everything.
\nThe .affix file of Ispell has the following structure:
prefixes\nflag *A:\n . > RE # As in enter > reenter\nsuffixes\nflag T:\n E > ST # As in late > latest\n [^AEIOU]Y > -Y,IEST # As in dirty > dirtiest\n [AEIOU]Y > EST # As in gray > grayest\n [^EY] > EST # As in small > smallest\n\n
And the .dict file has the following structure:
lapse/ADGRS\nlard/DGRS\nlarge/PRTY\nlark/MRS\n\n
Format of the .dict file is:
basic_form/affix_class_name\n\n
In the .affix file every affix flag is described in the following format:
condition > [-stripping_letters,] adding_affix\n\n
Here, condition has a format similar to the format of regular expressions. It can use groupings [...] and [^...]. For example, [AEIOU]Y means that the last letter of the word is \"y\" and the penultimate letter is \"a\", \"e\", \"i\", \"o\" or \"u\". [^EY] means that the last letter is neither \"e\" nor \"y\".
Ispell dictionaries support splitting compound words; a useful feature. Notice that the affix file should specify a special flag using the compoundwords controlled statement that marks dictionary words that can participate in compound formation:
compoundwords controlled z\n\n
Here are some examples for the Norwegian language:
\nSELECT ts_lexize('norwegian_ispell', 'overbuljongterningpakkmesterassistent');\n {over,buljong,terning,pakk,mester,assistent}\nSELECT ts_lexize('norwegian_ispell', 'sjokoladefabrikk');\n {sjokoladefabrikk,sjokolade,fabrikk}\n\nMySpell format is a subset of Hunspell. The .affix file of Hunspell has the following structure:
PFX A Y 1\nPFX A 0 re .\nSFX T N 4\nSFX T 0 st e\nSFX T y iest [^aeiou]y\nSFX T 0 est [aeiou]y\nSFX T 0 est [^ey]\n\n
The first line of an affix class is the header. Fields of an affix rules are listed after the header:
\nparameter name (PFX or SFX)
\nflag (name of the affix class)
\nstripping characters from beginning (at prefix) or end (at suffix) of the word
\nadding affix
\ncondition that has a format similar to the format of regular expressions.
\nThe .dict file looks like the .dict file of Ispell:
larder/M\nlardy/RT\nlarge/RSPMYT\nlargehearted\n\n
MySpell does not support compound words. Hunspell has sophisticated support for compound words. At present, PostgreSQL implements only the basic compound word operations of Hunspell.
\nThe Ispell dictionary template supports morphological dictionaries, which can normalize many different linguistic forms of a word into the same lexeme. For example, an English Ispell dictionary can match all declensions and conjugations of the search term bank, e.g., banking, banked, banks, banks', and bank's.
The standard PostgreSQL distribution does not include any Ispell configuration files. Dictionaries for a large number of languages are available from Ispell. Also, some more modern dictionary file formats are supported \u2014 MySpell (OO < 2.0.1) and Hunspell (OO >= 2.0.2). A large list of dictionaries is available on the OpenOffice Wiki.
\nTo create an Ispell dictionary perform these steps:
\ndownload dictionary configuration files. OpenOffice extension files have the .oxt extension. It is necessary to extract .aff and .dic files, change extensions to .affix and .dict. For some dictionary files it is also needed to convert characters to the UTF-8 encoding with commands (for example, for a Norwegian language dictionary):
iconv -f ISO_8859-1 -t UTF-8 -o nn_no.affix nn_NO.aff\niconv -f ISO_8859-1 -t UTF-8 -o nn_no.dict nn_NO.dic\n\n
copy files to the $SHAREDIR/tsearch_data directory
load files into PostgreSQL with the following command:
\nCREATE TEXT SEARCH DICTIONARY english_hunspell (\n TEMPLATE = ispell,\n DictFile = en_us,\n AffFile = en_us,\n Stopwords = english);\n\n
Here, DictFile, AffFile, and StopWords specify the base names of the dictionary, affixes, and stop-words files. The stop-words file has the same format explained above for the simple dictionary type. The format of the other files is not specified here but is available from the above-mentioned web sites.
Ispell dictionaries usually recognize a limited set of words, so they should be followed by another broader dictionary; for example, a Snowball dictionary, which recognizes everything.
\nThe .affix file of Ispell has the following structure:
prefixes\nflag *A:\n . > RE # As in enter > reenter\nsuffixes\nflag T:\n E > ST # As in late > latest\n [^AEIOU]Y > -Y,IEST # As in dirty > dirtiest\n [AEIOU]Y > EST # As in gray > grayest\n [^EY] > EST # As in small > smallest\n\n
And the .dict file has the following structure:
lapse/ADGRS\nlard/DGRS\nlarge/PRTY\nlark/MRS\n\n
Format of the .dict file is:
basic_form/affix_class_name\n\n
In the .affix file every affix flag is described in the following format:
condition > [-stripping_letters,] adding_affix\n\n
Here, condition has a format similar to the format of regular expressions. It can use groupings [...] and [^...]. For example, [AEIOU]Y means that the last letter of the word is \"y\" and the penultimate letter is \"a\", \"e\", \"i\", \"o\" or \"u\". [^EY] means that the last letter is neither \"e\" nor \"y\".
Ispell dictionaries support splitting compound words; a useful feature. Notice that the affix file should specify a special flag using the compoundwords controlled statement that marks dictionary words that can participate in compound formation:
compoundwords controlled z\n\n
Here are some examples for the Norwegian language:
\nSELECT ts_lexize('norwegian_ispell', 'overbuljongterningpakkmesterassistent');\n {over,buljong,terning,pakk,mester,assistent}\nSELECT ts_lexize('norwegian_ispell', 'sjokoladefabrikk');\n {sjokoladefabrikk,sjokolade,fabrikk}\n\nMySpell format is a subset of Hunspell. The .affix file of Hunspell has the following structure:
PFX A Y 1\nPFX A 0 re .\nSFX T N 4\nSFX T 0 st e\nSFX T y iest [^aeiou]y\nSFX T 0 est [aeiou]y\nSFX T 0 est [^ey]\n\n
The first line of an affix class is the header. Fields of an affix rules are listed after the header:
\nparameter name (PFX or SFX)
\nflag (name of the affix class)
\nstripping characters from beginning (at prefix) or end (at suffix) of the word
\nadding affix
\ncondition that has a format similar to the format of regular expressions.
\nThe .dict file looks like the .dict file of Ispell:
larder/M\nlardy/RT\nlarge/RSPMYT\nlargehearted\n\n
MySpell does not support compound words. Hunspell has sophisticated support for compound words. At present, PostgreSQL implements only the basic compound word operations of Hunspell.
\nThe Ispell dictionary template supports morphological dictionaries, which can normalize many different linguistic forms of a word into the same lexeme. For example, an English Ispell dictionary can match all declensions and conjugations of the search term bank, e.g., banking, banked, banks, banks', and bank's.
The standard PostgreSQL distribution does not include any Ispell configuration files. Dictionaries for a large number of languages are available from Ispell. Also, some more modern dictionary file formats are supported \u2014 MySpell (OO < 2.0.1) and Hunspell (OO >= 2.0.2). A large list of dictionaries is available on the OpenOffice Wiki.
\nTo create an Ispell dictionary perform these steps:
\ndownload dictionary configuration files. OpenOffice extension files have the .oxt extension. It is necessary to extract .aff and .dic files, change extensions to .affix and .dict. For some dictionary files it is also needed to convert characters to the UTF-8 encoding with commands (for example, for a Norwegian language dictionary):
iconv -f ISO_8859-1 -t UTF-8 -o nn_no.affix nn_NO.aff\niconv -f ISO_8859-1 -t UTF-8 -o nn_no.dict nn_NO.dic\n\n
copy files to the $SHAREDIR/tsearch_data directory
load files into PostgreSQL with the following command:
\nCREATE TEXT SEARCH DICTIONARY english_hunspell (\n TEMPLATE = ispell,\n DictFile = en_us,\n AffFile = en_us,\n Stopwords = english);\n\n
Here, DictFile, AffFile, and StopWords specify the base names of the dictionary, affixes, and stop-words files. The stop-words file has the same format explained above for the simple dictionary type. The format of the other files is not specified here but is available from the above-mentioned web sites.
Ispell dictionaries usually recognize a limited set of words, so they should be followed by another broader dictionary; for example, a Snowball dictionary, which recognizes everything.
\nThe .affix file of Ispell has the following structure:
prefixes\nflag *A:\n . > RE # As in enter > reenter\nsuffixes\nflag T:\n E > ST # As in late > latest\n [^AEIOU]Y > -Y,IEST # As in dirty > dirtiest\n [AEIOU]Y > EST # As in gray > grayest\n [^EY] > EST # As in small > smallest\n\n
And the .dict file has the following structure:
lapse/ADGRS\nlard/DGRS\nlarge/PRTY\nlark/MRS\n\n
Format of the .dict file is:
basic_form/affix_class_name\n\n
In the .affix file every affix flag is described in the following format:
condition > [-stripping_letters,] adding_affix\n\n
Here, condition has a format similar to the format of regular expressions. It can use groupings [...] and [^...]. For example, [AEIOU]Y means that the last letter of the word is \"y\" and the penultimate letter is \"a\", \"e\", \"i\", \"o\" or \"u\". [^EY] means that the last letter is neither \"e\" nor \"y\".
Ispell dictionaries support splitting compound words; a useful feature. Notice that the affix file should specify a special flag using the compoundwords controlled statement that marks dictionary words that can participate in compound formation:
compoundwords controlled z\n\n
Here are some examples for the Norwegian language:
\nSELECT ts_lexize('norwegian_ispell', 'overbuljongterningpakkmesterassistent');\n {over,buljong,terning,pakk,mester,assistent}\nSELECT ts_lexize('norwegian_ispell', 'sjokoladefabrikk');\n {sjokoladefabrikk,sjokolade,fabrikk}\n\nMySpell format is a subset of Hunspell. The .affix file of Hunspell has the following structure:
PFX A Y 1\nPFX A 0 re .\nSFX T N 4\nSFX T 0 st e\nSFX T y iest [^aeiou]y\nSFX T 0 est [aeiou]y\nSFX T 0 est [^ey]\n\n
The first line of an affix class is the header. Fields of an affix rules are listed after the header:
\nparameter name (PFX or SFX)
\nflag (name of the affix class)
\nstripping characters from beginning (at prefix) or end (at suffix) of the word
\nadding affix
\ncondition that has a format similar to the format of regular expressions.
\nThe .dict file looks like the .dict file of Ispell:
larder/M\nlardy/RT\nlarge/RSPMYT\nlargehearted\n\n
MySpell does not support compound words. Hunspell has sophisticated support for compound words. At present, PostgreSQL implements only the basic compound word operations of Hunspell.
\n