From: | Jean-Michel POURE <jm(dot)poure(at)freesurf(dot)fr> |
---|---|
To: | Andreas Pflug <Andreas(dot)Pflug(at)web(dot)de>, Dave Page <dpage(at)vale-housing(dot)co(dot)uk>, pgadmin-hackers(at)postgresql(dot)org |
Subject: | Re: pgAdmin3 ab sofort in Deutsch! |
Date: | 2003-06-06 08:09:51 |
Message-ID: | 200306061009.51567.jm.poure@freesurf.fr |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-hackers |
Dear all,
Congratulations for the language support. I have to catch up some work and
then I will translate pgAdmin3 into French.
> Where should we publicate pgadmin3.pot for all translators? Should we
> add it to CVS? (would make it more convenient for us)
Yes.
> Updating pgadmin3.pot *could* be added to Makefile, instead of calling
> stringextract manually, but this would create a lot of updates to CVS.
CVS release numbers are not increased after a commit unless the .pot file is
really different. So I see no problem calling a "make languages" by cron job
every 6 hours or so.
> Where should we put the resulting *.mo files? Again, for convenience, we
> could add them to CVS.
Yes. Although this is not very usuall, I vote for a separate CVS folder for
each language:
cvs_root/es_ES
cvs_root/en_US
cvs_root/de_DE
...
cvs_root/pgadmin3
Each folder will have different access codes :
user : es_ES
pass : ***************
This way, it will be more conveniant to give access codes to several people at
once (project manager, translators, re-writers). The number of translation
files can grow quickly : pgAdmin3 strings, website .po files, pgAdmin3 manual
.po files...
Managing a large number of languages is a turnkey for pgAdmin3 success.
Cheers,
Jean-Michel
From | Date | Subject | |
---|---|---|---|
Next Message | frank_lupo | 2003-06-06 09:04:22 | RE: pga2: problem schema |
Previous Message | Dave Page | 2003-06-06 07:32:23 | Re: pga2: problem schema |