Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 7675C64FCE4 for ; Mon, 15 Sep 2008 06:24:26 -0300 (ADT) Received: from postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 16456-04 for ; Mon, 15 Sep 2008 06:24:20 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from yx-out-2324.google.com (yx-out-2324.google.com [74.125.44.30]) by postgresql.org (Postfix) with ESMTP id E05AC64FCDF for ; Mon, 15 Sep 2008 06:24:19 -0300 (ADT) Received: by yx-out-2324.google.com with SMTP id 8so615802yxb.73 for ; Mon, 15 Sep 2008 02:24:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:subject :cc:in-reply-to:mime-version:content-type:content-transfer-encoding :content-disposition:references; bh=34tr63Bmq8Z/7Co6W5k75U5SY+Y+wezID7y0D17VK2c=; b=WWNyUSXV3/XDRwXOub8LHi1ixOoIoO6z16GWsvp0NsATBA7KdgDDK5ixVpZyx0OsgP NdMqA3o5zeAnsu1ebA7VfrwCqFwuCF3kL/QjclQzsr2Xij9K4YzuGdHf+JyEriXQJVJg DD0UTKVXPrsw7C5TwXA9t6toUZkP4Ur1bp+AQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=kT40C47EIFeXeW2JNOwzsY+h/HJASqdXbjgJZHQSzlgFl/2O/qMVLc/CUoKwFsiCPD +mrCE/9RyLGN4Gsub6ESJL6RQHG3b1eF8PmDf5VHJYU/4KNErJVTdfhM7l6hztCiUXii 5KxjGpdtBkl3L4NBNnetfryw3+CwC5QG0Qf90= Received: by 10.151.155.9 with SMTP id h9mr10425494ybo.8.1221470656976; Mon, 15 Sep 2008 02:24:16 -0700 (PDT) Received: by 10.150.227.7 with HTTP; Mon, 15 Sep 2008 02:24:16 -0700 (PDT) Message-ID: <1f60b6160809150224s4ec7bb6cn34c6efdb7ddb81dc@mail.gmail.com> Date: Mon, 15 Sep 2008 13:24:16 +0400 From: "=?KOI8-R?B?98nL1M/SIPfJ08zPws/Lz9c=?=" Subject: Re: Russian FAQ page charset problem Cc: PostgreSQL-documentation In-Reply-To: <48CE1FA4.8040305@hagander.net> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <48CE0F0B.4060600@gmx.net> <937d27e10809150048v58483686v646e6db4a9335bf@mail.gmail.com> <48CE1FA4.8040305@hagander.net> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=1.581 tagged_above=0 required=5 tests=MISSING_HEADERS=1.581 X-Spam-Level: * X-Archive-Number: 200809/15 X-Sequence-Number: 4976 Hmm. At this time, everything all right. But, How do I do at the next time after update? Would be I convert Russian translation to UTF-8 or leave it in KO8-R, before send it to Bruce? 2008/9/15 Magnus Hagander : > Dave Page wrote: >> On Mon, Sep 15, 2008 at 8:37 AM, Nikolay Samokhvalov >> wrote: >>> On Mon, Sep 15, 2008 at 11:30 AM, Peter Eisentraut 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. > > Done. > > I only touched the HTML one - seems the text one is already in latin > characters? > > //Magnus > > > -- > Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgsql-docs >