Re: PL/Perl translation, croak

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
Cc: Peter Eisentraut <peter_e(at)gmx(dot)net>, PG Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: PL/Perl translation, croak
Date: 2009-02-17 16:22:35
Message-ID: 3719.1234887755@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Alvaro Herrera <alvherre(at)commandprompt(dot)com> writes:
> Peter Eisentraut wrote:
>> plperl's nls.mk contains
>>
>> GETTEXT_TRIGGERS:= _ errmsg errdetail errdetail_log errhint errcontext
>> write_stderr croak Perl_croak
>>
>> As far as I can tell, croak() and Perl_croak() are provided by the Perl
>> library. So it is quite unclear to me how we expect their argument
>> strings to be translated using our message catalogs. Is this unfinished
>> business or is there some mechanism here that I'm not seeing?

> IIRC I just added them because we have a couple of error messages that
> are output with Perl_croak and one with croak. Does it fail to work? I
> don't remember if I actually tested it.

ISTM it would only work if the message was fed through our gettext
before being passed to croak(). So you'd need to write croak(_("msg"))
and marking croak itself as a gettext trigger is wrong.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2009-02-17 16:27:47 Re: [COMMITTERS] pgsql: Redefine _() to dgettext() instead of gettext() so that it uses
Previous Message Marco Colombo 2009-02-17 16:17:40 Re: Good Delimiter for copy command