Hi!

> -----Ursprüngliche Nachricht-----
> Von: [EMAIL PROTECTED] 
> [mailto:[EMAIL PROTECTED] Im 
> Auftrag von Markus Wollny
> Gesendet: Mittwoch, 21. Juli 2004 17:04
> An: Oleg Bartunov
> Cc: [EMAIL PROTECTED]; 
> [EMAIL PROTECTED]
> 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

---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
      joining column's datatypes do not match

Reply via email to