Re: Proceeding with gettext - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: Proceeding with gettext
Date
Msg-id Pine.LNX.4.30.0105301642220.757-100000@peter.localdomain
Whole thread Raw
In response to Re: Proceeding with gettext  (Bruce Momjian <pgman@candle.pha.pa.us>)
Responses Re: Proceeding with gettext  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Bruce Momjian writes:

> Peter, can you give a little sample of how an elog() call would look in
> the new system?  Thanks.

No change.

elog() would call gettext() internally, so the code change there is
localized to elog.c.  For other function calls that contain translatable
message strings it looks like (example from psql):
   fprintf(stderr, gettext("Invalid command \\%s. Try \\? for help.\n"), my_line);

So obviously it would pay off if the communication of a program was
encapsulated in a limited number of functions.

-- 
Peter Eisentraut   peter_e@gmx.net   http://funkturm.homeip.net/~peter



pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: Support for %TYPE in CREATE FUNCTION
Next
From: Tom Lane
Date:
Subject: Re: Unused pg_class columns