From: Artur Zakirov <zaartur@gmail.com>
To: matti.linnanvuori@portalify.com, pgsql-bugs@lists.postgresql.org, PG Bug reporting form <noreply@postgresql.org>
Subject: Re: BUG #16337: Finnish Ispell dictionary cannot be created
Date: Fri, 3 Apr 2020 12:33:00 +0900
Message-ID: <cae19e93-692f-d646-6ec7-3edc0ec27edb@gmail.com> (raw)
In-Reply-To: <16337-0a68a7a1726ffbc6@postgresql.org>
References: <16337-0a68a7a1726ffbc6@postgresql.org>
Hello,
On 4/2/2020 7:11 PM, PG Bug reporting form wrote:
> postgres=# CREATE TEXT SEARCH DICTIONARY finnish_ispell ( TEMPLATE = ispell,
> DictFile = fi_fi, AffFile = fi_fi, Stopwords = finnish);
> ERROR: syntax error
> CONTEXT: line 83 of configuration file
> "/usr/pgsql-12/share/tsearch_data/fi_fi.affix": " I >
> ALI\-
> "
Thank you for the email.
It seems that here the backslash is used to escape the following
character according to the comment for the following flag:
> flag *E:
> . > YLI # ylijohtaja
> I > YLI\- # yli-inhimillinen
Escaping character is valid for ispell format (see
https://manpages.debian.org/testing/ispell/ispell.5.en.html):
> Any character with special meaning to the parser can be changed to an uninterpreted token by backslashing it
I've looked also for Hunspell finnish dictionary. But I didn't find any
I found only some postgres extension:
https://github.com/Houston-Inc/dict_voikko
I think it is possible to fix the postgres parser. But I'm not sure
should we do that.
At first sight it is necessary to fix parse_affentry().
--
Artur
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: zaartur@gmail.com, noreply@postgresql.org
Subject: Re: BUG #16337: Finnish Ispell dictionary cannot be created
In-Reply-To: <cae19e93-692f-d646-6ec7-3edc0ec27edb@gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox