Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id AC38A2E0095 for ; Thu, 27 Mar 2008 11:07:13 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 16767-07-3 for ; Thu, 27 Mar 2008 11:07:00 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from sd-2317.dedibox.fr (sd-2317.dedibox.fr [88.191.17.192]) by postgresql.org (Postfix) with ESMTP id 5CBBC2E0090 for ; Thu, 27 Mar 2008 11:06:56 -0300 (ADT) Received: from [127.0.0.1] (localhost.localdomain [127.0.0.1]) by sd-2317.dedibox.fr (Postfix) with ESMTP id D5174343D; Thu, 27 Mar 2008 15:06:45 +0100 (CET) Message-ID: <47EBA9F4.3000207@lelarge.info> Date: Thu, 27 Mar 2008 15:06:44 +0100 From: Guillaume Lelarge User-Agent: Thunderbird 2.0.0.12 (X11/20080227) MIME-Version: 1.0 To: Adrian Maier CC: Magnus Hagander , PostgreSQL www Subject: Re: PostgreSQL website translations References: <47D3C345.6020206@hagander.net> <20080310094928.GH30980@svr2.hagander.net> <47D517C4.3000508@lelarge.info> <47E6D923.9050307@lelarge.info> <20080327130632.4baa89f8@mha-laptop> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200803/610 X-Sequence-Number: 14729 Adrian Maier a écrit : > On Thu, Mar 27, 2008 at 2:06 PM, Magnus Hagander wrote: >> Adrian Maier wrote: >> > Perhaps we could something like : every translated contains >> > a comment with the date+time+revision of the corresponding >> > English page ? at least this would make it possible to >> > manually manage the corresponding English revision for a given >> > translated page. >> >> Perhaps we could use a custom svn property for that? That would likely >> make it easier to process automatically to pull out differences and >> such. And perhaps some wrapper scripts around svn to help you set >> things automatically? > > I haven't used such custom properties. As long as such a property can > be set for individual files , it seems to be a better (more reliable) solution > compared to relying on comments. Some scripts for using this facility > would be a significant progress . > There's something I don't quite understand. What's the interest in having these comments (or custom svn properties) ? Tell me if I'm wrong. This is what we want to achieve : we want to know if a specific translated webpage is out of date Problem is : * translator checks out a file * during the translation, someone else checks out the file * and commit its changes * then translator commits its new translation Using the modification date doesn't help us because the translation file will be newer than the english one. Using the svn revision does not help us because the translation file will have a revision newer than the english one. So, your idea seems to put the revision of the english file in a comment or in a custom property. So, it's a manual change : * translator checks out a file * he updates the comment of the translation with the revision of the english file * he translates * he commits Is that right ? And when the web server needs to choose between the english file and the translated one, it parses the translated one to get the revision put in comments, it gets the current revision of the english files and it finally compares them ? Could work, but we still rely on the translator good will. No automatic process here. Or am I wrong ? -- Guillaume. http://www.postgresqlfr.org http://dalibo.com