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

From Markus Wollny
Subject Re: [OpenFTS-general] AW: tsearch2, ispell, utf-8 and german special characters
Date
Msg-id 2266D0630E43BB4290742247C891057505BF2F53@dozer.computec.de
Whole thread Raw
Responses Re: [OpenFTS-general] AW: tsearch2, ispell, utf-8 and  (Oleg Bartunov <oleg@sai.msu.su>)
List pgsql-general
Hi!

> -----Ursprüngliche Nachricht-----
> Von: openfts-general-admin@lists.sourceforge.net
> [mailto:openfts-general-admin@lists.sourceforge.net] Im
> Auftrag von Markus Wollny
> Gesendet: Mittwoch, 21. Juli 2004 17:04
> An: Oleg Bartunov
> Cc: pgsql-general@postgresql.org;
> openfts-general@lists.sourceforge.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;
bynow 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
lookupin the Ispell-dictionary? 

Kind regards

   Markus Wollny

pgsql-general by date:

Previous
From: "Wang, Mary Y"
Date:
Subject: SQL - display different data
Next
From: "Gellert, Andre"
Date:
Subject: Wanted: Want to hide data by using PL/PGSQL functions