Skip site navigation (1) Skip section navigation (2)

Re: Added \n to libpq prints

From: "Serguei Mokhov" <sa_mokho(at)alcor(dot)concordia(dot)ca>
To: "Bruce Momjian" <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: "PostgreSQL-patches" <pgsql-patches(at)postgresql(dot)org>
Subject: Re: Added \n to libpq prints
Date: 2001-08-18 02:59:18
Message-ID: 044701c12791$c72de720$5dd9fea9@gunn (view raw or flat)
Thread:
Lists: pgsql-patches
----- Original Message ----- 
From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Sent: Friday, August 17, 2001 10:55 PM


> > ----- Original Message ----- 
> > From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
> > Sent: Friday, August 17, 2001 11:02 AM
> > 
> > > I added some missing \n's to libpq error output.
> > 
> > This change affects the NLS {de|ru}.po files for libpq as well
> > in /src/interfaces/libpq/, so they need to be merged with the sources.
> 
> Yes, I know.  I thought Peter didn't want us messing with that.  Somehow
> he wants to handle the merges.

AFAIR he said something like let the language team maintain their language
issues and submit patches against current merges. The problem is that,
if you do not have an appropriate locale set up and if you edit the file certain characters
may easily get corrupt. This might not be a bigger problem for the latin* encodings,
but for others it is.

S.





In response to

pgsql-patches by date

Next:From: Serguei MokhovDate: 2001-08-18 03:02:06
Subject: Re: encoding names
Previous:From: Bruce MomjianDate: 2001-08-18 02:55:32
Subject: Re: Added \n to libpq prints

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group