Re: tsearch in core patch

Magnus Hagander wrote:
> Tom Lane wrote:
> > Alvaro Herrera <alvherre(at)commandprompt(dot)com> writes:
> >> 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.
> >
> > Also, the problem we're dealing with here is mainly lack of
> > standardization of the encoding part of locale names. AFAIK, just about
> > everybody agrees on "es_ES", "ru_RU", etc; it's the part that comes
> > after that (if any) that is not too consistent across platforms.
>
> That may have been true until we started supporting Windows...
> Swedish_Sweden.1252 is what I get on my machine, for example. Principle
> is the same, but values certainly aren't.

Well, at least the name is not itself translated, so a mapping table is
not right out of the question. If they had put a name like
"Español_Chile" instead of "Spanish_Chile" we would be in serious
trouble.

--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support