| From: | Dave Page <dpage(at)pgadmin(dot)org> |
|---|---|
| To: | Guillaume Lelarge <guillaume(at)lelarge(dot)info> |
| Cc: | pgadmin-hackers <pgadmin-hackers(at)postgresql(dot)org> |
| Subject: | Re: pgadmin3-release.pot |
| Date: | 2009-07-01 12:54:36 |
| Message-ID: | 937d27e10907010554v493d0b99r4b3721df0908909c@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgadmin-hackers |
On Wed, Jul 1, 2009 at 1:49 PM, Guillaume Lelarge<guillaume(at)lelarge(dot)info> wrote:
> Le mercredi 1 juillet 2009 à 14:47:34, Guillaume Lelarge a écrit :
>> Hi Dave,
>>
>> Le mercredi 1 juillet 2009 à 14:05:04, Dave Page a écrit :
>> > [...]
>> > I think it's probably time to update pgadmin3-release.pot. Any reason
>> > not to that you can think of?
>>
>> Actually, it's already done... on my laptop. Don't know why I didn't push
>> it on the server. I probably forgot to do it. Thanks for the reminder.
>
> Hummm, stupid me. I thought you were talking about pgadmin3.pot. What is the
> purpose of pgadmin3-release.pot? there's good chance you already told me, but
> I don't remeber.
When we release, we copy pgadmin3.pot to pgadmin3-release.pot. From
then on, whenever you run stringextract, it copies
pgadmin3-release.pot and uses that as the basis for the new
pgadmin3.pot.
I think the idea is, that all strings that are ever in a release
version of pgAdmin build up in pgadmin3-release.pot, so that you can
always use a modern translation with an older version of pgAdmin
without losing strings that are no longer in the modern release.
--
Dave Page
EnterpriseDB UK: http://www.enterprisedb.com