From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Serguei Mokhov" <mokhov(at)cs(dot)concordia(dot)ca> |
Cc: | "Manfred Koizar" <mkoi-pg(at)aon(dot)at>, "PostgreSQL Hackers" <pgsql-hackers(at)postgresql(dot)org>, "Peter Eisentraut" <peter_e(at)gmx(dot)net> |
Subject: | Re: pg_dump.options.diff |
Date: | 2003-01-02 20:20:35 |
Message-ID: | 3500.1041538835@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
"Serguei Mokhov" <mokhov(at)cs(dot)concordia(dot)ca> writes:
> Now, this:
> #if defined(HAVE_GETOPT_LONG)
> #define xo(long,short,desc) printf("%s %s\n", long, desc)
> #else
> #define xo(long,short,desc) printf("%s %s\n", short, desc)
> #endif
> seems relatively generic, so it could be used by more than one tool.
But there's no good place to put it. I'd say just stick it into each
tool; it's no worse than repeating the existence of a "usage()"
subroutine in each tool.
> Is pushing it up to c.h an option,
I'd vote against that.
>> The trouble I see there is that the layout --- in particular the column
>> width --- would be embedded in such a routine and not alterable by
>> simply replacing message texts.
> True, but what would be wrong by having an argument for the column width?
The translator would have no control over such an argument --- at least
not without some mechanism outside the .po files.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Jeroen T. Vermeulen | 2003-01-02 20:30:57 | Re: [HACKERS] Cast your vote ... |
Previous Message | Dan Langille | 2003-01-02 20:07:48 | Re: [HACKERS] Cast your vote ... |
From | Date | Subject | |
---|---|---|---|
Next Message | Serguei Mokhov | 2003-01-02 22:51:55 | Re: pg_dump.options.diff |
Previous Message | Serguei Mokhov | 2003-01-02 20:04:12 | Re: pg_dump.options.diff |