I'm not sure about other translators, but I'd like to see two files: one
for the backend and one for the utilities.
Translating strings can be a slow and tedious process and completing
them all at the same time is not likely. With two files you can choose
to translate the tools during one devel
Alvaro Herrera wrote:
The biggest downside I see is the long execution time for msgmerge.
I can live with that, especially if it will save me translating "out of
memory" six or seven times.
I'm using poedit which can replace empty translations with previous
translated values for the same/similar s
On Tue, Nov 09, 2004 at 12:00:46PM -0500, Tom Lane wrote:
> Peter Eisentraut <[EMAIL PROTECTED]> writes:
> > I was thinking about organizing the translation files in a more efficient
> > manner. (not for 8.0, obviously)
> > [snip]
> > And it would easily solve issues like translatable strings
> >
Peter Eisentraut <[EMAIL PROTECTED]> writes:
> I was thinking about organizing the translation files in a more efficient
> manner. (not for 8.0, obviously)
> [snip]
> And it would easily solve issues like translatable strings
> appearing in the pgport library, which has no makefile structure to s
