Received: from localhost (maia-2.hub.org [200.46.204.187]) by postgresql.org (Postfix) with ESMTP id 2BFAE9FB8C3 for ; Tue, 13 Feb 2007 14:20:13 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.187]) (amavisd-new, port 10024) with ESMTP id 59218-04 for ; Tue, 13 Feb 2007 14:20:04 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from davinci.ethosmedia.com (server227.ethosmedia.com [209.128.84.227]) by postgresql.org (Postfix) with ESMTP id 606219FBA29 for ; Tue, 13 Feb 2007 14:20:05 -0400 (AST) X-EthosMedia-Virus-Scanned: no infections found Received: from [63.195.55.98] (account josh@agliodbs.com HELO spooky.sf.agliodbs.com) by davinci.ethosmedia.com (CommuniGate Pro SMTP 4.1.8) with ESMTP id 11419340; Tue, 13 Feb 2007 10:24:01 -0800 From: Josh Berkus Organization: PostgreSQL @ Sun To: pgsql-www@postgresql.org Subject: Re: Multi-language to be or not to be Date: Tue, 13 Feb 2007 10:20:06 -0800 User-Agent: KMail/1.8.2 Cc: Tino Wildenhain , Magnus Hagander , Guillaume Lelarge , Peter Eisentraut , Adrian Maier References: <45CF18A1.1090903@hagander.net> <45D0E362.1020903@hagander.net> <45D1549B.2080407@wildenhain.de> In-Reply-To: <45D1549B.2080407@wildenhain.de> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200702131020.06670.josh@agliodbs.com> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.186 tagged_above=0 required=5 tests=AWL, BAYES_50, FORGED_RCVD_HELO X-Spam-Level: X-Archive-Number: 200702/205 X-Sequence-Number: 11610 Magnus, I have to say "I told you so". When the existing translation scheme was built two+ years ago, I pointed out that it was cumbersome, confusing and inaccessable and predicted that none of our non-English communities would use it. So, my vote is that whether or not we have *an* translation infrastructure, the current incomplete and non-standard infrastructure be junked. It's never going to be used in its current form. Further, we're going to have to expect that some language communities will never translate the main site, since that puts them in a position of having all new content generated in English and just having their site mirror that without the ability to add new content originating in their group. And I don't think that most of our language groups are large enough to sustain both organizing content for their site and keeping translations of the English site updated. Also, a couple of the local site groups told me that they want an easy-to-use CMS like Drupal, so they're not merging to our site for that reason. P.S. Josh D, you are absolutely wrong about our language composition. The majority of our community speaks a first language other than English, and at least half of the non-English speakers aren't fluent in English. There are large communities in Brazil, Spanish-speaking South America, Italy and Germany -- as well as Japan -- which you aren't aware of because they don't join the English-speaking MLs for obvious reasons. When I used to answer webmaster@, for example, I got *more* questions in Portuguese than in English. -- Josh Berkus PostgreSQL @ Sun San Francisco