make life easier for translators
This patch breaks up the long, long usage text in pg_dump and pg_restore.
Every time someone changes something in this big string a translator (for
each language) have to read through it and try to figure out what it is
that differs now from the old translation.
It's much better to split it up to one string per option (and other utils
in postgresql do that).
I also replaced gettext() with _(). I didn't find any policy saying what
is the prefered way, and both _() and gettext() are used in other files. I
changed to _() since that is what most other programs use.
--
/Dennis
Attachments:
pg_dump_restore_gettext_fix.patchtext/plain; charset=US-ASCII; name=pg_dump_restore_gettext_fix.patchDownload+146-149
Dennis Bjorklund writes:
This patch breaks up the long, long usage text in pg_dump and pg_restore.
Good idea. I've installed this patch and your translation files from
August 20, refitted for this change.
I also replaced gettext() with _(). I didn't find any policy saying what
is the prefered way, and both _() and gettext() are used in other files. I
changed to _() since that is what most other programs use.
It's rather arbitrary, but I didn't want to reserve the _ symbol globally,
so it's a decision local to the source file or the subproject.
--
Peter Eisentraut peter_e@gmx.net