Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id AB7C72E0033 for ; Thu, 27 Mar 2008 12:30:18 -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 57219-03 for ; Thu, 27 Mar 2008 12:29:57 -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.159]) by postgresql.org (Postfix) with ESMTP id 87CBA2E0093 for ; Thu, 27 Mar 2008 12:29:56 -0300 (ADT) Received: by fg-out-1718.google.com with SMTP id 22so4164127fge.23 for ; Thu, 27 Mar 2008 08:29:54 -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:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=8tOHhnd0z9LdzqMxZ+LHk/e1JrrX0dR6gv3U7wJyzTo=; b=QnKOjarVFtu/vRKMszvgFDzFxdxqW2UgckM1vPgH3zHLj71+nk1sS6a9iW7dw4vnPegTYzGFg5Qx8NSz89wQ8rZD1NqMKQ/RXshw5xuWOlFTmwaHN4w45gOo9PweCsxePJvHEHiWzrhlf8PEd2rsKJ3uXkcftjXG8gBAvYQ59Zc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=BQgFo039VgloKLkaW8bmc1Rrz01+mX+HntOhEMQ0sIgn0vEWH+GTFaHoUJXyvxOGAWlptMl92h6YB1WdG+zHB3ePjQV7SEcHfe2nV2M5Iw8b7dmR8G+3gWjJpdiNHFlK4d4RQNkO0/vuU3JwTqjtwa1164R8/0PoeTGmNrcgB38= Received: by 10.86.97.7 with SMTP id u7mr937680fgb.39.1206631794129; Thu, 27 Mar 2008 08:29:54 -0700 (PDT) Received: by 10.86.83.9 with HTTP; Thu, 27 Mar 2008 08:29:54 -0700 (PDT) Message-ID: Date: Thu, 27 Mar 2008 17:29:54 +0200 From: "Adrian Maier" To: "PostgreSQL www" Subject: Re: PostgreSQL website translations In-Reply-To: <47EBADA7.7050603@lelarge.info> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <47D3C345.6020206@hagander.net> <20080310094928.GH30980@svr2.hagander.net> <47D517C4.3000508@lelarge.info> <47E6D923.9050307@lelarge.info> <47EBADA7.7050603@lelarge.info> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200803/612 X-Sequence-Number: 14731 On Thu, Mar 27, 2008 at 4:22 PM, Guillaume Lelarge wrote: > Adrian Maier a =E9crit : > > [...] > > > Ok: I understand that there are no work resources for building some > > web application for translating the website. Some time ago i've been > > told that i'd have to rely on just CVS . I've accepted that and began = to > > translate the texts. And look what's the result: X months later when = I had > > the translation complete I found out that in fact the framework was no= t > > ready for accepting new translations - and all the work was in vain > > because when/if the everything will be ready i'll have to check and > > translate every single page. Again. > > > > Nope. > > I'll have to do this also. But I won't translate everything. I'll print > the english webpage and the french one, read them and check for > differences. I agree this is a tedious process, but much less than > translate once again every single webpage. Checking differences visually is what we should try to avoid : it's tedio= us, boring, and error-prone. Obviously, we have no automatic tools capable to compare an English text with its French translation and find the differences . But we can do 'diff' between different versions of the English text, provided that we know which revisions to compare. If we knew "the revision of the English page that corresponds to the latest translation " we could do svn diff on the English page (between that revision and HEAD) and see the differences , so that we wouldn't need to visually compare anything ! All we'd have to do is to look at the diff output and jump directly to the few phrases that were modified. That's what I'm after : a mechanism that can show me the specific modifications that were made on a specific English page since the last time *I* have translated that particular page. The problem is that this variable "the revision of the English page that corresponds to the latest translation" can be different for every page and is stored in only one place: the translator's memory . If the translator i= s offered a way to store it somewhere (anywhere : in svn as a property , or as a comment, or in a PostgreSQL database, ... ) then it would be possible to write some scripts for making the translation work much easier. --=20 Adrian Maier