Re: [OpenFTS-general] AW: tsearch2, ispell, utf-8 and german special characters

From: "Markus Wollny" <Markus(dot)Wollny(at)computec(dot)de>
To: "Oleg Bartunov" <oleg(at)sai(dot)msu(dot)su>
Cc: <pgsql-general(at)postgresql(dot)org>, <openfts-general(at)lists(dot)sourceforge(dot)net>
Subject: Re: [OpenFTS-general] AW: tsearch2, ispell, utf-8 and german special characters
Date: 2004-07-21 16:30:28
Message-ID: 2266D0630E43BB4290742247C891057505BF2F53@dozer.computec.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general


Hi!

> -----Ursprüngliche Nachricht-----
> Von: openfts-general-admin(at)lists(dot)sourceforge(dot)net
> [mailto:openfts-general-admin(at)lists(dot)sourceforge(dot)net] Im
> Auftrag von Markus Wollny
> Gesendet: Mittwoch, 21. Juli 2004 17:04
> An: Oleg Bartunov
> Cc: pgsql-general(at)postgresql(dot)org;
> openfts-general(at)lists(dot)sourceforge(dot)net
> Betreff: [OpenFTS-general] AW: [GENERAL] tsearch2, ispell,
> utf-8 and german special characters

> The issue with the unrecognized stop-word 'ein' which is
> converted by to_tsvector to 'eint' remains however. Now
> here's as much detail as I can provide:
>
> Ispell is Version 3.1.20 10/10/95, patch 1.

I've just upgraded Ispell to the latest version (International Ispell Version 3.2.06 08/01/01), but that didn't help; by now I think it might be something to do with a german language peculiarity or with something in the german dictionary. In german.med, there is an entry

eint/EGPVWX

So the ts_vector output is just a bit like a wrong guess. Doesn't it evaluate the stopword-list first before doing the lookup in the Ispell-dictionary?

Kind regards

Markus Wollny

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Gellert, Andre 2004-07-21 17:32:15 Wanted: Want to hide data by using PL/PGSQL functions
Previous Message Wang, Mary Y 2004-07-21 15:56:51 SQL - display different data