public inbox for [email protected]  

help / color / mirror / Atom feed

From: Guillaume Lelarge <[email protected]>
To: Adrian Maier <[email protected]>
Cc: PostgreSQL www <[email protected]>
Subject: Re: PostgreSQL website translations
Date: Thu, 27 Mar 2008 17:00:50 +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]>
	<20080327130632.4baa89f8@mha-laptop>
	<[email protected]>
	<[email protected]>
	<[email protected]>

Adrian Maier a écrit :
> On Thu, Mar 27, 2008 at 4:06 PM, Guillaume Lelarge
> <[email protected]> wrote:
>> [...]
>>  Could work, but we still rely on the translator good will. No automatic
>>  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.

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.html 
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.

> I am primarily interested in (2) , because plain cvs/svn  is not helpful
> enough when translating .
> 
> As for (1) : it will never be possible to automatically ensure that a
> translation is truly up-to-date .  We'll need to trust the translators when
> they claim they've updated some page .  Especially when you don't
> understand their language ...
> 

+1


-- 
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]
  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