Re: i18n files

From: "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk>
To: <pgadmin(at)pse-consulting(dot)de>, <dpage(at)vale-housing(dot)co(dot)uk>, <pgadmin-hackers(at)postgresql(dot)org>
Subject: Re: i18n files
Date: 2005-12-09 21:43:34
Message-ID: 00cb01c5fd09$a051d491$6a01a8c0@valehousing.co.uk
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgadmin-hackers

Hi Andreas,

1.4.1 will be packaged with whatever is in the 1.4 branch. Aside from the fact that I have enough to do at release anyway (doc updates, 4 builds of pgAdmin, refreshes of everything else in pgInstaller, and it's build and testing) without having to merge translations from trunk, the tags/branches in SVN should match exactly what is released to allow any build to be easily recreated. Plus of course, there are makefiles and build scripts to keep in sync.

Regards, Dave

-----Original Message-----
From: "Andreas Pflug"<pgadmin(at)pse-consulting(dot)de>
Sent: 09/12/05 21:30:57
To: "Dave Page"<dpage(at)vale-housing(dot)co(dot)uk>, "pgadmin-hackers"<pgadmin-hackers(at)postgresql(dot)org>
Subject: i18n files

Hi Dave,

I did quite some updates on *.mo and *.po files lately, but only for
HEAD. IMHO there's no point in maintaining head and trunk for these
files, since they're 100 % backward compatible. (and CHANGELOG.txt
covers all changes too).

Just a note before 1.4.1 is packaged with outdated versions :-)

Regards,
Andreas

-----Unmodified Original Message-----
Hi Dave,

I did quite some updates on *.mo and *.po files lately, but only for
HEAD. IMHO there's no point in maintaining head and trunk for these
files, since they're 100 % backward compatible. (and CHANGELOG.txt
covers all changes too).

Just a note before 1.4.1 is packaged with outdated versions :-)

Regards,
Andreas

Responses

Browse pgadmin-hackers by date

  From Date Subject
Next Message Andreas Pflug 2005-12-09 22:05:11 Re: i18n files
Previous Message Andreas Pflug 2005-12-09 21:27:03 i18n files