Tatsuo,
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 con
On Fri, 2007-07-06 at 15:43 +0900, 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
Tatsuo Ishii <[EMAIL PROTECTED]> writes:
> 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
Hi,
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 Uni
