Thread: pgAdmin3 ab sofort in Deutsch!

Code to call language dependent strings is successfully added to
pgAdmin3. It will work with wx2.4, and won't need Unicode for standard
languages (whatever ansi considers to be a standard language :-)

To create/update the pgadmin3.pot file, which acts as input to poedit,
the script stringextract can be used. By default, it will always append,
so over time there will be some garbage in it. This is ok, as long as
the app is changing. For a fresh build, simply pgadmin3.pot can be deleted.

For supporting an additional language, simply create a directory using
the canonical name under ui.


There are some questions left:

Where should we publicate pgadmin3.pot for all translators? Should we
add it to CVS? (would make it more convenient for us)
Updating pgadmin3.pot *could* be added to Makefile, instead of calling
stringextract manually, but this would create a lot of updates to CVS.

Where should we put the resulting *.mo files? Again, for convenience, we
could add them to CVS.

 From now on, the Win32 version will be binarily distributed as Unicode
version.

Regards,
Andreas

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