From: Bruce Momjian <bruce@momjian.us>
Message-Id: <200809231805.m8NI5SO26294@momjian.us>
Subject: Re: Russian FAQ page charset problem
In-Reply-To: <937d27e10809231104l65817ff8ucc54e4c264eaa6f9@mail.gmail.com>
To: Dave Page <dpage@pgadmin.org>
Date: Tue, 23 Sep 2008 14:05:28 -0400 (EDT)
CC: Nikolay Samokhvalov <samokhvalov@gmail.com>,
	Peter Eisentraut <peter_e@gmx.net>,
	PostgreSQL-documentation <pgsql-docs@postgresql.org>
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="US-ASCII"

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.

-- 
  Bruce Momjian  <bruce@momjian.us>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

  + If your life is a hard drive, Christ can be your backup. +