Received: from localhost (unknown [200.46.204.184]) by postgresql.org (Postfix) with ESMTP id EF9442E0033 for ; Thu, 27 Mar 2008 15:18:49 -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 88803-04 for ; Thu, 27 Mar 2008 15:18:36 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.5 Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.154]) by postgresql.org (Postfix) with ESMTP id 577D42E0031 for ; Thu, 27 Mar 2008 15:18:38 -0300 (ADT) Received: by fg-out-1718.google.com with SMTP id 22so4219298fge.23 for ; Thu, 27 Mar 2008 11:18:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=8VgBgDliaCgP9jMvng2mP7/euHwz3noJ2kINRIX2yKU=; b=YjSlflTfCtwyO3WRAcYZKYLDqHHKF29Zhyu4ndBaSkSm4TMK+N6Nyuh1pFqsK0WNjy5NeHtio0J1sdHrNCTC2ZEnO/goXle07CyXJRAJyFmkdNsAbH9bqwkKupts5tqWjDetkuZjiHET4yHeI/P0QtMbFt5if+zlDk03AmyIwmU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=jxjZWSB80Ij4GG/POukSrqo1fNJ3C/3KoJOwn5DaMstrOhJ9ZN/Kz6itxA+hvd1B8JVFZfdiRWd38BlD5tSoUAyDzdMjBCPQ+5W2oyzpEkAn726/h6kMwV5zQtf1RKWZV6eIms4a6fCE9T9oSguiDn1V8zAEOdAZMk1Q77HvndI= Received: by 10.86.60.15 with SMTP id i15mr1056803fga.36.1206641917120; Thu, 27 Mar 2008 11:18:37 -0700 (PDT) Received: by 10.86.83.9 with HTTP; Thu, 27 Mar 2008 11:18:36 -0700 (PDT) Message-ID: Date: Thu, 27 Mar 2008 20:18:36 +0200 From: "Adrian Maier" To: "Guillaume Lelarge" Subject: Re: PostgreSQL website translations Cc: "PostgreSQL www" In-Reply-To: <47EBC4B2.2010304@lelarge.info> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <47D517C4.3000508@lelarge.info> <47E6D923.9050307@lelarge.info> <20080327130632.4baa89f8@mha-laptop> <47EBA9F4.3000207@lelarge.info> <47EBC4B2.2010304@lelarge.info> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200803/623 X-Sequence-Number: 14742 On Thu, Mar 27, 2008 at 6:00 PM, Guillaume Lelarge wrote: > Adrian Maier a =E9crit : > > On Thu, Mar 27, 2008 at 4:06 PM, Guillaume Lelarge > > wrote: > >> [...] > > >> Could work, but we still rely on the translator good will. No automat= ic > >> process here. Or am I wrong ? > > > > Actually , there are two different purposes : > > 1) detecting which translated pages went out-of-date > > 2) providing some reliable tools that help the translators to easily = spot > > the (English) modifications that they need to incorporate into their > > translated texts. > > You can already do this with HTML comments on the translation. To use > custom SVN properties, all translators will need to have SVN write > access to pgweb, which can be a problem. In this case the comments are preferable since they can start being used immediately after choosing a certain format . > If we agree on the HTML comments, we need to add the Revision tag on > each "template/en" file (see > http://svnbook.red-bean.com/en/1.4/svn.advanced.props.special.keywords.h= tml > for details). The PHP code will be able to compare the Revision tag > automatically added by SVN in the english file with the Revision comment > manually added by the translator on the translated file. > > For example, we will have: > > /* $Revision: 144 $ */ > > in the english file, and: > > /* #Revision: 144 # */ > > in the translated one. I don't use dollar between "Revision: 144" in the > translated file so that SVN doesn't automatically replace the english > based revision with the new translated revision. +1 --=20 Adrian Maier