Jens,
could you check affix file for
compoundwords controlled z
also, can you provide link to dictionary files, so we can check if they
supported, since we have only rudiment support of hunspell.
btw,it'd be nice to have output from ts_debug() to make sure dictionaries
actually used.
Oleg
On Mon, 7 Feb 2011, Jens Sauer wrote:
> Hey,
>
> I want to use hunspell as a dictionary for the full text search by
>
> * using PostgresSQL 8.4.7
> * installing hunspell-de-de, hunspell-de-med
> * creating a dictionary:
>
> CREATE TEXT SEARCH DICTIONARY german_hunspell (
> TEMPLATE = ispell,
> DictFile = de_de,
> AffFile = de_de,
> StopWords = german
> );
>
> * changing the config
>
> ALTER TEXT SEARCH CONFIGURATION german
> ALTER MAPPING FOR asciiword, asciihword, hword_asciipart,
> word, hword, hword_part
> WITH german_hunspell, german_stem;
>
> * now testing the lexizer:
>
> SELECT ts_lexize('german_hunspell', 'Schokaladenfarik');
> ts_lexize
> -----------
>
> (1 Zeile)
>
> Shouldn't it be something like this:
> SELECT ts_lexize('norwegian_ispell', 'sjokoladefabrikk');
> {sjokoladefabrikk,sjokolade,fabrikk}
> (from the 8.4 documentation of PostgreSQL)
>
>
> The dict and affix files in the tsearch_data directory were
> automatically generated by pg_updatedicts.
>
> Is this a problem of the splitting compound word functionality? Should
> I use ispell instead of hunspell?
>
> Thanks
>
>
Regards,
Oleg
_____________________________________________________________
Oleg Bartunov, Research Scientist, Head of AstroNet (www.astronet.ru),
Sternberg Astronomical Institute, Moscow University, Russia
Internet: oleg@sai.msu.su, http://www.sai.msu.su/~megera/
phone: +007(495)939-16-83, +007(495)939-23-83
