Re: String changes - Mailing list pgsql-patches

From Dennis Björklund
Subject Re: String changes
Date
Msg-id Pine.LNX.4.44.0303082230160.27526-100000@zigo.dhs.org
Whole thread Raw
In response to Re: String changes  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: String changes
List pgsql-patches
On Sat, 8 Mar 2003, Tom Lane wrote:

> Yeah, but making those printfs different from the others is a recipe
> for future mistakes.  I thought that proposed patch was useless
> micro-optimization, too.

The reason to remove it is to help the translators.

When I find the string "\n" in the translation file I have to look that up
in the source to understand what it is and what it should be translated
to. Of course I could just translate it to "\n" but my experience as a
translator tells me that it's usually a sign of a misstake. When there is
many translations, and each translator has the same problem, then it may
be worth it to remove it.

It has nothing to do with the 0.00001s it takes to do the call to gettext.

--
/Dennis


pgsql-patches by date:

Previous
From: Joe Conway
Date:
Subject: new typeconv example (was [HACKERS] More outdated documentation)
Next
From: Tom Lane
Date:
Subject: Re: String changes