Received: from localhost (maia-3.hub.org [200.46.204.184]) by postgresql.org (Postfix) with ESMTP id 4F3589FB7A1 for ; Wed, 4 Apr 2007 18:44:33 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.184]) (amavisd-maia, port 10024) with ESMTP id 26826-06 for ; Wed, 4 Apr 2007 18:44:19 -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 4A9279FB704 for ; Wed, 4 Apr 2007 18:44:23 -0300 (ADT) Received: from dynamic.hagander.net ([127.0.0.1]) (encrypted and authenticated) by svr2.hagander.net (Postfix) with ESMTP id 0676EDCC57A; Wed, 4 Apr 2007 23:44:20 +0200 (CEST) Message-ID: <46141C4F.3070901@hagander.net> Date: Wed, 04 Apr 2007 23:44:47 +0200 From: Magnus Hagander User-Agent: Thunderbird 2.0.0.0pre (Windows/20070404) MIME-Version: 1.0 To: Guillaume Lelarge CC: pgsql-www@postgresql.org Subject: Re: Typos fixes and an accesskey References: <46118E2E.7000706@lelarge.info> In-Reply-To: <46118E2E.7000706@lelarge.info> X-Enigmail-Version: 0.95b Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200704/7 X-Sequence-Number: 11757 Guillaume Lelarge wrote: > Hi, > > I send again my patchs because they don't seem to appear on the mailing > list. I just hope you won't receive the two same messages. > > You'll find attached a .tar.gz which contains two patches. > > > The first one, typos.patch, fixes a few typos I found while translating > the templates. Please, review them because I'm not a native english > speaker. This patch appears to contain a whole lot of changes that are just whitespace (such as the indention). That makes it much harder to find out what has really changed. Can you submit it without the whitespace changes? > The second one, searchaccesskey.patch, adds an accesskey (q) for the > search text box field. It's a quick way to access this text box. You can > change the key if you want but I would really like to see an access key > on this field. I'm not really sure about what you can and can not do with accesskeys, but is there a particular reason you chose "q" for the search feature? Seems like "s" would be a more logical choice? //Magnus