Message-ID: <48D94400.709@hagander.net>
Date: Tue, 23 Sep 2008 21:31:12 +0200
From: Magnus Hagander <magnus@hagander.net>
User-Agent: Thunderbird 2.0.0.16 (X11/20080724)
MIME-Version: 1.0
To: Bruce Momjian <bruce@momjian.us>
CC: Dave Page <dpage@pgadmin.org>,
	Nikolay Samokhvalov <samokhvalov@gmail.com>,
	Peter Eisentraut <peter_e@gmx.net>,
	PostgreSQL-documentation <pgsql-docs@postgresql.org>
Subject: Re: Russian FAQ page charset problem
References: <200809231805.m8NI5SO26294@momjian.us>
In-Reply-To: <200809231805.m8NI5SO26294@momjian.us>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Bruce Momjian wrote:
> Dave Page wrote:
>> On Tue, Sep 23, 2008 at 7:01 PM, Bruce Momjian <bruce@momjian.us> wrote:
>>> Dave Page wrote:
>>>> On Mon, Sep 15, 2008 at 8:37 AM, Nikolay Samokhvalov
>>>> <samokhvalov@gmail.com> wrote:
>>>>> On Mon, Sep 15, 2008 at 11:30 AM, Peter Eisentraut <peter_e@gmx.net> wrote:
>>>>>> This was already discussed on the pgsql-www list recently, but there has
>>>>>> been no resolution on what to do yet.
>>>>> What about using UTF8 for Russian text? Why not simply "iconv -f
>>>>> koi8-r -t utf8 ..."?
>>>> I thought that was what Bruce was going to do. He has other priorities
>>>> at the moment though, so perhaps one of the the committers could
>>>> handle it.
>>> No, the conversion to a UTF8 header is done by the web infrastructure;
>>> the file in CVS is in the native Russian encoding, koi8-r, and I don't
>>> know how to change that.
>> That's the iconv -f bit suggested above, that I thought you were doing.
> 
> Nope, never did that, and I don't have the proper locales on my sever.

That's not locale, that's encoding. And it's independent of what locales
you have - AFAIK as long as you have iconv, you should be good.

For next time, that is - since it's already fixed this time :-)

//Magnus