Message-ID: <937d27e10809231104l65817ff8ucc54e4c264eaa6f9@mail.gmail.com>
Date: Tue, 23 Sep 2008 19:04:30 +0100
From: "Dave Page" <dpage@pgadmin.org>
To: "Bruce Momjian" <bruce@momjian.us>
Subject: Re: Russian FAQ page charset problem
Cc: "Nikolay Samokhvalov" <samokhvalov@gmail.com>,
	"Peter Eisentraut" <peter_e@gmx.net>,
	PostgreSQL-documentation <pgsql-docs@postgresql.org>
In-Reply-To: <200809231801.m8NI1fk25513@momjian.us>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <937d27e10809150048v58483686v646e6db4a9335bf@mail.gmail.com>
	<200809231801.m8NI1fk25513@momjian.us>

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.

> However, it now seems all the FAQs are in ASCII or UTF8 so I think we
> are OK going into the future.

Yup, Magnus converted them.

-- 
Dave Page
EnterpriseDB UK:   http://www.enterprisedb.com