Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 66C9E6501A2 for ; Mon, 25 Aug 2008 11:37:25 -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 87936-07 for ; Mon, 25 Aug 2008 11:37:06 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from svr2.hagander.net (svr2.hagander.net [88.198.128.226]) by postgresql.org (Postfix) with ESMTP id 46C79650174 for ; Mon, 25 Aug 2008 11:37:12 -0300 (ADT) Received: from dynamic.hagander.net ([127.0.0.1]) (encrypted and authenticated) by svr2.hagander.net (Postfix) with ESMTP id 4B8D4DCC9B1; Mon, 25 Aug 2008 16:37:09 +0200 (CEST) Received: from [127.0.0.1] (localhost [127.0.0.1]) by mha-laptop.hagander.net (Postfix) with ESMTP id 7D4FF124145; Mon, 25 Aug 2008 16:37:08 +0200 (CEST) Message-ID: <48B2C394.6020402@hagander.net> Date: Mon, 25 Aug 2008 16:37:08 +0200 From: Magnus Hagander User-Agent: Thunderbird 2.0.0.16 (X11/20080724) MIME-Version: 1.0 To: Peter Eisentraut CC: pgsql-www@postgresql.org, Bruce Momjian , Andrew Sullivan Subject: Re: [BUGS] BUG #4279: Bad codepage in our web-site References: <200808221803.m7MI3nu12836@momjian.us> <48B2668C.3040006@hagander.net> <200808251727.37176.peter_e@gmx.net> In-Reply-To: <200808251727.37176.peter_e@gmx.net> X-Enigmail-Version: 0.95.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests=none X-Spam-Level: X-Archive-Number: 200808/103 X-Sequence-Number: 15693 Peter Eisentraut wrote: > On Monday 25 August 2008 11:00:12 Magnus Hagander wrote: >> I wouldn't put too much work into that. Wouldn't it be better to migrate >> them to the wiki instead? > > I'm all in favor of the wiki, but consider that this is prominent user-facing > stuff here. If we put the FAQ in the wiki, why not the entire web site? > Perhaps the web team should take over these files and apply the existing > translation framework to it. That we could certainly do. At least if we can get pgweb set up to allow specific permissions to update these things - I would like to rid us of the bottleneck of having to write up an actual patch and send it to a list, to have somebody else apply it, and only then realize it's broken HTML etc. The translators should be able to do this on their own. I don't think the current web team can just "take them over". Sure, they could take over the part that Bruce does today which is apply patches for people, but it doesn't solve the issue in itself. //Magnus