Re: Gettext support for pgAdmin3 and the web site

From: Andreas Pflug <Andreas(dot)Pflug(at)web(dot)de>
To: jm(dot)poure(at)freesurf(dot)fr
Cc: pgadmin-hackers(at)postgresql(dot)org, Dave Page <dpage(at)vale-housing(dot)co(dot)uk>, "Adam H(dot) Pendleton" <fmonkey(at)fmonkey(dot)net>
Subject: Re: Gettext support for pgAdmin3 and the web site
Date: 2003-05-29 16:37:19
Message-ID: 3ED6373F.3020009@web.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgadmin-hackers

Jean-Michel POURE wrote:

>Hi Andreas,
>
>Just for information, do you think it would be difficult to add Gettext
>support to pgAdmin3? We could run an extract script on Snake and publish the
>.po files for translation everyday. I can handle po files merges for the team
>if you need someone.
>
It's not difficult, just going through the sources. gettext is supported
by wxWindows, so we should go ahead. I wonder if the wxrc lib already is
gettext aware. If not, after loading the resource it would be necessary
to loop through all controls and push them into the translator; not too
dificult either.

I don't think it's a good idea just to analyze the binary in total;
there are way too many non-translatable strings in it.

So there are these steps to perform:
- initialize gettext
- replace all translatable wxT() with _() in the sources
- push all *.xrc into the string extractor
- adding the gettext processing to Makefile
- adding the gettext processing to VC project.

I'll start this; as long as gettext isn't active, the _() macro can be
redefined as wxT().

I've seen that wxGetTranslation(), the gettext equivalent of wxWindows,
will use and return char*, not wxChar*. I wonder if this will give
problems if we are switching to unicode.

Regards,

Andreas

In response to

Browse pgadmin-hackers by date

  From Date Subject
Next Message Linus Mwaniki 2003-05-29 16:44:03 unsubscribe
Previous Message Dave Page 2003-05-29 12:18:57 Re: pgadmin2 ButtonMenus err