Received: from localhost (maia-1.hub.org [200.46.204.191]) by postgresql.org (Postfix) with ESMTP id A108C9FA5E5 for ; Mon, 16 Apr 2007 03:10:53 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.191]) (amavisd-maia, port 10024) with ESMTP id 93058-03 for ; Mon, 16 Apr 2007 03:10:48 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from svr2.hagander.net (svr2.hagander.net [88.198.128.226]) by postgresql.org (Postfix) with ESMTP id 355A49FA433 for ; Mon, 16 Apr 2007 03:10:48 -0300 (ADT) Received: from dynamic.hagander.net ([127.0.0.1]) (encrypted and authenticated) by svr2.hagander.net (Postfix) with ESMTP id 1542EDCC7C5; Mon, 16 Apr 2007 08:10:46 +0200 (CEST) Subject: Re: [pgsql-advocacy] Broken links in presskit Date: Mon, 16 Apr 2007 08:10:40 +0200 From: "Magnus Hagander" To: josh@agliodbs.com Cc: "Robert Treat" , pgsql-www@postgresql.org MIME-Version: 1.0 X-Mailer: Lonely Cat Games ProfiMail In-Reply-To: <4622ABCB.30600@agliodbs.com> Content-Type: text/plain; charset=iso-8859-1 Message-Id: <20070416061046.1542EDCC7C5@svr2.hagander.net> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200704/101 X-Sequence-Number: 11851 > Well, you only did the english version. Are you saying that links got > broken *after* translation? That could be an issue I really didn't > think of ... well, to be more accurate, I didn't think of any way to do > anything about it. Both. There was one broken link in the template that propagated to a lot of files (But some translators fixed it in their copy). and several different ones in different translations. > Suggestions? The automated link checker mentioned? That would help, but it can only get so far. I think for something as important as the press kit we need manual checking. I think it would help to ask the translators to doublecheck all links after the page has gone up on the website. > The issue is that we often don't get final translations until ~~ 3 days > before the release, and we have a lot of them. So I'm not sure checking > by hand will help. Well, if we run out of time it's still better to have it fixed a couple of days later than not at all. /Magnus