"Serguei Mokhov" <mokhov(at)cs(dot)concordia(dot)ca> writes:
> Looks good to me, but there is still a little inconvenience
> of multiline option descriptions, and the above won't handle
> it nicely.
True, a multiline description would have to look like
xo(_("-f, --file=FILENAME "),
_("-f FILENAME "),
_("output file name\n"
" more description"));
Which is not great, but it doesn't seem completely unworkable either.
And the translator can still adjust the column spacing without any
> may be a whole generic option-formatting routine
> should be created; one for all the tools? ;-)
> Similar to explain_option() of Manfred,
> which will handle the mulitline, padding, and other stuff?
> (am being half serious here, but it could be an "option")
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.
regards, tom lane
In response to
pgsql-hackers by date
|Next:||From: snpe||Date: 2003-01-02 19:07:56|
|Subject: Re: [HACKERS] Cast your vote ...|
|Previous:||From: Rod Taylor||Date: 2003-01-02 18:50:51|
|Subject: Re: Bug in pg_get_constraintdef (for deferrable|
pgsql-patches by date
|Next:||From: Tom Lane||Date: 2003-01-02 19:33:31|
|Subject: Re: NOT NULL Fixes |
|Previous:||From: Serguei Mokhov||Date: 2003-01-02 18:39:48|
|Subject: ru: translation updates -- backend and libpq|