fts configuration doesn't related to the encoding ! It's fully up to you
how to combine parser and dictionaries.

The problem arise only if you want
to define somehow so-called default configuration, which, as I inclined
now, is a bad feature. We choose locale name to identify default confgiuration,
for 8.3 people suggested to have language name.

On Fri, 6 Jul 2007, Tatsuo Ishii wrote:


I'm wondering if a tsearch's configuration is bound to a language or
an encoding. If it's bound to a language, there's a serious design
problem, I would think. An encoding or charset is not necessarily
bound to single language. We can find such that example everywhere(I'm
not talking about Unicode here). LATIN1 inclues English and several
european languages. EUC-JP includes English and Japanese etc. And
we specify encoding for char's property, not language, I would say the
configuration should be bound to an encoding.
Tatsuo Ishii
SRA OSS, Inc. Japan

---------------------------(end of broadcast)---------------------------
TIP 4: Have you searched our list archives?


Oleg Bartunov, Research Scientist, Head of AstroNet (www.astronet.ru),
Sternberg Astronomical Institute, Moscow University, Russia
Internet: [EMAIL PROTECTED], http://www.sai.msu.su/~megera/
phone: +007(495)939-16-83, +007(495)939-23-83

---------------------------(end of broadcast)---------------------------
TIP 6: explain analyze is your friend

Reply via email to