| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Kovacs Zoltan <kovacsz(at)pc10(dot)radnoti-szeged(dot)sulinet(dot)hu> |
| Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: backend/po, make update-po works strange |
| Date: | 2002-01-16 20:18:48 |
| Message-ID: | 18353.1011212328@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Kovacs Zoltan <kovacsz(at)pc10(dot)radnoti-szeged(dot)sulinet(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2002-01-16 20:44:36 | Re: Error in 7.2 |
| Previous Message | Kovacs Zoltan | 2002-01-16 20:00:54 | Re: backend/po, make update-po works strange |