Re: backend/po, make update-po works strange - Mailing list pgsql-hackers

From Tom Lane
Subject Re: backend/po, make update-po works strange
Date
Msg-id 18353.1011212328@sss.pgh.pa.us
Whole thread Raw
In response to Re: backend/po, make update-po works strange  (Kovacs Zoltan <kovacsz@pc10.radnoti-szeged.sulinet.hu>)
List pgsql-hackers
Kovacs Zoltan <kovacsz@pc10.radnoti-szeged.sulinet.hu> writes:
> An example: parser/parse_agg.c contains an elog error at line 111 without
> any gettext call. In opposite, postmaster/postmaster.c at line 290
> contains an fprintf with a gettext call. Why the difference? Of course,
> the second string will appear in postgres.pot and the first one
> won't. File "gettext-files" contains both file.

The elog() strings are supposed to be picked up without any additional
marking.  Sounds like you are using the wrong procedure for extracting
the strings.  But I dunno what the right procedure is ...
        regards, tom lane


pgsql-hackers by date:

Previous
From: "Hiroshi Inoue"
Date:
Subject: Re: again on index usage
Next
From: Tom Lane
Date:
Subject: Re: Error in 7.2