public inbox for [email protected]  

help / color / mirror / Atom feed

From: Guillaume Lelarge <[email protected]>
To: Adrian Maier <[email protected]>
Cc: Magnus Hagander <[email protected]>
Cc: PostgreSQL www <[email protected]>
Subject: Re: PostgreSQL website translations
Date: Thu, 27 Mar 2008 15:06:44 +0100
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<20080327130632.4baa89f8@mha-laptop>
	<[email protected]>

Adrian Maier a écrit :
> On Thu, Mar 27, 2008 at 2:06 PM, Magnus Hagander <[email protected]> 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

view thread (30+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected]
  Subject: Re: PostgreSQL website translations
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox