Skip site navigation (1) Skip section navigation (2)

Re: Proceeding with gettext

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Proceeding with gettext
Date: 2001-05-30 17:14:48
Message-ID: 24758.991242888@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackers
Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
>> Wouldn't there need to be changes in the %-escape usage in elog message
>> strings?

> Are you referring to the possibility that the parameters need to appear in
> a different order in the translated message?  This can be handled if the
> translator uses the %1$s style place holder in the translated string.

Oh, I see: the translated message can use that form, but the original
need not.  Okay.

Are you planning to tackle any of the other elog-related stuff that's
been discussed in the past?  (Automatic file/linenumber information,
relabeling the set of severity codes, that sort of thing?)  Sooner or
later we're going to have to bite the bullet and edit every elog
instance in the system.  I'm just wondering if that flag day is implicit
in this change, or if we can put it off awhile longer.

			regards, tom lane

In response to

Responses

pgsql-hackers by date

Next:From: Bruce MomjianDate: 2001-05-30 17:14:58
Subject: Re: Support for %TYPE in CREATE FUNCTION
Previous:From: Ian Lance TaylorDate: 2001-05-30 17:06:06
Subject: Re: Support for %TYPE in CREATE FUNCTION

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group