X-Original-To: pgsql-www-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 90C55D6817; Thu, 3 Nov 2005 13:31:33 -0400 (AST) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 86030-10; Thu, 3 Nov 2005 17:31:31 +0000 (GMT) Received: from davinci.ethosmedia.com (server227.ethosmedia.com [209.128.84.227]) by svr1.postgresql.org (Postfix) with ESMTP id 4B453D8B00; Thu, 3 Nov 2005 13:31:31 -0400 (AST) X-EthosMedia-Virus-Scanned: no infections found Received: from [64.81.245.111] (HELO [192.168.2.2]) by davinci.ethosmedia.com (CommuniGate Pro SMTP 4.1.8) with ESMTP id 8413220; Thu, 03 Nov 2005 09:34:01 -0800 Message-ID: <436A49BB.2030104@agliodbs.com> Date: Thu, 03 Nov 2005 09:32:43 -0800 From: Josh Berkus User-Agent: Mozilla Thunderbird 1.0.6 (Macintosh/20050716) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Magnus Hagander Cc: pgsql-www@postgresql.org, translators@postgresql.org Subject: Re: Presskits for 8.1 Release References: <6BCB9D8A16AC4241919521715F4D8BCE6C7B5C@algol.sollentuna.se> In-Reply-To: <6BCB9D8A16AC4241919521715F4D8BCE6C7B5C@algol.sollentuna.se> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0 required=5 tests=[none] X-Spam-Score: 0 X-Spam-Level: X-Archive-Number: 200511/23 X-Sequence-Number: 8738 Magnus, > mha@developer:~/pgfoundry/press/pr/releases/8.1/en$ grep -n " presskit81.html.en > 16:

Original Press Release

> 100:

Additional Features in this > Release

> 142:

Quoted Companies

> 164:

Where to Download

> 177:

Documentation

> 187:

License

> 201:

Contacts

> 215:

Corporate Support

> 228:

Links

> 279:

Official Translations of This Oh. I was going from examples of how to do an anchor tag. I take it that it was wrong? > > Oh. Yeah, you'd have to have each translator do it. Well, we'll get the headers from some people but not others. Can we live without the ones we don't get? Or put them in English? >>I don't have the time or the knowledge to fix XHTML problems; >>that's my markup that you're having problems with and it >>represents the limit of my HTML know-how (I *did* post to >>this list asking for feedback before the translations >>started, but, whatever) Can someone on the web team take this over? > > > Not sure - I certainly wouldn't go into doing russian etc on my own, as > I wouldn't know how to actually fix a lot of the things. Hmmm. Well, the Russians don't necessarily know any XHTML. How can we get out of this? --Josh