Re: Proceeding with gettext - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Proceeding with gettext
Date
Msg-id 24758.991242888@sss.pgh.pa.us
Whole thread Raw
In response to Proceeding with gettext  (Peter Eisentraut <peter_e@gmx.net>)
Responses Re: Proceeding with gettext  (Peter Eisentraut <peter_e@gmx.net>)
List pgsql-hackers
Peter Eisentraut <peter_e@gmx.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


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Proceeding with gettext
Next
From: Ian Lance Taylor
Date:
Subject: Re: Support for %TYPE in CREATE FUNCTION