From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
---|---|
To: | Teodor Sigaev <teodor(at)sigaev(dot)ru> |
Cc: | Hannu Krosing <hannu(at)skype(dot)net>, Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Subject: | Re: tsearch in core patch |
Date: | 2007-06-22 14:28:26 |
Message-ID: | 20070622142826.GF8949@alvh.no-ip.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Teodor Sigaev wrote:
> >> --- how do many languages use ISO8859-1 locale?.
> > ISO8859-1 is encoding, not locale.
>
> I meant, if we'll use encoding name (for example PG_LATIN1) we couldn't
> distinguish languages which use that encoding (for example italian and
> finnish and some more), but using locale names it's possible:
> it_IT.ISO8859-1, fi_FI.ISO8859-1
I don't understand. Why use "it_IT.ISO8859-1"? You just need to know
the language, so "it" is enough. The _IT part specifies that it's the
italian spoken in Italy. This may be irrelevant in most cases, but
consider that pt_PT and pt_BR are AFAIK somewhat different languages.
I very much doubt that the different spanishes are any different in the
stemming rules, so there's no need for es_ES, es_PE, es_AR, es_CL etc;
but in the case of portuguese I'm not so sure. Maybe there are other
examples (like chinese, but I'm not sure how useful is tsearch for
chinese).
And the .ISO8859-1 part you don't need at all if you accept that the
files are UTF8 by design, as Tom proposed.
--
Alvaro Herrera Developer, http://www.PostgreSQL.org/
"Nadie esta tan esclavizado como el que se cree libre no siendolo" (Goethe)
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2007-06-22 14:28:37 | Re: tsearch in core patch |
Previous Message | Tom Lane | 2007-06-22 14:26:37 | Re: Worries about delayed-commit semantics |